Last updated: 4 May 2026 · France / EU
This policy describes how DATEMAP ("we", "us") processes personal data when you use our waitlist landing page. We aim to comply with the GDPR and applicable French and EU law.
The controller is the legal entity operating DATEMAP (startup). Contact details will be published on the product website as it matures.
Waitlist: email address only, and a creation timestamp. We do not collect city, profile information, or analytics identifiers beyond what your browser and hosting provider may log for security (e.g. IP in server logs — kept minimal and short-term where possible).
We process your email to manage the waitlist and send you a confirmation email, plus occasional updates about DATEMAP if you remain subscribed. Legal bases: your consent (Article 6(1)(a) GDPR) when you submit the form and tick the consent box; and, where applicable, our legitimate interest in securing the service and preventing abuse (Article 6(1)(f) GDPR).
Waitlist data is stored in Supabase (PostgreSQL). Data may be processed in the EU or under appropriate safeguards if providers use non-EU regions — we select configurations aligned with GDPR expectations for a startup MVP.
Transactional emails (e.g. waitlist confirmation) are sent via Resend. Resend acts as a processor under our instructions.
We keep waitlist emails until you withdraw consent or we delete the list as the product launches, unless a longer period is required by law. You may request deletion at any time (see below).
We do not sell your data. We share it only with infrastructure providers strictly necessary to run the waitlist (e.g. Supabase, Resend, hosting on Vercel).
Under the GDPR you may request access, rectification, erasure, restriction, portability, and objection where applicable. You may withdraw consent at any time without affecting prior lawful processing. You may lodge a complaint with a supervisory authority (e.g. CNIL in France).
We use reasonable technical and organizational measures appropriate to an early-stage product, including access-controlled database keys on the server and HTTPS for transport.
For the full legal context, also read our Terms & Conditions.