Privacy Policy
Effective date: 25 July 2026
mmeet brings two people to a real meeting and then gets out of the way. This Policy describes exactly which data that needs, where it goes, and how long it lives. It is written from what the app actually does: every line below corresponds to a specific place in the code rather than to a general formula.
1. Data controller
The mmeet team
The data controller under the GDPR is the mmeet team. For any question about this Policy or about your rights, reach us through the contact form.
2. Data we collect
This list is complete: everything the app stores about you is named here.
| Category | Examples |
|---|---|
| Account | Email and a bcrypt password hash, or your Google / Apple identifier if you sign in with them |
| Profile | Name, date of birth, gender, who you are looking for, city and its coordinates, zodiac sign, app language |
| Media | Your profile photo and the mmeet video with your answers. Stored in cloud storage in Frankfurt (EU) |
| Guardian contact | One phone number of a person who can be called in an emergency during a meeting. You enter it yourself — make sure that person is comfortable with it |
| Meetings and matches | Your matches, the proposed place and time, meeting confirmations and cancellations, and your remaining meetings for the month |
| Coordination chat messages | Text and — if you tap "Share location" — precise GPS coordinates. They live only while the chat is open: it opens one hour before the meeting and closes one hour after it, and every message is deleted on close |
| Technical data | Device type, OS version, push notification token (FCM), time of last activity |
| Product analytics (PostHog) | Your account identifier, gender, city, whether a video is uploaded, and which screens and actions occurred in the app. Email, name and phone numbers are not sent to analytics |
| Crash reports (Firebase Crashlytics) | Your account identifier and the technical detail of the crash. Email and name are not sent |
| Payments | Subscription status and remaining credits. We never see your card details — those are handled entirely by the App Store and Google Play |
3. Legal bases (GDPR)
| Contract | Creating an account, showing profiles, arranging a meeting — the service cannot run without this data |
| Consent | Notifications, product analytics, sharing your location in chat, the guardian contact. Consent can be withdrawn — see section 7 |
| Legitimate interest | Media moderation, abuse prevention, crash diagnostics, community safety |
| Legal obligation | Responding to lawful requests from public authorities |
4. How we use data
- Create your account and show your profile to people it may interest.
- Carry mutual interest through to a specific place and time.
- Open the coordination chat one hour before the meeting and close it one hour after.
- Send notifications about matches, meetings and changes to them. We do not send marketing campaigns.
- Check every photo and video automatically, so fakes and inappropriate content never reach other people.
- Investigate reports and block those who break the rules.
- Find and fix technical failures.
5. Who we share data with
Other people in the app see your profile: name, photo, age, city, video and answers. You decide what goes there. Your guardian contact and your email are never shown to other people.
Processors
| Google Cloud | Hosting for the website and blog; technical logs containing IP addresses | Belgium, EU |
| DigitalOcean Spaces | Storage for photos and videos | Frankfurt, EU |
| Google Gemini | Automated check of photos and videos before publication | Google (EU / US) |
| Firebase (Google) | Push notifications and crash reports | US |
| PostHog | Product analytics — which screens and actions occur in the app | EU |
| Resend | Sending email: address verification and service messages | US |
| Apple, Google | In-app payment processing | US |
Some processors (Firebase, Resend, Apple, Google, Google Gemini) process data in the United States. Those transfers rely on the Standard Contractual Clauses (SCC) approved by the European Commission, and on the EU–US Data Privacy Framework where the processor is certified under it.
We do not sell or rent your data. There are no advertising networks and no third-party trackers in the app.
6. How long data lives
- Chat messages — deleted when the chat closes, one hour after the meeting.
- Profile, photos and video — for as long as your account exists.
- Meeting and match records — for as long as your account exists.
- Technical logs — up to 30 days.
- After account deletion — see section 9.
7. Your rights (GDPR)
You have the right to obtain a copy of your data, correct it, delete it ("right to be forgotten"), restrict processing, port your data to another service, and withdraw consent you previously gave. Withdrawing consent does not affect the lawfulness of processing before the withdrawal.
To exercise any of these rights, write to us through the contact form. We respond within 30 days. If our response does not satisfy you, you have the right to lodge a complaint with the data protection authority in your country.
8. Data security
- All data travels over an encrypted HTTPS / TLS connection.
- Passwords are stored only as a bcrypt hash — the original password exists neither in the database nor in the logs.
- Authorization tokens are kept in your device's secure storage (Keychain on iOS, EncryptedSharedPreferences on Android).
- Emails, phone numbers and message contents never reach server logs.
9. Account and data deletion
You can delete your account at any time in the app's settings. Your profile, photos, video, messages, matches and meetings are deleted with no way to restore them. One anonymous record is kept: the reason for leaving, the feedback you chose to write, the app language, and the date. It contains no name, email or account identifier — it cannot be traced back to who left; it exists so we can see why people leave.
10. Age
mmeet is for adults only. Registration under the age of 18 is not permitted; accounts found to belong to minors are removed along with all their data.
11. Changes to this Policy
If the data we collect or the processors we share it with change, this page is updated and the effective date changes with it. We announce material changes in the app.
12. Contacts
Questions about this Policy — through the contact form.
