Privacy Policy

Fancy a Drink (FAD)

Version 14 — Last updated: 11 November 2026

Fancy a Drink (“FAD”) is an app that helps people meet in real life in a low-threshold way at an affiliated bar. Because FAD leads to a real, physical meeting, we take privacy and safety extremely seriously and deliberately process no more data than necessary. This policy explains in plain language which data we use, why, with whom we share it, how long we keep it, and what rights you have.

1. Who are we?

FAD is offered by A.Y.V. Hubers Beheer B.V., established in Rotterdam. A.Y.V. Hubers Beheer B.V. is the controller for all personal data processed through the app and the associated bar portal.

A.Y.V. Hubers Beheer B.V.

Laan op Zuid 188

3071 AA Rotterdam, The Netherlands

Chamber of Commerce (KVK): 24425152 | VAT: NL818710093B01

Contact for privacy questions: privacy@fancyadrink.app

Once a Data Protection Officer has been appointed, their contact details will be listed here.

2. What does the app do?

FAD shows you profiles of other members, lets you invite one another for a drink and meet in real life at an affiliated partner bar, where the first introductory drink is offered via a voucher. The app has five membership tiers: Preview (free, browsing and chatting, no physical meeting except with your linked partner), Silver, Gold, Platinum and Ultra VIP. From Silver onward, verification is mandatory; a physical meeting and the voucher are available only to verified members, except between two linked partners in a couple subscription. The voucher screen shows the tier of the person who sent the invitation; your match sees it, and the bar sees it when you show the screen. With Ultra VIP, others may infer from this that you have passed the asset check. In addition, other members see your tier on your profile and, for Platinum and Ultra VIP, a crown by your name and avatar, including on the map and in the list. With the setting "Show my subscription to others" you hide this from other members, with two exceptions: the Preview tier is always visible, and if as a Platinum or Ultra VIP member you do not open your profile to another member's tier, that member sees you on the map as a black circle with a question mark and a crown, without photo or name. On the voucher screen the tier is always shown.

Because the app leads to a meeting in the real world, we process certain data (such as a liveness check and your approximate location) precisely to make that meeting safer. We explain the reason for each item below.

3. What data do we collect?

3.1 Account and registration data

Email address, used for your account, logging in (via a 6-digit code) and necessary service messages.
Date of birth, which you enter at registration. We use it to confirm that you are 18 or older, to show your age (not your date of birth) to other members, for the age filter and the minimum and maximum age you set yourself for matching, and to suggest a younger or older face in the avatar picker, which you can change. Your age is calculated each time it is needed and is not stored separately.
First name and a self-chosen nickname. Other members initially see only your nickname; your first name appears only after a match.

Couple subscription. If you take out a couple subscription (in the app: Bar hopping as a couple), we additionally process the link itself: who you are linked to, the link code, who proposed and confirmed the link, and when it started or ended. We use this solely to make the couple subscription work.

3.2 Profile data

Real profile photos, visible to other members in the Discover list, on your profile, in chat and in the status overview. As long as a paid account has not yet completed identity verification, we temporarily show other members a neutral icon instead of the photos.
On the map we show a composed comic-style avatar instead of your photo. This is a design choice and a soft threshold; the protection of your location lies in the blurring described in 3.3, not in the avatar.
Gender and the gender preference you are looking for. Because your gender preference may reveal your sexual orientation, we use it only with your explicit consent, solely for searching and matching. We show your preference to no one and pass it to no processor.
Religion, if you fill it in yourself, and your religion preference, if you filter by it. Both are optional and we process them only with your explicit consent, which you give separately: we show your religion on your profile and use it when other members filter by religion, and we use your preference for searching and matching. If you clear the field or your filter, we delete the information and your consent lapses.
Hobbies, interests, short profile texts and self-chosen personality traits.
Occupation or field of study (mandatory), so that other members get a realistic impression.

Assessment of photos. Every photo you upload is checked automatically before it is published. We check that it contains no nudity, and for the mandatory face photo (the photo shown on the voucher screen) we also check that a face is visible, because that photo must be recognisable. This check is carried out by Google Cloud Vision, acting as our processor. The photo is processed solely for this assessment, is not retained by the processor and is not used to train models. If a photo does not pass, it is rejected and other members never see it. We tell you that the photo was rejected, but not which feature was detected, because that information would make it possible to circumvent the check. If you disagree with the outcome, you can contact us at privacy@fancyadrink.app and a staff member will review the photo. The same check applies to photos you send in a chat.

