Privacy Policy

1Controller and contact

The controller within the meaning of Article 4(7) GDPR is Seyd Njoya, Elisenstr. 3, 45888 Gelsenkirchen, Germany. No entry in the German commercial register (Handelsregister).

For any data protection question and to exercise your rights, write to contact@meetdo.fun.

Data protection officer: none appointed. Where the conditions of Article 37 GDPR are not met and no officer has been appointed, the contact address above is the point of entry.

2Principles and scope

This policy covers the meetDo mobile app on iOS and Android and the associated servers. It does not cover third-party services reachable from the app, which have privacy notices of their own.

We collect only the data a feature actually needs, and only for as long as it is used. No personal data is sold and no advertising network is embedded.

3Overview of processing activities

Purpose, categories of data, legal basis and retention — activity by activity.

3.1 Account and authentication

• Data: email address, password hash, display name, registration date, session and refresh tokens; if you have it verified, your phone number.
• Legal basis: Article 6(1)(b) GDPR — performance of the user contract.
• Retention: for the life of the account, then 30 days before final erasure.

3.2 Public profile

• Data: display name, profile picture, level, activities practised, optional details.
• Legal basis: Article 6(1)(b) — without a visible profile no match can be made.
• Retention: for the life of the account; changes take effect immediately.

3.3 Slots and programmes

• Data: title, description, activity, date and time, meeting point and coordinates, participant list, rhythm and duration of a programme.
• Legal basis: Article 6(1)(b).
• Retention: for the life of the account; past sessions for up to 24 months for your practice statistics.

3.4 Messaging between members

• Data: content, sender, recipient, timestamp, read status.
• Legal basis: Article 6(1)(b).
• Retention: until deleted by those involved, at the latest when the account is closed.

3.5 Location and proximity search

• Data: precise device coordinates, search radius, addresses you type; for a slot's weather, the position of its venue rounded to about 10 km.
• Legal basis: Article 6(1)(a) — your consent, given through the operating system dialog.
• Retention: a position is processed for the duration of the search and is not kept as a history; the coordinates of a meeting point stay with the slot.

3.6 Push notifications

• Data: device token, device type, language, notification preferences.
• Legal basis: Article 6(1)(a) — your consent.
• Retention: until consent is withdrawn, until uninstall, or after 90 days of an invalid token.

3.7 Online status and attendance

• Data: last activity time, attendance confirmations for slots.
• Legal basis: Article 6(1)(b), under the control of the "online status visible" setting.
• Retention: the status is continuously overwritten and never historised.

3.8 Badges and progress

• Data: number of participations, badges earned, derived statistics.
• Legal basis: Article 6(1)(b).
• Retention: for the life of the account.

3.9 Safety and abuse prevention

• Data: reports and their content, suspension decisions, technical characteristics of abusive access.
• Legal basis: Article 6(1)(f) — our legitimate interest in protecting users and the service; the balance tips in your favour as soon as the data is no longer necessary for that purpose.
• Retention: up to three years, matching the limitation period for possible claims.

3.10 Technical logs

• Data: IP address, timestamp, endpoint called, status code, app version, operating system, error reports from the app (which you can turn off in “Who sees me”, “Technical logs” section). Your account identifier is replaced by a pseudonym and the IP address is truncated; your content, your location and your name are never included.
• Legal basis: Article 6(1)(f) — operational security, diagnostics, defence against attacks.
• Retention: 30 days at most (currently 14 days at Grafana Labs), up to 12 months in the event of a documented security incident.

3.11 Support requests

• Data: the content of your message, contact address, account concerned.
• Legal basis: Article 6(1)(b) and (f).
• Retention: three years after the request is closed.

3.12 Public web pages (meet-do.com)

• Data: for a slot you organise in a public place, its activity, its next date within 30 days and an area of about 500 m around the place. Never your name, your photo, an address or a recurrence ("every Tuesday"); a private place never appears.
• In addition, even when switched off, a slot in a public place may count, with nothing about you, in an activity area of about 2 km: never alone (at least 3 slots from 2 different people), never with a time, a place or a name. Private places, private programs and activities hidden from the map never count.
• Legal basis: Article 6(1)(f) — legitimate interest in showing meetDo and its activities publicly. You can object at any time: the "Public web pages" switch in "Who sees me", or "Cut everything now", removes your slots from the site within 10 minutes.
• Retention: as long as the slot is upcoming and the switch is on.

