How we handle your information

Who is responsible for your data

• The couple — Demilade & Bobola — are the data controllers. They decide

why your information is collected (to invite you, coordinate aso-ebi, and keep you updated about their wedding).

• yes.wedding (operated by TheRadar) is the data processor. We store

and handle the information on the couple's behalf; we do not use it for our own marketing. Entity: TheRadar.

What we collect, and why

We do not collect or store card numbers. Payment is a direct bank transfer between you and the couple's account; no card data ever touches this site, and there is no payment processor in between. Confirmed: no card data touches this site.

Invite-open analytics are first-party and household-level. We do not use third-party tracking pixels, and the open record does not store your raw invite token, IP address, or browser user-agent.

How messages reach you

Outbound messages (WhatsApp/email updates) are sent through AelosX, a messaging system operated within TheRadar, acting as a sub-processor. For message delivery, we pass the name and contact address needed to send the message. For held privacy-review workflows, we pass the household name, internal guest id, requested privacy action, and consent choice, without raw contact addresses. AelosX is operated by TheRadar (same entity, internal sub-processor).

Legal basis & your rights

• Consent is the basis for update messages — you opted in, and you can opt

out at any time.

• Applicable law: Nigeria Data Protection Act (NDPA) 2023 for Nigeria-based

guests; GDPR/UK GDPR for guests in the EU/UK (diaspora). NDPA 2023 applies to Nigerian guests; GDPR applies to EU/UK diaspora guests. A DPCO registration check is recommended before launch.

• You can see, correct, or delete your data. Submitted private invitations

now include a privacy slip where you can turn updates on/off or ask the couple to remove contact routes. The request is reviewed before destructive deletion so payment, receipt, and wedding-operation records are not erased by accident. AelosX may create a held workflow for the request, but destructive AelosX erasure is not enabled until the Aelos auth gate and dry-run sync path are proven. Within 30 days of your request.

Retention

We keep your information until **after the wedding (14 November 2026) plus a reasonable wind-down period**, then delete it, unless you ask us to remove it sooner. 6 months after the wedding (May 2027), then deleted.

Security

Data is held in an access-controlled database; admin access is limited to the couple and people they explicitly authorize; public forms are rate-limited. No method is perfectly secure.

Contact

privacy@theradar.co