Face photo for the meeting. In addition to your profile photos, we ask for one photo in which your face and shoulders are clearly visible. This photo appears on the voucher screen, so your match and the bar staff can see it is you at the meeting. Showing it to bar staff happens by you presenting your own screen, as with an admission ticket; we do not send this photo to the bar, and bar staff may not photograph or record the screen. As long as you have not yet added this photo, your regular profile photo appears on the voucher screen.

Processing location. The nudity check takes place within the European Union. Two checks can only be carried out outside the European Union, because our processor’s European facility does not support those functions: the face check on your first profile photo and on your face photo (the photo shown on the voucher screen), and the recognition of the logo on a payment card in the Ultra VIP asset check. Each time this concerns a one-off processing of a single image, solely for that check; if another photo becomes your first profile photo or your face photo, only that photo is checked again. This transfer relies on the safeguards described in chapter 7. These checks create no biometric template and we build no facial database; we establish only that a face is present in the photo and how large it appears.

3.3 Location data

Always approximate. On the map and in the list a profile is never shown at its exact location, not even after a match. We store your actual position, but show others only a point placed at random 100 to 200 metres away from it; the distance others see is also calculated from that shifted point. Everyone sees the same point, and it only changes when you move more than a kilometre, so your actual position cannot be worked out by looking repeatedly. This shows that someone is broadly nearby, without anyone being precisely traceable. This is our implementation of the GDPR principle of data minimisation.
Visible on the map and list. You decide with two switches whether you appear on the map and in the list; you only see others if you are visible yourself. While you are visible, we update your position when you switch one on or open the app, at most once every ten minutes; we never track you in the background for this. If you are not visible, we use your position in the Bars tab only to find bars nearby, without storing it. If you switch both off, we delete your position immediately. If it has not been updated for seven days, we delete it as well; if your notifications are on, you receive a message about this one day in advance.
On the way to a meeting. On a spontaneous date the app sends your position every ten seconds once you have both confirmed a bar, on a planned date only once you indicate that you are on your way; this continues until you have both checked in or one of you leaves the date. The other person only sees how far away you still are and, if you indicate it yourself, that you are on your way to the bar, never where you are; we delete these positions as soon as the meeting ends, and in any case no later than four hours after the last update. When you check in, our server checks whether you are within 150 metres of the bar; we record only the time, not your position.

3.4 Biometric data — the liveness check (special category data)

From Silver onward you carry out a liveness check: a selfie used to establish that you are a real, living person, and to compare your face with your identity document (against fake profiles and catfishing). This check is carried out by our verification partner Stripe Identity.

Verification is enforced at the moment you actually want to arrange a physical meeting: when confirming a bar, checking in and activating the voucher. Not at registration or when purchasing a membership.

Processing your face for this check is a processing of biometric data and therefore a special category of personal data within the meaning of Article 9 GDPR. We process it solely on the basis of your explicit consent, which we request separately and independently of the other terms, before the check. You may refuse this consent. If you refuse, you can still use Preview for free; for the verified features we then offer you an alternative, non-biometric verification route (see below).

Roles. In this check Stripe acts in a dual role: as a processor, Stripe stores the recordings and the consent evidence on behalf of FAD, and as an independent controller, Stripe uses biometrics for its own fraud prevention.
Data minimisation and retention. FAD does not build a biometric database of its own and does not store a biometric template itself. FAD receives from Stripe only a reference to the verification session and its outcome, being successful, failed or cancelled, together with the associated timestamps. Your identity document, your name and your date of birth are processed by Stripe and are not stored by FAD. At Stripe, the biometric features are fully deleted within one year; other identity data is generally kept by Stripe for up to three years as a processor. You can withdraw your consent for the biometric use at Stripe at any time via privacy@stripe.com.
Alternative without biometrics. If you do not want a biometric check, we offer a manual route: you send a photo of yourself with your identity document and an indicated gesture or code, which a staff member assesses visually without automated biometric processing. This keeps access to the verified features possible without having to provide biometrics.

3.5 Identity data

On escalation (for example following a report or for access to higher tiers), a full identity check via a document scan may be requested, also via Stripe Identity. This processes your legal name, date of birth and a passport-photo comparison. The facial comparison in the document check is also a processing of biometric data under Article 9 GDPR, on the basis of your explicit consent.

