Privacy policy

The controller of your personal data under the EU General Data Protection Regulation (GDPR) is:

• KMM Technologies
• Legal form: Sole proprietorship (eenmanszaak)
• Owner: Klaus M. Müller
• Prins Willem-Alexanderlaan 9207312 GD ApeldoornNetherlands
• Chamber of Commerce no.: 97917311
• VAT number: NL005295669B02
• Email: info@meetmomme.nl

We have not appointed a data protection officer. Article 37 GDPR requires one where core activities consist of regular and systematic monitoring of people on a large scale, or of processing special categories of data on a large scale; our assessment is that MomMe meets neither condition. Send any privacy question to info@meetmomme.nl.

• Account data — name, email address and, where available, a profile picture. Depending on how you sign in, these come from Google, Facebook (Meta) or Apple; alternatively you give only an email address, to which we send a one-time sign-in link.
• Profile data — first name, date of birth, town, postcode, the profile photos you upload, a short bio, information about children (age stage), mother phase, family situation and preferences. Your town and postcode are converted once into coordinates so we can work out the distance to other mothers. We do not use GPS and we do not track your location.
• Verification photo (optional)— if you choose the “verified” badge, you take a selfie holding a given gesture. Only our moderators see it, it is never shown on your profile, and it is deleted immediately after review.
• Usage — swipe decisions (interested / not now) and chat messages.
• Technical data — a cookie remembering that you have seen the cookie notice, a device token for push notifications (in the app only, and only if you allow them), IP addresses (briefly, for security and abuse prevention) and technical error reports (logs, without chat content).
• Subscription data — whether you have an active MomMe Circle subscription. We receive no payment details; Apple or Google handles payment.
• Reports: if you report someone, the category and any note you add; if someone reports you, the reported messages and the conversation around them. Section 6 says how long we keep them.
• Suggestions, corrections and photos of days out (in the app, from version 1.0.6): if you suggest a place or report that something is wrong with one, we keep what you write, which place it is about and when. If you add a photo of a place, we keep the photo and the permission you gave: the text you agreed to, its version, the time and the app version. When you upload it we remove the location data from the file (EXIF), so a photo never gives away where you took it. See sections 3 and 6.
• Photos in a chat (in the app, from version 1.0.6): when you send a photo in a chat, we store it with us so that you can both see it. When it is sent we make a new copy of the photo and remove the location and camera data from the file (EXIF), so a photo never gives away where you took it. Photos in a chat are not checked automaticallyand are not sent to Google. Nobody at MomMe looks at them, except a photo that is reported. The app shows a chat photo through a signed link valid for 15 minutes, and keeps it only in your phone's working memory, not on its storage. See section 6.
• Reactions, replies, days out and plans in a chat (in the app, from version 1.0.6): when you react to a message with an emoji, we store which emoji, on which message and when. When you reply to a message, we store which message your reply points to. When you share a day out in a chat, we store which place you shared. When you suggest a day out, we store the place (name and town), the day and time if you choose them, who suggested it, and what you both answered or changed. Only the two of you see this, unless one of you makes a report: our moderators then see the reported messages and the conversation's latest messages (see section 6, Exception: reports). A push notification about a plan names no place and no time, so they do not show on your lock screen. See section 6.
• Browsing days out (in the app, from version 1.0.6): we work out the distance to a place on our server from the coordinates of your town and postcode; we do not use GPS. When you tap Route, your phone opens a maps app (such as Apple Maps, Google Maps or Waze) with the place; that app handles it under its own terms. When you share a day out outside the app, you share a public link to that place's page on meetmomme.nl; it holds nothing about you. When you add a plan to your calendar, we make a calendar file with the place, the day and the time, which your phone opens through a link valid for 15 minutes. We do not keep that file; the plan is then in your own calendar.
• Lights (in the app): when you light a light, we store the reason you pick from a fixed list (a rough night, feeling alone or a sick child, say), the time, and an approximate spot. We work that spot out from the coordinates of your home town and postcode and move it at random, by up to 5 kilometres; we do not use GPS. Other mothers only ever get that moved spot, never the coordinates of your home town; your own app does get them, to centre the map on where you live. A light burns for 8 hours, or shorter if you put it out yourself. While it burns, other mothers in the app see the reason, the approximate spot, the time and the number of hearts on the map, but not your name or your photo. When you send a heart to a light, we store that, and the mother who lit it sees your first name, also in her push notification. If she thanks you, you get a notification without her name. See section 6.
• MomMeetups and their group chat (in the app): when you organise a MomMeetup, we store its title, description, day and time, town, venue and address, how the others can recognise you if you fill that in, and the number of places. A member of our team reads a meetup before it becomes visible. After that, other mothers in the app see the title, description, day and time, the town, your name and profile photo as the organiser, and how many mothers are coming, with their profile photos. The venue, the address and how to recognise you are shown only to the mothers you have approved. The title, description, day and time and the town are also on meetmomme.nl, visible to anyone and findable through search engines, without your name, the venue or the address. When you ask to join, we store your request, and the organiser sees your name, town, age, stage of motherhood and profile photo to decide. In a meetup's group chat we store your messages, shown with your name and photo to the organiser and the approved mothers, and when you last opened it (only to show you what is unread; nobody else sees that). See section 6.
• MomMe points (in the app, from version 1.0.6): a points balance and its history: which things you did in the app earned points (a light that burned out, a heart for a light, an approved photo of a day out, a complete profile, say), when, and which rewards (a month of MomMe Circle) were requested and granted from them. See sections 3 and 6.
• Conversation ideas (in the app, from version 1.0.6): when you open a new chat, the app may show you a few ideas for a first message. We choose them by fixed rules, on our own servers, using only what you can both already see on each other's profile: an answer you both gave to a Klik question, and your children's age stage. No artificial intelligence is involved and no new service provider. We record which ideas you were shown, whether you picked, edited or dismissed one, and whether that conversation got a first message and a reply; never the text of your messages. With your account we also keep three settings: when you first used an app version with conversation ideas (it decides whether a conversation counts in the comparison), whether you turned the ideas off, and whether we have already asked you if you want to keep them. Section 6 says how long we keep this.

