Privacy Policy

Draft for the MVP launch — written for this product, not reviewed by a lawyer. Treat this as a placeholder until it gets real legal review.

Who we are

This Privacy Policy explains what personal data Blind Adventure collects, why, and what rights you have over it. The site operator is the data controller for the data described here.

What we collect

Why we process this data (legal basis)

Account and profile data: necessary to provide the booking and matching service (contract, Art. 6(1)(b) GDPR). Sensitive gender/orientation data: your explicit, separate consent (Art. 9(2)(a) GDPR), which you can withdraw at any time by contacting us. Safety-related data (reports, blocks, emergency contact): our legitimate interest in running a safe platform (Art. 6(1)(f) GDPR).

Who we share data with

Nominatim/OpenStreetMap (geocoding, see above). Our email provider, to send booking confirmations, reminders, and the meeting-point reveal. We do not sell personal data or share it with advertisers. Until an Adventure is over, other users never see your name, email, or exact identity — crew mates and Adventure details are anonymized (“Person 1”, “#047”). Afterwards crew mates see each other’s first name, and your e-mail address is only shared with a crew mate if you both choose to stay in touch (see below).

Cookies and local storage

We use WordPress’s own login cookies to keep you signed in — no advertising or analytics cookies. The homepage’s swipe deck remembers which Adventures you’ve saved or skipped in your browser’s local storage only; this never leaves your device and isn’t tied to your account.

How long we keep it

We keep account and booking data for as long as your account exists. Reports are kept for as long as needed for moderation purposes.

Your rights

Under the GDPR you have the right to access, correct, export, or delete your personal data, to object to or restrict certain processing, and to withdraw consent (for sensitive data) at any time. You can do most of this yourself under My account: edit your profile, withdraw your consent for sensitive data, download your data as a JSON file, and delete your account. Deleting anonymises your account: your profile, contact, emergency-contact, WhatsApp and consent data, your contact choices and blocks, and your message history are deleted and your name and e-mail are replaced by a placeholder; bookings, crew memberships, ratings (without comments) and reports are kept without any link to you, so that other people’s crews, our statistics and safety moderation stay intact. Future bookings are cancelled first. The download does not include reports other people filed against you, to protect their rights and our safety work. For any other request, contact the site operator. You also have the right to lodge a complaint with your local data protection supervisory authority.

Contact

Questions about this policy, or to exercise any of the rights above, can be sent to the site operator via the contact details on this site.

WhatsApp updates (optional)

If you opt in — during sign-up or later on the Safety page — we also send your Adventure messages (booking confirmation, reminder, the meeting-point release and the feedback request) to your mobile number via WhatsApp, in addition to the e-mails you always receive. These messages have the same content as the e-mails, including the meeting point once it is released. For this we store your mobile number and when you opted in.

WhatsApp messages are delivered through the WhatsApp Business Platform of Meta Platforms Ireland Ltd., which processes your number and the message content on our behalf; data may also be transferred to Meta Platforms, Inc. in the USA. Legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time on the Safety page — from then on you only receive e-mails; withdrawing doesn’t affect messages already sent.

Staying in touch with your crew

After an Adventure you can choose crew mates you would like to hear from again. Once the Adventure is over, the people from your crew are listed by first name so you can tell them apart. Your choice is private: another person only finds out if they chose you too. If you both chose each other, we send each of you the other’s first name and e-mail address — and only then. Once shared, this can’t be undone, because the contact has already been passed on; a choice that hasn’t been reciprocated can be withdrawn at any time. Choices are stored with the two accounts and the Adventure for as long as your account exists. Legal basis is your consent (Art. 6(1)(a) GDPR), given per person by choosing them.

Age verification (optional)

You can optionally verify your age on the My account page via Stripe Identity. If you choose to, you are redirected to Stripe’s own hosted verification flow and asked to show an ID document there. We never receive or store that document — Stripe processes it and sends us back only the result. When it’s a match, we briefly compare the verified name and date of birth against your account to confirm they’re consistent; we keep only whether they matched, not the values. If they don’t match, we review that one case to keep the platform safe — the verified name and date of birth are included in that internal review, but are not otherwise stored, and you’re notified too. Booking never requires this; it only shows a verified badge on your account. Stripe Identity, operated by Stripe, Inc. / Stripe Payments Europe, Ltd., acts as our sub-processor for this one step. Legal basis is your consent (Art. 6(1)(a) GDPR), given by starting the verification.

Paying for an Adventure

If you book a paid Adventure, you pay via Stripe Checkout, a payment page hosted by Stripe — we never see or store your card details, only Stripe does. We send Stripe the price, a description of the booking (your account’s e-mail and the Adventure’s public number, never the secret activity or location), and receive back whether the payment succeeded, which we use to confirm your booking. If a refund is due, we ask Stripe to return the payment the same way; we don’t hold the money ourselves. Stripe, Inc. / Stripe Payments Europe, Ltd. acts as our sub-processor for this. Legal basis is performance of the booking contract (Art. 6(1)(b) GDPR).