3.6 Asset data (Ultra VIP only)

Ultra VIP is the only tier with an asset check. It does not apply to Platinum or to any lower tier, and for those tiers we request no financial data.

If you choose Ultra VIP, you demonstrate yourself that you meet the tier. You choose from three routes: a business credit report from a recognised provider together with a Chamber of Commerce registration or evidence of participation in a company, a photo of a payment card that is issued by invitation only, or a statement from a notary or accountant regarding assets or solvency. We never ask for bank details, bank statements or access to your account.

The document is read and assessed in an automated way. We check whether the name on the document matches the name on your account, whether the document is current, and whether it meets the applicable threshold. If that check passes, the source document is deleted immediately after the assessment and we keep only the outcome, the extracted amount, the applied threshold, the chosen route and the timestamp. If the check does not pass, a staff member reviews it; in that case the document is kept until that review is complete, with a maximum of thirty days.

If you choose the payment-card route, the photo is processed outside the European Union for the logo recognition, because our processor’s European facility does not support that function. Cover the card number before taking the photo; we do not need it and do not ask for it.

Your rights in this assessment. The first check is automated. You always have the right to human intervention, to state your own position and to contest the outcome. If your application is rejected, that human review follows automatically; you do not have to ask for it. If you disagree with that outcome, you can respond via privacy@fancyadrink.app.

In the route via a notary or accountant we never see the underlying data. The notary or accountant is the controller for the processing of that data and acts under their own professional rules.

Submitted documents are held in shielded storage. They are never visible to other members and are not used for anything else.

3.7 Telephone number and the “avoid” feature

Your telephone number is always shielded from other members; no one can find you via your number.

With the avoid feature you can enter numbers of people you would rather not run into, via your phone’s contact picker — we never read your full address book.

We use your telephone number only for the avoidance function. For that we store only an encrypted representation, from which the number cannot be recovered.

3.8 Chat messages and photos in the chat

Messages you exchange with another member after a match.
Photos in the chat automatically expire 8 hours after being sent and are then physically deleted; no photo archive is deliberately built up. You can send at most six photos per conversation per day. Chat photos are held in shielded storage that only the two participants can access.

When you sign up or later in the safety centre, you can voluntarily provide one or more safety contacts, with an email address. We process those contact details on the basis of our legitimate interest in your physical safety (Article 6(1)(f)), solely for your safety during a date: to share a live location link with that contact, and to send that contact a safety alert if you do not respond to the check-in (see below); no name, photo or other data of your match. The data is not reused and not used for marketing. Where possible we inform the provided contact about this processing. The safety contact does not need a FAD account. We store these contact details in readable form, because a hashed value would be unusable in an emergency to actually reach the contact.

How the live location link works. The link points to a page on our own website with a unique, unguessable code in the address. Anyone who has the link can open the page; no account is needed, because a safety contact does not have to be a member. The page shows only your location and nothing about the person you are meeting, and states clearly that it comes from Fancy a Drink, with a reference to this privacy policy. The link works only while you have sharing active and expires automatically afterwards; sharing stops after four hours unless you extend it yourself, and you can end it yourself at any time. We delete your last shared position as soon as sharing ends, and no later than one hour after it has expired. If you have checked in during a date, sharing continues while the app is in the background, with an update every five minutes or every fifty metres; your phone then visibly shows that your location is in use. The page is not indexed by search engines. If your safety contact forwards the link, that person can also follow along while sharing is running; only share the link with people you trust.

Check-in during a date and automatic safety alert. If you have provided a safety contact with an email address and Check-in is on (this is the default; you switch it off in the safety centre), the app asks you two hours after you have checked in at the bar, with a notification, to confirm that you are okay. If you confirm, a new round of two hours begins. If you do not confirm, a final notification follows after four hours; if you do not respond to it within 30 minutes, we send your safety contact an email and start a live location share, so that your contact can see your position through the link in the email as soon as your phone provides it. We check this every five minutes, so a notification or email may arrive up to five minutes later. The check-in stops when the date ends, when you switch it off or when you no longer have a safety contact with an email address. In addition, we send an email if a share you started yourself goes without a new location for about half an hour. The email contains your nickname, how many check-ins you missed or that your share stopped, the time you checked in and of the last reminder you did not confirm, the link to the sharing page and, if available, the time of your last known location; if there is no location yet, we name the bar where you agreed to meet. We do not include raw coordinates, nor any data about the person you are meeting. The email is sent through our email processor Brevo, which therefore also sees the link. In the message we explain to your safety contact who we are, why it was sent, on what legal basis we process the contact’s details and where this privacy policy can be found, so that someone without a FAD account also knows what happens to their own data. If your safety contact no longer wants to receive alerts, they can unsubscribe through the email; we then remove the contact and let you know that it no longer receives alerts, so that you can choose another contact. The times mentioned may be adjusted if practice requires it.