• Running your account and connecting you with other mothers, including showing your profile to other users — necessary to perform our contract with you, Article 6(1)(b).
• Push notifications (a new match, a new message) — performance of the contract, Article 6(1)(b). Sending them also needs your device permission, which you can withdraw in your phone settings at any time.
• Occasional reminder emails when you have a new match and have not been in the app for a while: at most three in a row, and none after that until you are back. This rests on our legitimate interest in a service that is actually useful, Article 6(1)(f). You can object at any time, in the app under Profile, Settings, or via the unsubscribe link in the email.
• Occasional emails about MomMe itself, when there are new features in the app, say. These are rare and one-off, they never advertise anyone else's products, and they rest on our legitimate interest in telling you about the service you use, Article 6(1)(f). You can object at any time via the unsubscribe link in the email or in the app under Profile, Settings, after which you will not get another. If you said yes to these emails when you signed up or in the app, the basis is your consent, Article 6(1)(a), which you can withdraw in the same places.
• Keeping the platform safe — screening uploaded photos for unacceptable content, rate limiting, abuse and fraud prevention — legitimate interest, Article 6(1)(f).
• Fixing and improving the service — legitimate interest, Article 6(1)(f).
• Improving the list of days out with your suggestions, corrections and photos. Only our editors see suggestions and corrections; if we decline one, you see the reason in My contributions. A photo stays private until our editors approve it; after that we show it in the app (and possibly later on meetmomme.nl) without your name. Suggestions and corrections: legitimate interest (a correct list), Article 6(1)(f). Photos: your consent, through the licence you grant when you add one, Article 6(1)(a).
• Finding out whether conversation ideas helpconversations get started. For that, a fixed share of new chats (about one in five) shows no ideas for a while, so we can compare; which chats those are follows from a fixed rule and says nothing about you. You can turn the ideas off in your profile settings at any time (from version 1.0.6 of the app). Legitimate interest in improving the service, Article 6(1)(f).
• Running the chat, with reactions, replies, shared days out and plans, and showing the distance to days out: performance of the contract, Article 6(1)(b).
• Running lights and MomMeetups: showing your light to other mothers, delivering hearts and thanks, showing meetups, putting requests to the organiser and running the group chat: performance of the contract, Article 6(1)(b).
• Keeping MomMe points and granting rewards. Every 1,000 points earn a month of MomMe Circle; a member of our team reviews the request and sees your points history while doing so, so that abuse (accounts that only send each other hearts, say) can be recognised. Your points are visible to you alone, never to other mothers. Performance of the contract (the points programme in the terms of use), Article 6(1)(b).

We never sell your data and we do not use it for advertising. We do not carry out automated decision-making, including profiling, that produces legal or similarly significant effects within the meaning of Article 22.

