Blijdorp

Privacy Policy

Effective date: 10 August 2026 · Version 1.2

Blijdorp is a neighbourhood app that helps new and expecting mothers in Blijdorp, Rotterdam find each other for walks, coffees and friendship. We built it privacy-first: we collect the minimum needed to connect you with neighbours, we never sell your data, and we never show anyone your exact location. This policy explains what we process, why, and your rights under the EU General Data Protection Regulation (GDPR).

1. Who is responsible (controller)

Svetlana Zigalkina de Boer, Rotterdam, the Netherlands, is the data controller for the Blijdorp app.
Contact: via the in-app support form (Me → Contact support).

2. What we collect and why

DataWhy (purpose)Legal basis (Art. 6 GDPR)
Name, profile photo, life stage (expecting / has children) Your profile, shown to verified neighbours so you can find each other Contract (providing the service)
Phone number Sign-in by SMS code; keeps throwaway accounts out Contract; legitimate interest (community safety)
Recovery email (optional) Getting back into your account if you lose your phone; only used after you confirm it via a link Contract
Approximate location Showing you on the neighbourhood map and finding mums near you. We store only a point snapped to a ~200 m grid — your exact address or GPS position is never stored and never shown Contract; consent (you grant location access)
Children's age band and optionally gender Matching you with mums in a similar phase. We deliberately never ask a child's name or exact birth date Contract
Messages, invites, RSVPs, availability The core service: chatting and planning meetups. Messages are visible only to their participants Contract
Invitation link (who invited you) Blijdorp is invite-only; we record which member's code you used Legitimate interest (community trust)
Push token Sending notifications (new message, RSVP) to your device Contract; you can disable notifications in iOS settings
Blocks and reports Safety: keeping the community respectful; reports go to the founder for moderation Legitimate interest (safety); legal obligation where applicable
Journal entries: voice notes, typed notes, photos and the dates you give them Your private journal. Entries are visible only to you — never to other members, never on the map, never in chat. Each voice or typed note is sent once to our AI provider to be transcribed and written up; nothing is used to train anyone's models Contract (providing the service); consent (you grant microphone access)
Album share links (only if you make one) Letting family read one of your albums in a browser, without an app or an account. A link exists only when you create it: it carries an unguessable token, shows that album's dates, written records and photos and nothing else, and stops working the moment you turn it off. Photo links inside the page expire after an hour. We count how many times a link was opened, so you can see it is being read — never who opened it Consent (you choose to share); contract
Exports you make yourself The album PDF is created on your phone and handed to whatever you choose — Files, mail, a print service. Once it leaves the app it is yours to look after; we keep no copy Contract
Usage analytics (screens viewed, features used) Improving the app: seeing which parts are actually used and where people get stuck. Two contentless records — a pseudonymous event stream (PostHog, EU) and a small table in our own EU database holding an action name, a count and your member id (for example “album exported, 11 pages”). Never your name, phone, message or journal contents, photos, or location Legitimate interest (product improvement)

A note on profile photos: your photo is stored at an unlisted web address so the app can display it. It is not indexed or listed anywhere, but anyone with the exact link could view it. Choose a photo you are comfortable with.

3. What we never do

4. Who processes data for us

We use a small number of service providers (processors), bound by data processing agreements:

ProviderWhat forWhere
SupabaseDatabase, sign-in, file storageEU (Frankfurt, Germany)
TwilioSending the SMS sign-in codeUSA*
GoogleOptional "Continue with Google" sign-inEU/USA*
Expo & AppleDelivering push notificationsUSA*
ResendAccount and support emailsEU (Ireland)
MapboxMap display and place searchUSA*
Google (Gemini API)Transcribing and writing up your journal notes — one call per note. Your notes are not used to train modelsEU/USA*
PostHogPseudonymous usage analyticsEU (Frankfurt, Germany)
GitHub PagesHosting this policy and the page family opens an album link on. The page holds no data itself — it asks our EU database for the album each time it is openedUSA*

*Transfers to US providers are protected by the EU–US Data Privacy Framework and/or EU Standard Contractual Clauses (Art. 46 GDPR), and are limited to what each service strictly needs (e.g. Twilio only receives your phone number to deliver the code).

5. How long we keep data

6. Your rights

Under the GDPR you can, at any time:

Use the in-app support form (Me → Contact support) for any of these; we respond within one month. You also have the right to complain to the Dutch supervisory authority, the Autoriteit Persoonsgegevens.

7. Security

Data is encrypted in transit and at rest, stored in the EU, and protected by strict database access rules (each member can only read what the app intends her to see). Sign-in uses one-time codes — there are no passwords to steal. The community itself is protected by invitation-only membership, phone verification and active human moderation.

8. Children

Blijdorp is for adults (18+). We process only minimal information about members' children — an age range and optionally gender, provided by the parent — to match families in a similar phase. We never knowingly collect data from children themselves.

9. Changes

If we change this policy in a meaningful way we will tell you in the app before the change takes effect. The current version always lives at this address.