3.9a Calendar link for a planned date

Once the bar and the moment of a planned date are set, you can add the date to your own calendar. The app creates a link to a calendar file containing only your match's first name and nickname, the name and address of the bar and the agreed moment. Anyone who has the link can open the file without logging in; the link works until 24 hours after the agreed moment, and we keep no copy of the file. What your calendar app then does with the appointment is governed by that app's terms.

3.10 Reports, blocking and moderation

You can block and report other members. For a report we record who reports, against whom, the reason and any explanation, plus a status for handling. We use this data to safeguard the safety of the platform and to detect patterns of unsafe behaviour.

If you report in the app that a partner bar is closed, we record who reported it, which bar and when, plus a status and the outcome of the handling. The bar is not shown who made the report. We use such a report to check the bar’s listing in the app and to detect misuse of the reporting function; a report does not automatically remove a bar from the app.

3.11 Payment and subscription data

Payments for paid tiers run mandatorily through Apple’s and Google’s in-app purchases, managed via RevenueCat. FAD does not receive credit card numbers or full payment data; we receive only the status of your subscription (which tier, active or not).

3.12 Technical data and age signals from the app stores

A technical device identifier and push tokens, to send notifications and to counter abuse.
Error reports. If something goes wrong in the app, we store the error message together with the app version, the platform, the operating system version, the app language and the screen on which it happened. We do not link this to your account: no user number, email address, nickname or device identifier is included, and we filter email addresses, phone numbers and other identifying codes out of the text beforehand. We use this only to find and fix errors, and delete it after 30 days.
Age signals. In regions where the law requires it, we receive an age category via the age-signal APIs of Apple (Declared Age Range) and Google (Play Age Signals), without your exact date of birth. We use this signal solely to provide age-appropriate access; we do not store it and do not use it for advertising or to share with third parties, in accordance with both platforms’ terms.
Consent for device data. For placing or accessing certain data on your device (such as push tokens) we ask your consent where the law requires it; strictly necessary technical identifiers, for example against abuse, we use on the basis of necessity.

3.13 Waiting list (landing page)

If you sign up via the public landing page for a city that is not yet active, we process your city, email address, telephone number, gender and age, solely to contact you at launch in your city and to measure demand per city. This is done on the basis of your consent, which is recorded with a timestamp.

3.13a Suggesting a venue (optional email address)

If you suggest a bar or venue through our website, you can optionally leave your email address. We process that address solely on the basis of your consent, given through a separate, unticked checkbox, to notify you when the venue you suggested joins or when FAD launches in your city. The field is optional: without an email address the venue is still submitted. You first receive a confirmation email (double opt-in); only after you confirm do we add you to a separate list at our email processor Brevo, kept apart from our business contacts. Every email contains an unsubscribe link; unsubscribing deletes your data in a single action. We keep your address until the purpose is met or at most twelve months after your submission, whichever comes first, and then delete it, including at Brevo.

3.13b Approaching hospitality venues

To invite hospitality venues to become partner bars, we email venues in the Netherlands at the general business email address they publish themselves, such as an info address; we do not use personal addresses for this. We take the name, address and that email address from the venue’s public business listing through Google’s Places service. We do this on the basis of our legitimate interest in recruiting partner bars (Article 6(1)(f)). A venue receives at most two messages: an invitation and one reminder. Every message contains an unsubscribe link. After unsubscribing, we keep the address only as a non-reversible code (hash), solely to prevent the venue from being approached again. If the venue does not sign up, we delete its data no later than twelve months after the last message. You can object at any time via privacy@fancyadrink.app.

3.14 What we do NOT collect

We never read your full address book or contact list.
We never sell or rent your data to third parties.
We do not use advertising IDs and do not show third-party advertisements in the app.
We do not build a biometric database of our own.

4. Why do we process this data (legal bases)?

Under the GDPR we have a legal basis for each processing operation:

Providing the service (account, matching, chatting, map, vouchers, location on the map and list and on the way to a meeting): performance of the contract (Article 6(1)(b)).
Liveness and identity check (biometrics): your explicit consent (Article 9(2)(a)), alongside performance of the contract for the verified membership.
Gender preference, religion and religion preference: your explicit consent (Article 9(2)(a)), which you can withdraw at any time.
Asset verification (Ultra VIP only): performance of the contract for the tier you have chosen, with your consent for supplying the documents.
Avoid feature: your consent and our legitimate interest in members’ safety (Article 6(1)(a) and (f)).
Safety contact: our legitimate interest in your physical safety (Article 6(1)(f)); we inform the contact where possible.
Reports, blocking, moderation and abuse prevention: our legitimate interest in a safe platform and accurate listings of partner bars, and where applicable compliance with a legal obligation (Article 6(1)(f) and (c)).
Error reports: our legitimate interest in a well-functioning and secure app (Article 6(1)(f)).
Waiting list and optional features: your consent (Article 6(1)(a)), which you can withdraw at any time.

5. Automated decision-making

A number of processes run wholly or partly automatically: the liveness and identity check via Stripe Identity, the assessment of asset documents for Ultra VIP, the automated assessment of uploaded photos, and the soft reduction of visibility in the event of a repeated pattern of no-shows (which restores itself once you appear normally again).

If an automated process (such as the verification, the income/asset check, the photo assessment or the no-show system) leads to a refusal, sanction or restriction of your account, you always have the right to human intervention: via privacy@fancyadrink.app you can object, state your position and request a re-assessment. We guarantee that an account is never permanently restricted or blocked without a final human review. The no-show measure is a light, self-restoring restriction of your visibility with no legal effect.

We use automated image and text recognition for reading asset documents and for assessing uploaded photos. We inform you when you are dealing with an AI system. The provider of the AI service does not use the supplied data to train its models.

We engage only the processors listed below. We conclude a data processing agreement with each of them. In addition there is one situation in which data reaches someone outside those processors: if you provide a safety contact, that contact receives a message from us when a safety alert is triggered. That contact is not a processor but a recipient you designated yourself; see chapter 3.9. Beyond this, we share your data with no one.

Supabase, Inc. (hosting and database): our database and authentication; FAD’s data is held in the EU region (Ireland).
Vercel Inc., United States (bar-portal hosting and server functions): running the server functions behind the bar portal (partners.fancyadrink.app), including bar sign-up and the waiting list, and bars referred by members.
Stripe Payments Europe, Ltd. / Stripe, Inc. (payment and verification): the liveness and identity check (Stripe Identity) and payment handling.
Sendinblue SAS (Brevo), France (email): sending service messages, verification codes and safety alerts to a safety contact you have provided.
Fastly, Inc. (delivery of map imagery): delivering the map imagery on the page where a safety contact views a shared location. In doing so Fastly sees the visitor’s IP address and which map tile is requested; a tile covers an area of several hundred metres and is not the exact position. The map data itself comes from OpenStreetMap.
Cloudflare, Inc. (domain, DNS and email routing): our domain infrastructure.
RevenueCat, Inc. (subscription management): managing the in-app subscriptions on top of Apple and Google.
Google Ireland Limited / Google LLC (image and text recognition): the automated assessment of uploaded photos and the reading of asset documents (Ultra VIP only).
Apple Distribution International Ltd. and Google (app stores): distribution, in-app payments and, where legally required, age signals.
Expo (650 Industries, Inc.), United States (push notifications): delivering push notifications (invitation, match, message, activation, safety alert) to your device. For this we pass on your device’s Expo push token together with the notification text; for a chat message this is the sender’s nickname with one fixed, translated phrase, or for several messages at once only the number of new messages, never the content of a message; for other notifications a fixed, translated text. Expo passes the notification on to Apple and Google, who deliver it to the device.

In addition to these processors, when a bar registers we consult two external sources that operate under their own responsibility and are not processors for us: the Business Register of the Chamber of Commerce (checking the KVK number provided by the bar owner; for a sole proprietorship the registered name may be the owner’s own name) and Google’s Places service (finding the venue’s correct, publicly known business listing).

7. International transfers

FAD’s core processing takes place within the European Economic Area (EEA): our database is at Supabase in Ireland and our email runs via Brevo in France. A number of processors are (also) established in the United States, in particular Vercel, Expo, Fastly and parts of Google, Stripe, RevenueCat, Cloudflare and Apple.