• Google LLC — Sign-in via Google OAuth (US).
• Apple Inc. — Sign in with Apple (US). Apple may create a private relay address so your email is not shared. See apple.com/legal/privacy.
• Meta Platforms Ireland Ltd. — Sign-in via Facebook OAuth (Ireland/US).
• Resend — Sends our emails (sign-in codes, welcome emails, reminders, emails about MomMe and moderation notices). Receives your email address, your first name and the content of the email, and processes them only to deliver it (US, standard contractual clauses).
• STRATO AG — Hosts our email addresses (such as info@ and moderation@meetmomme.nl) on a server we manage ourselves (Germany). If you email us, your address and your message are stored there. STRATO supplies only the server infrastructure.
• Neon Inc. — Database provider (US). All profile data, matches and messages are stored in the EU (Frankfurt).
• Vercel Inc. — Hosting for the web application (US).
• Cloudflare Inc. — Storage of profile photos and of photos you send in a chat, via Cloudflare R2 (US). Photos are stored in the EU and are not publicly accessible: the app shows them through a signed link valid for at most seven days (for a photo in a chat: 15 minutes). Anyone holding such a link can view the photo until the link expires; after that it stops working.
• Bird B.V. (Pusher) — Real-time delivery of chat messages. Messages pass through Bird's servers but are not stored there.
• Vercel Inc. (Web Analytics) — Anonymous page views and performance. No cookies are set and no IP addresses are stored, so this involves no access to information stored on your device.
• Google LLC (Cloud Vision API) — Uploaded photos are checked once, automatically, for unacceptable content. Legitimate interest in platform safety, Article 6(1)(f). Google does not retain the images after processing. Photos you send in a chat are not sent to Google.
• RevenueCat, Inc. — Manages the MomMe Circle subscription (US). Receives a pseudonymous internal account ID (a random code, not your name or email), your name and email, device identifiers and purchase and subscription events. Deleted along with your account. Card and bank details never reach RevenueCat or MomMe; they stay with Apple or Google.
• Apple Inc. / Google LLC (payment) — Processes subscription payment through your App Store or Google Play account (US). MomMe receives no payment details; we see only whether your subscription is active.
• Functional Software, Inc. (Sentry) — Error monitoring (US). Receives technical details (error type, an internal user ID). Chat messages and profile content are not sent.
• 650 Industries, Inc. (Expo) — Delivery of push notifications and app updates (US).
• Upstash, Inc. — Caching and rate limiting (US). The cache briefly holds copies of the profiles shown in your discovery deck (up to 10 minutes) and of nearby lights (up to 20 seconds). Rate limiting briefly processes IP addresses and internal user IDs. Chat messages are not stored there.
• KEPTAGO LTD (Geoapify) — Converts town and postcode into coordinates (Cyprus, EU), through the EU endpoint api-eu.geoapify.com. Only the town and postcode you typed are sent, no name, email or other account data. The request is made by our own server, so Geoapify does not receive your IP address or device details. Geoapify retains the query, the headers, our server IP address and a timestamp for each request, for access control and usage counting.
• OpenStreetMap Foundation (Nominatim) — Fallback for the same conversion, used only while Geoapify is temporarily unreachable (UK). Here too, only the town or postcode is sent, with no name, email or other account data.

We have, or are putting in place, a processing agreement with each of the above.

Some of the providers above are in the United States. Where personal data leaves the European Economic Area, we rely on the European Commission's standard contractual clauses, Article 46(2)(c) GDPR. You can ask us for a copy of the safeguards that apply to any particular transfer.

We keep your data for as long as you have an active account. If you delete your account:

• removed from our database at once: your account, profile data, matches and chat messages, all linked sessions and push device tokens;
• removed at our providers straight after: your profile photos and any verification photo not yet reviewed (at Cloudflare R2; reviewed ones are already deleted straight after review) and your subscription record at RevenueCat. If that fails once, we log it and clean it up afterwards;
• temporary copies in our cache (Upstash) expire on their own, within 10 minutes.

Deleting your account is final and cannot be undone.

Suggestions, corrections and photos of days out. We keep suggestions and corrections for as long as your account exists; they are deleted with it. If we decline a photo, we delete the file at once; only the fact that it was declined, with the reason, stays visible in My contributions. If you delete your account, we delete your photos still under review and your declined photos. An approved photo stays, no longer linked to you: the licence you granted applies to the photo, which shows a place, not you. The record of that permission (the text, its version and the time, without your name) stays with the photo. To have an approved photo removed, contact us through the support page; we then delete the photo and that record.

Lights. A light is no longer visible to others after 8 hours, or as soon as you put it out. What we store about it (the reason, the time, the approximate spot and the hearts) stays for as long as your account exists and is deleted with your account. A heart you sent is also deleted when the mother who lit that light deletes her account.

MomMeetups and their group chat.We keep a meetup, its sign-ups and its group chat for as long as the organiser's account exists; when she deletes her account, or when we remove the meetup, they are deleted. A meetup that is over no longer appears in the lists in the app and on meetmomme.nl. If you withdraw your request or leave a meetup, we delete your sign-up at once. You can delete your own message in a group chat; the organiser and MomMe can too. When you delete your account, we delete your sign-ups, your messages and the meetups you organised.

MomMe points. We keep your points balance, its history and your rewards for as long as your account exists; they are deleted with it. Points not yet credited (for a photo that was just approved, say) are deleted with it too.