3.13 What I'm into and suggestions

• Data: the activities you choose (at sign-up or on "Me") and their optional level; those meetDo learns from what you do: confirmed attendance, joining a session, sessions and programmes you publish, following an activity; the activities you set aside ("Not for me"); your usual availability (days and times of day); for a suggestion sent as a notification, the suggested session and when it was sent. meetDo never learns from the pages you view or the time you spend on a screen, and a no-show or a cancellation takes nothing away from your interests.
• Purpose: to show you first what suits you (feed, map, choosing an activity), to pick the "For you" suggestions, one in four of them outside your interests, and to send at most one suggestion notification a day and three a week, never during your quiet hours. Your interests are visible to you alone: they never appear on your public profile, in search, or to other members. What meetDo has learned is expressed in words ("You keep coming back"), never as a number.
• Legal basis: Article 6(1)(f) — our legitimate interest in showing you first what suits you. You can object at any time: remove an interest, set an activity aside ("Not for me"), turn off "Suggestions" in the notification settings, or turn off "Learn from my sessions" in "What I'm into", which erases everything meetDo has learned.
• Retention: for as long as the account exists. What is learned fades on its own: its weight halves after 120 days without a new session, then it is erased. An activity you set aside stays set aside for 90 days. Sent suggestions are kept for 30 days.

3.14 Verified organizer application

• Data: the type of application (independent or coach), your trading name, your registration number if there is one (encrypted, never shown to other members), the date you applied; at review, facts meetDo already holds (verified email address and phone number, number of sessions hosted, no sanction in force); the decision, its date and, for a refusal or a withdrawal, its reason.
• What others see: only the “Verified organizer” badge on your profile, while the application is approved.
• Legal basis: Article 6(1)(b) — you ask for this verification, and it is part of the service.
• Retention: for as long as the account exists; a new application replaces the previous one. Each decision is also recorded in the team's log, alongside moderation decisions (§ 3.9).

3.15 Plans and purchases

• Data: your account's plan, its status, its end date and, if it was granted, the team member who granted it; for an App Store purchase, what Apple sends us: the original transaction identifier, the product, the end of the current period, automatic renewal and the environment (live or test). Apple sends us neither your name, nor your address, nor your payment details. The notifications Apple sends us are logged by their identifier and type, never their content.
• Legal basis: Article 6(1)(b) — making available the tools of the plan you took out or were granted.
• Retention: for as long as the account exists. When it is erased, the plan goes with it; the record of Apple's notifications remains, with no remaining link to you.

3.16 Structures

• Data: for a structure (club, association, company…): its name, its type, its registration number, the mandate you declare to represent it, its city and postcode, its description, its website, its contact phone number and email address, the review decision and its reason; for each member: their role, who invited them and when, and the date they accepted.
• No one is added to a structure without their agreement: an invitation only takes effect once accepted, and declining it erases it. A structure is visible to other members only once approved by the team.
• Legal basis: Article 6(1)(b).
• Retention: for as long as the structure exists. Leaving a structure erases your membership; dissolving it, or erasing its owner's account, deletes it. Its linked programmes then return to their authors, without being deleted.

3.17 Session and programme reports

• Data: an organizer can download the report of a session or programme they organise (PDF, CSV or JSON). It contains the title, the activity and the dates; for a session, each participant with their display name, the date they joined, their participation status and attendance, and the session comments; for a programme, its change log. Never an email address, a phone number, a location or anything from a safety watch.
• Legal basis: Article 6(1)(f) — the organizer's legitimate interest in keeping track of who took part in what they organise. Participants already see this in the app; the report tells the organizer nothing more.
• Retention: meetDo produces the file on request and does not keep it. Once downloaded, it is the organizer's responsibility, and they may use it only to organise their activities.

4Location data in detail

Proximity search and the map only work with your device's precise position. We ask for it only when you actually open one of those features — not at installation, and never in the background.

We keep no location history. A position is used to compute distances and then discarded. The only coordinates stored durably are those of meeting points you have yourself attached to a slot or a programme — they are content, not a movement profile.

The "public location" setting on your profile decides whether other members see a location for you. It is independent of the system permission: one allows us to process, the other governs visibility.

5Messaging

Messages are transmitted encrypted and stored on our servers so that you find them again on a new device; the photos and voice messages attached to them are stored, already encrypted, with Cloudflare. We do not use end-to-end encryption at present: we are technically able to access content, but do so only to handle a report or on the basis of a legal obligation.

