Privacy Policy
Last updated 4 October 2026. Applies to the WEDDI app for Android and to getweddi.com.
WEDDI helps you meet people who are in the same place as you, right now. That only works if you can trust us with very little — so we collect as little as we can, keep it for as short a time as we can, and never sell it. Questions: hello@getweddi.com.
What we collect, and why
| Data | Why |
|---|---|
| Email address | To sign you in with a one-time code, and to contact you about your account. Never shown to other users. |
| Profile: first name, birth date (shown as age), gender, bio, interests, languages, city | So people at the same venue know who you are. Your birth date confirms you are 18 or over. |
| Profile photos (up to 5) | Shown to people who can discover you at a venue and to your matches. |
| Verification selfie | A person on our team compares it with your photos once, to confirm you are real and an adult. It is never shown to other users. We do not run face recognition on it. |
| Location — only while the app is open | To find venues near you and confirm you are at the one you check into. We use your coordinates for that request and do not store them. Other people see a venue name or a rough distance, never your position. |
| Check-ins, "I'm Open" status, likes, waves, matches, messages (text, photos, voice notes) | The product itself. Messages are visible only to the two people in the match. |
| Reports and blocks | Safety. Reports are read by our moderators. |
| Device push token (only if you allow notifications) | To deliver notifications you have switched on. |
| Product events (e.g. "checked in", "matched", "met in person") | To understand whether WEDDI actually helps people meet. Never contain your location. |
Nearby (Bluetooth)
If you use Nearby, your phone exchanges short-lived anonymous identifiers with phones around it over Bluetooth. Before a mutual match, nothing about you leaves your phone except an anonymous codename and three interests, and our servers are not involved. When two people both tap "I'm interested", their phones exchange the details each chose to reveal, and the app may then create a match on our servers so you can chat. Bluetooth scanning is never used to work out where you are.
Who processes data for us
- Hostinger (servers in the EU) hosts our API, database, photo storage and email.
- Google Analytics counts anonymous visits to this website. It is not used in the app.
- If enabled in a future version: Google Firebase (Google sign-in and push notifications), Google Places (venue names; receives a location for the lookup, nothing about you) and Anthropic (optional AI suggestions; receives only the bio or photo you asked about, for that request, and does not train on it).
We never sell your data, never share it with advertisers, and show no ads.
How long we keep it
- Your account data: until you delete your account.
- Crossed-paths history: 24 hours. Skipped profiles: 30 days. Sign-in codes: 10 minutes.
- "I'm Open" expires after 2 hours; check-ins after 3.
- Database backups: kept privately on our servers for 14 days, then deleted.
Deleting your account
In the app: Profile → Settings → Delete account. Or on the web: getweddi.com/delete-account. Deletion is immediate and complete — profile, photos, selfie, check-ins, likes, matches and messages are erased from the live database at once, and disappear from backups within 14 days. If we suspended your account for a safety reason, we may keep a minimal record that it was suspended, so the same person can't simply rejoin.
Your rights
Depending on where you live (for example under the GDPR or the UAE PDPL) you can ask for a copy of your data, a correction, deletion, or restriction of processing, and you can object to processing or complain to your data protection authority. Write to hello@getweddi.com from the address on your account; we answer within 30 days.
Age
WEDDI is for people aged 18 and over. Accounts found to belong to anyone younger are removed.
Security
All traffic is encrypted (HTTPS). Photos and voice notes are stored privately and served only through short-lived signed links to people allowed to see them. Sign-in codes are stored only as one-way hashes. Session tokens on your phone are kept in the system's secure storage and are not included in device backups.
Changes
If we change this policy in a way that matters, we will tell you in the app before it takes effect.