Exception: reports.A report (by you about someone else, or by someone else about you) is kept even after a match ends and after an account is deleted, so that deleting an account cannot make a report disappear. We keep: who reported, the report's category and note, the reported messages (for a reported photo, a copy of that photo) and, for each report made from a chat, that conversation's latest messages at the moment of reporting (up to 40 per report), and the reported person's name, town and a cryptographic hash of her email address. We keep this until 6 months after our decision on the report, or, while there is no decision yet, until 12 months after the latest report; then it is deleted automatically. Legal basis: legitimate interest in platform safety, and the establishment, exercise or defence of legal claims, Article 6(1)(f).

Separately, we keep a short record of every report: who reported whom, when, the report's status and, while the conversation still exists, a reference to it. It holds no messages, category or note. We use it to keep the two of you from meeting again in the app, so it stays for as long as both accounts exist, beyond the periods above. It is deleted as soon as either account is deleted. Legal basis: legitimate interest in protecting you from renewed contact, Article 6(1)(f).

Photos in a chat. A photo you send in a chat is kept for as long as the conversation exists. If either of you deletes the photo in the chat, ends the match, or deletes her account, we delete the photo from our storage within an hour. A reported photo is kept as a copy with the report, for as long as the report (see above). A photo the other mother saved on her phone, or took a screenshot of, cannot be called back by us: so only send what you would also show at a birthday party.

Reactions, replies, days out and plans in a chat. These belong to the conversation: we keep them for as long as the conversation exists. If either of you ends the match, or either of you deletes her account, we delete them with the conversation. Reported messages, including ones about a plan, are kept with the report, for as long as the report (see above). If we take a place off the list of days out, its name and town stay in your plan. A plan you added to your own calendar is out of our reach: if you move or cancel the day out, remove it from your calendar yourself.

Conversation ideas. The records about conversation ideas (which ones you saw, picked or dismissed, and whether a conversation got a first message and a reply) are pseudonymised, not anonymous: they hold no message text, but they can be linked to a conversation. Each record gets a fixed deletion date when it is written, and is deleted at the next daily clean-up after that date: records from an evaluation at most 97 days after its originally scheduled end (7 days to follow the last conversations, then 90 days to analyse the result and decide), other usage records after 90 days. If we stop an evaluation early, that fixed deletion date does not change. They stay until that date when a match is ended, otherwise the evaluation would miss exactly the conversations that never got going. If you delete your account, we remove your account ID from them straight away; what remains stays until the same date. The fixed terms of an evaluation (its period, its deletion date and the rule that decides which chats show no ideas) contain no personal data, and we keep them permanently as the record of how the comparison was made. The three settings with your account (see section 2) belong to your account: they stay while your account exists and are deleted with it; the daily clean-up above does not touch them. Legitimate interest in improving the service, Article 6(1)(f).

Exception: bans. Where we have deleted an account for breaking the terms of use, we keep a cryptographic hash of the email address to stop it being used to register again. The address itself cannot be recovered from it. Legitimate interest in platform safety, Article 6(1)(f).

Under the GDPR you have the right to:

• access the data we hold about you (Article 15);
• rectification of data that is wrong (Article 16);
• erasure (Article 17) — you can delete your account and everything attached to it yourself, in the app (Profile → Delete account);
• restriction of processing (Article 18);
• portability — a copy of your data in a common format (Article 20);
• object to certain processing (Article 21 — see the separate notice below).

Write to info@meetmomme.nl. We reply within one month.

You have the right to object at any time, on grounds relating to your particular situation, to processing of your personal data that is based on our legitimate interests (Article 6(1)(f)). If you do, we will stop processing the data in question unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or the processing is for establishing, exercising or defending legal claims.

An email to info@meetmomme.nl is enough. You can also turn reminder emails off directly, in your profile or via the unsubscribe link in any such email.

You have the right to complain to a data protection authority.

MomMe is established in the Netherlands, so the Dutch Autoriteit Persoonsgegevens is our lead authority under the one-stop-shop (Article 56). You may always complain to the authority in the country where you live instead — in Ireland, the Data Protection Commission.

MomMe sets one strictly necessary cookie:

• Notice cookie — remembers that you have seen the cookie notice (valid one year).

We set no tracking or advertising cookies. Because the cookie is strictly necessary to provide a service you have explicitly requested, it does not require consent under Article 5(3) of the ePrivacy Directive as implemented in the country where you live.

We keep MomMe technically secure: encrypted connections (HTTPS), private photo storage (not publicly reachable, temporary signed links only) and passwordless sign-in via magic links or OAuth.

Found a security problem or a vulnerability? Please tell us directly at security@meetmomme.nl rather than sharing it publicly. We reply as fast as we can and are grateful for responsible disclosure. See also our security.txt.

We may update this policy. We will tell you about significant changes by email or a notice in the app.