Messages are not analysed for profiling, advertising or model training.

The "receive messages" setting determines who may write to you. Deleting a conversation removes it from your view; the copy held by the other person remains, as it forms part of their own data.

6Push notifications and device token

To send notifications, your operating system generates a device token — an identifier that designates your device to the delivery service. We store it with your account and pass it to Firebase Cloud Messaging (Android) or to the Apple Push Notification service (iOS).

The content of a notification necessarily passes through those services. We therefore keep it to the minimum and avoid including sensitive information.

You can turn notifications off entirely in your device settings, or tune them type by type in the app. The token is deleted as soon as you withdraw consent, uninstall the app, or the delivery service reports it as permanently invalid.

7Recipients and processors

Inside the app, other members see what you publish: your profile, your slots and programmes, the messages you send them. Beyond that, we pass data only to the following providers, each bound by a processing agreement under Article 28 GDPR and limited to what they need to deliver their service.

• Railway — hosting of the servers and the database, and fallback copy of uploaded files.
• Cloudflare (R2) — storage of uploaded files (profile photos, images, videos, voice messages) in the European Union: files are stored already encrypted by our servers, and Cloudflare does not hold the key needed to read them.
• Google Maps Platform and Places API — map display and address autocompletion; requests contain the coordinates needed for display.
• Firebase Cloud Messaging (Google) — delivery of notifications to Android devices.
• Apple Push Notification service — delivery of notifications to iOS devices.
• App Store (Apple) and Google Play — distribution of the app and handling of any purchases; in that respect these providers act as independent controllers.
• Grafana Labs (Grafana Cloud) — technical monitoring of the service: technical logs, request traces and operating metrics, hosted in the European Union (Germany), with a pseudonymised account identifier and a truncated IP address.
• Resend — sending the emails related to your account (for example address confirmation or password reset): your email address and the content of the message.
• Twilio — verifying your phone number by SMS: the number and the verification code.
• Hostinger — hosting of the meet-do.com website: web server logs (IP address, page requested, timestamp).

The app also contacts public services directly, without any account data. Like any web server, they receive your device's IP address and act as independent controllers:

• MET Norway (the Norwegian Meteorological Institute): a slot's weather, with the venue's position rounded to about 10 km;
• Unsplash: some images in the activity catalogue;
• only when Google Maps does not respond and the map falls back to OpenStreetMap: the OpenStreetMap Foundation (United Kingdom) for the map tiles of the area shown, served by a worldwide network of cache servers (Fastly, United States), komoot (Photon, Germany) for looking up a city or an address (the text typed, without your position), and FOSSGIS e.V. (Germany) for calculating a route (the start and end points).

We also disclose data where the law requires it, in particular to law enforcement authorities on the basis of a valid request.

8Transfers outside the European Union

Some of the providers listed are established in the United States or operate part of their infrastructure there. A transfer of personal data outside the European Union may therefore take place.

Such transfers are governed by the European Commission's standard contractual clauses under Article 46(2)(c) GDPR, except where an adequacy decision under Article 45 applies — for the United States, the recipient's certification under the EU-US Data Privacy Framework.

The United Kingdom benefits from an adequacy decision; OpenStreetMap map tiles pass through the cache servers of Fastly, based in the United States.

A copy of the applicable safeguards is provided on request at contact@meetdo.fun. Where a provider allows it, we prefer its European regions.

9Retention periods

We keep personal data only for as long as the purpose requires, then erase it or irreversibly anonymise it.

• Active account: for the whole of the contractual relationship.
• After account deletion: a 30-day grace period — it protects against accidental deletion — then permanent removal from production systems.
• Backups: overwritten no later than 90 days after deletion; until then they are inaccessible outside a restore procedure.
• Technical logs: 30 days, up to 12 months in the event of a security incident.
• Reports and suspension decisions: up to three years.
• What I'm into: for as long as the account exists; what is learned fades after 120 days without a new session, an activity set aside stays so for 90 days, sent suggestions are kept for 30 days.
• Accounting records for paid services: up to ten years, in line with commercial and tax retention obligations.

10Your rights

The GDPR gives you the following rights. Exercising them is free: an informal email to contact@meetdo.fun is enough, and we answer within one month. If the request is complex or we receive many, this period may be extended by two months; we then tell you so within the first month, with the reason.