For transfers to the US we rely on appropriate safeguards. The EU-US Data Privacy Framework (DPF) is a valid transfer mechanism: the General Court of the European Union confirmed its validity on 3 September 2025. We rely on the DPF where the processor concerned is DPF-certified (such as Stripe), and we additionally use the European Commission’s Standard Contractual Clauses (SCCs) as a fallback, partly because an appeal against the DPF is still pending before the Court of Justice.

8. How long do we keep data?

Account data: as long as your account exists; after deletion, erased or anonymised within 30 days, including back-ups.
Biometric source material (liveness/identity): not kept by FAD; only a reference and the outcome are kept for as long as your account exists. At Stripe: biometric features deleted within 1 year, other identity data up to 3 years.
Financial source documents: where the check passes, deleted immediately after the assessment; where it fails, kept until the review by a staff member is complete, with a maximum of thirty days. Only the outcome, the extracted amount and the applied threshold are kept, for as long as the membership based on them is active and otherwise for up to twelve months after the assessment.
Chat photos: automatically deleted 8 hours after being sent.
Chat messages: kept as long as the match exists; if either person deletes the match, the conversation disappears for both.
Location: your last position until you switch both switches off, until seven days after the last update or until you delete your account, whichever comes first; positions on the way to a meeting until the meeting ends and no later than four hours after the last update; your last position when sharing live until sharing ends and no later than one hour after it has expired; on check-in and for an emergency signal only a time, no position.
Reports and safety data: up to 24 months after handling, or longer if necessary for a legal obligation.
Reports that a partner bar is closed: we erase who made the report six months after handling; which bar, when, the status and the outcome are kept for as long as the bar participates.
Safety contact details: kept for as long as you keep the contact in the app; if you delete the contact or close your account, they are erased immediately.
Check-in and safety alerts: the data of a check-in round (when confirmed or missed) and of a live share (without position) 30 days after it ends; of a sent safety alert (when and to which contact, without the message text) 90 days.
Waiting-list data: until launch in your city or a maximum of 12 months, whichever comes first.
Error reports: 30 days.
Push notifications in our sending queue: seven days after sending.

9. How do we secure your data?

Telephone numbers for the avoid feature are processed solely in encrypted/hashed form, never stored in readable form.
Chat photos are held in shielded storage with access rules, so that only the two participants see them.
The voucher screen is protected against screenshots (blocked on Android, detected on iOS after which the voucher expires).
The processing of biometrics is outsourced to a specialised partner (Stripe Identity), so that we do not manage a biometric database ourselves.

10. Your rights

Under the GDPR you have the right of access, rectification, erasure, restriction, data portability and objection. Where we process on the basis of consent, you can withdraw it at any time — in particular your consent for the biometric verification. You can delete your account in the app. Send a request to privacy@fancyadrink.app; we respond within 30 days.

11. Minimum age and age verification

FAD is intended solely for persons aged 18 and over. This is a strict lower limit: the app leads to a physical meeting and is connected with the consumption of alcohol. By using the app you declare that you are 18 or older.

At registration we ask for your date of birth. From Silver onward your age is additionally verified via the liveness/identity check. Where the law requires it, we also use the age signals from the app stores and additional age verification that meets the locally applicable requirements (such as the “highly effective age assurance” prescribed by the Online Safety Act in the United Kingdom). An exception applies to a couple subscription: the linked partner who remains on Preview does not go through this check; their age rests on the date of birth provided at registration.

12. Changes to this policy

We may update this policy. For significant changes we show a notice in the app. The date at the top indicates when the policy was last updated.

13. Complaints and contact

Do you have questions or complaints? Email privacy@fancyadrink.app. If we cannot resolve it together, you can lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) via autoriteitpersoonsgegevens.nl.

14. Region-specific rights

United Kingdom (UK GDPR): users from the UK have equivalent rights. Complaints can be lodged with the Information Commissioner’s Office (ICO) via ico.org.uk. In addition, the obligations of the Online Safety Act apply to FAD in the UK (see chapter 11).

FAD is offered in the Netherlands. Expansion to other countries of the European Economic Area and the United Kingdom will follow step by step. The app is deliberately not available worldwide; we do not offer it in jurisdictions we do not yet serve.

Privacy Policy