• Access (Article 15): a copy of the data we process about you, with the purposes, recipients and retention periods.
• Rectification (Article 16): correction of inaccurate data and completion of incomplete data — for most fields, directly from your profile.
• Erasure (Article 17): deletion of your data, unless a legal retention obligation stands in the way.
• Restriction (Article 18): suspension of processing while accuracy or a balancing of interests is verified.
• Portability (Article 20): return of the data you provided to us, in a common, machine-readable format.
• Objection (Article 21): to processing based on legitimate interest, on grounds relating to your particular situation.
• Withdrawal of consent (Article 7(3)): at any time, for the future — in particular for location and notifications.

"Download my data" (Settings › Account) gives you, right away and in a machine-readable file, what meetDo keeps about you: profile, contact details and settings (privacy, notifications, languages, alerts), activities and interests, availability, the programmes you organise or co-organise with their schedules, sign-ups for and attendance at sessions, invitations, searches from the last 90 days, return watches, your emergency contacts and the people whose contact you are, safety incidents and shares, subscriptions and follow requests you sent, blocks and reports you made, session memories, comments, votes and badges, messages you sent with their attachments and proposals, reviews and recommendations you gave, reactions, devices and sessions, notifications and suggestions you received, plans, your organiser file, recorded no-shows, sanctions that targeted your account with their reason, your account's security log and usage events from the last 30 days.

It does not yet include data that also concerns other people: messages and reviews you received, who follows you or asks to follow you, reports and moderation checks targeting you, the audiences you are part of and, if you are on the meetDo team, the moderation actions you took. Handing these over awaits legal advice: you can already request them by writing to contact@meetdo.fun under Article 15, and we will reply within one month. Some information is, as a rule, not disclosed, after weighing the rights of other people (Article 15(4)): who blocked or reported you, and internal moderation notes. Technical secrets (passwords, tokens, encryption keys) never are.

11Right to lodge a complaint with a supervisory authority

Without prejudice to any other remedy, Article 77 GDPR gives you the right to lodge a complaint with a supervisory authority — in the Member State of your residence, of your place of work, or of the alleged infringement.

The authority competent for us is Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, the supervisory authority for North Rhine-Westphalia, Kavalleriestr. 2–4, 40213 Düsseldorf, Germany. A complaint does not require that you contact us first — we would nonetheless welcome the chance to resolve the matter ourselves.

12No automated decision-making

No automated decision within the meaning of Article 22 GDPR producing legal effects concerning you or similarly significantly affecting you is carried out.

Suggestions of activities, sessions and members are based on distance, your usual availability, the activities you chose and those meetDo has learned from your sessions (§ 3.13). They order what is shown to you and exclude no one; the decision to message someone or join a session is entirely yours.

Suspension decisions are always taken or confirmed by a human being. You may contest them (clause 13 of the terms of use).

13Security of processing

In accordance with Article 32 GDPR we implement technical and organisational measures appropriate to the risk, in particular:

• Encryption of all communication between app and server, according to the state of the art.
• Storage of passwords solely as a salted, non-reversible hash.
• Short-lived session tokens with a renewal mechanism, so that an intercepted token quickly becomes worthless.
• Access to production data restricted to those who need it, and logged.
• Notification of a personal data breach to the supervisory authority within 72 hours and, where the risk is high, to the individuals concerned (Articles 33 and 34 GDPR).

14Minors

The app is not directed at people under 18. We do not knowingly collect data about children.

If we learn that an account is held by a younger person, we suspend it and delete the associated data promptly. Parents and guardians can report such a case to contact@meetdo.fun.

15Cookies, trackers and device identifiers

The app is a native application: it sets no advertising cookies and embeds no tracking pixels.

• Local device storage: session token, language choice, display mode and notification preferences. Necessary for operation, never leaves the device.
• Device token for notifications: see clause 6, subject to consent.
• Map display: Google Maps may set identifiers of its own to serve tiles; Google's privacy notice applies in addition; on the backup map, OpenStreetMap's servers set no identifier.

We do not read the operating system advertising identifiers (IDFA, Advertising ID). No cross-app or cross-site tracking is carried out.

16Changes to this policy

We adapt this policy when the app, our providers or the law change. Only the version available in the app is authoritative; its version and effective date appear at the top of the document.

We announce any substantial change — a new category of data, a new purpose, a new recipient — in advance by email and in the app. Where a change requires your consent we obtain it separately: we never base new processing on your merely continuing to use the app.