ChoozMe - version 0.261118.3 - in force since 18 November 2026
Privacy Policy
How ChoozMe collects, uses, shares and protects personal data
In short: we do not sell your personal data and we do not run advertising in the Platform.
Version: v3.1.0 | Effective date: 2026-11-18
1. Data controller
| Controller | ChoozMe (we, us) |
| Privacy contact | privacy@choozme.com |
| Data protection officer | No data protection officer is appointed |
| Regulator | UAE Data Office |
This policy applies under the UAE Personal Data Protection Law (Federal Decree-Law 45/2021, the PDPL). It covers the ChoozMe website (choozme.com) and the ChoozMe apps (the Platform). Capitalised words such as Activity, Listing and Provider have the meaning given in section 2 of our Terms and Conditions (the Terms).
2. Who this covers
- Seekers, who create free accounts, choose interests, and discover and book Activities.
- Providers, who publish and deliver Activities and subscribe to a provider plan.
- Participants, who attend an Activity, including people an account holder books for (for example a child), and walk-in attendees whom a provider adds without an account.
- People shown in pictures that users upload, and website visitors (including people who join our waiting list).
3. What we process, why, and on what legal basis
Under the PDPL, personal data may be processed with the person's consent (Art. 6) or, without consent, only in the cases listed in Art. 4. The federal law has no general "legitimate interests" ground.
| What | Data | Why | Legal basis (UAE PDPL) |
|---|---|---|---|
| Account | Name, email, phone, date of birth, gender, nationality, username, password (stored only as a hash), language, time zone, city, area, country, interests, saved places, notification and display settings, whether two-step sign-in is on, profile photos | Create and run your account, sign you in, apply the 18+ rule, personalise what you see | Contract, Art. 4(9). Gender and nationality: consent, Art. 6 |
| Location | Your home city and country. On a phone, the app reads your approximate position once (if you allow it) and passes it to your phone's operating-system geocoder (Google or Apple services on your device) to turn it into a city and country; only the city and country are saved by us. On the web version, the position is sent through our gateway to OpenStreetMap Nominatim to look up the place; it is not linked to your account, but the rounded position and the answer are kept in a cache at our gateway for up to 30 days | Show classes and events near you | Consent, Art. 6 (phone or browser permission) |
| Provider locations | Venue address and coordinates of each class, event and session (shown publicly), the country at the time of publishing, and any relocation appeal | Show where an Activity takes place and check that a provider is listing in the country it operates in | Contract, Art. 4(9) |
| Profile and provider details | Photo, brand name and logo, biography, disciplines, experience, languages, links, plan and payment-account status | Show your public profile and Listings | Contract, Art. 4(9) |
| Face check | Short live capture (a series of frames taken while you follow on-screen prompts), the uploaded photos, a face template, the result, the consent version, and device and IP of each attempt | Confirm you are a real person, the same person each time, and that one person holds one account | Explicit consent, Art. 6, for sensitive (biometric) data. See section 4 |
| Face block list | Face template of an account banned for abuse | Stop banned users returning | Legal claims, Art. 4(3) |
| Bookings and attendance | What you booked, for whom, when, price, cancellations, check-ins, attendance, credits, packages, waiting list, transfers | Run bookings, refunds and reminders | Contract, Art. 4(9) |
| Participants and walk-in attendees | Name and, if the booker or provider adds them, email, phone and (for participants) date of birth of the person attending | Run the booking and attendance, and let a participant claim a profile | Contract, Art. 4(9); the booker or provider confirms authority (section 5) |
| Payments | Payment reference, amount, currency, status, refund and credit records. Card details stay with the payment partner | Take payments, refunds and subscription fees | Contract, Art. 4(9); keeping records: legal obligation, Art. 4(10) |
| Content | Class and event pictures, posters, session gallery photos, reviews, ratings, requests and offers | Publish Listings and let users find them | Contract, Art. 4(9). Pictures of other people: their consent, which the uploading provider must have (section 6) |
| Messages | Chat messages (stored as written) and conversation records, including the display names of both people | Deliver messages between users | Contract, Art. 4(9) |
| Safety records | Profile and message reports, blocks, moderation decisions and the reported content | Handle abuse, protect users, cooperate with authorities | Legal claims, Art. 4(3); legal obligation, Art. 4(10) |
| Security and device data | IP address, country, city, network, device id and name, operating system, app version, sign-in history, signed-in and trusted devices, and security, audit and request logs (section 9) | Keep accounts secure, detect fraud and misuse, support investigations | Consent given when you accept this policy at sign-up, Art. 6; account security as part of the contract, Art. 4(9) |
| Sign-up acceptance record | Version of the Terms and of this policy you accepted, when, and from which app version and platform (no IP address) | Prove which text you accepted | Legal claims, Art. 4(3) |
| Push notifications | Push token of your device, platform, device id and name, device time zone, on/off and quiet-hours settings | Send booking and account notifications | Consent, Art. 6 (phone permission); service messages: contract, Art. 4(9) |
| Service emails | Your email and the email content | Confirmations, receipts, reminders, sign-in and security codes, security alerts | Contract, Art. 4(9) |
| Updates from providers you follow | Your email and push token | Tell you when a provider you follow publishes or changes a class, when a waiting-list place opens, and similar notices | Consent, Art. 6; you can switch these off in the app settings |
| Referrals | Referral code, who signed up through it, the status (signed up, subscribed, paid) and any pending reward. The referrer sees the first name of the person referred | Run the referral programme | Contract, Art. 4(9) |
| Support reports | If you choose to send a problem report from the app: device, app and session details, the last 25 KB of the in-app event log and error list, and your note (up to 1,000 characters), sent by email | Fix the problem you report | Consent, Art. 6 (you trigger it) |
| Calendar | Nothing leaves your phone. If you choose, an event is written to your phone's calendar | Add a booking to your calendar | Consent (phone permission), on-device only |
| Website waiting list | Email, language, invite code, confirmation status and timestamps; a hashed form of your IP address for rate limiting; Cloudflare Turnstile bot check | Tell you when ChoozMe launches | Consent, Art. 6 (double opt-in) |
We do not run advertising in the Platform. Service messages about your bookings and account are not marketing. The messages in "Updates from providers you follow" are sent on the basis of the settings above.
4. The face check
When you sign up, change your profile photo, or become a provider, we ask you to take a short live face check. We ask for your explicit consent first, and you can choose not to take it, in which case you cannot open an account.
- Why: to confirm you are a real person, that you are the same person each time, and that one person holds only one account. This protects users from fake and duplicate accounts and from banned users returning.
- How: the face is first found on your phone (Google ML Kit, which runs on the phone and does not send pictures to Google). The comparison and the liveness check run on ChoozMe's own servers in Germany. No third-party face recognition service is used.
- What we keep: the frames of each check, the photos you uploaded for it, a face template (a numerical description used to compare faces) for each attempt, the result, the consent version, and the device and IP address of the attempt. Previous profile photos are kept while the account is open. If an account is banned for abuse, a block-list entry for that face is kept so the ban cannot simply be worked around. Entries are added by authorised ChoozMe staff and have no time limit; they stay until a person removes them.
- How long:
- a refused sign-up attempt: 90 days;
- an unfinished check: 24 hours;
- a verified account: while the account exists, and 365 days after the account is finally deleted (that deletion happens 90 days after you close the account, see section 9, so in total about 455 days after you close it);
- an account banned for abuse: 1,825 days (5 years); the block-list entry has no time limit.
- Who sees it: only authorised ChoozMe staff, and access to face-check pictures is recorded. It is never sold or used for advertising.
- If the check refuses you: a refusal is made automatically. We do not yet have a set review process; you may write to privacy@choozme.com and we will look at your request, but we do not promise a particular outcome or time.
- Withdrawing consent: you can stop taking the face check at any time, but then the account cannot continue. We do not have an automatic withdrawal function: to have your face data removed, close your account (section 9) or write to privacy@choozme.com.
- The face check confirms an account, not a person's background, qualifications or safety.
5. Bookings for someone else and children
An adult account holder may book for another person, including a child. A provider may also add a walk-in attendee who has no account and has not seen this policy. We ask only for the information needed to run the booking or attendance. The booker confirms they are entitled to give us the participant's details and, for a child, that they are the parent or guardian or have their consent. If the participant's email is added, we may email the participant about the booking and invite them to claim their own profile.
Accounts are for people aged 18 and over; the sign-up check is a date of birth that you enter, and we do not verify it against a document. We do not use children's information for marketing or profiling. A parent or guardian, or a walk-in attendee, can ask us to show, correct or delete their data at privacy@choozme.com; we handle these requests by hand and cannot yet do them from within the app.
6. Photos and other people
Providers can upload pictures for their profile, brand, Listings and session galleries, and these may show other people, including participants. The provider who uploads a picture is responsible for having the right to use it and the consent of every identifiable person shown (and a parent's or guardian's consent for children), as set out in section 9 of the Terms. ChoozMe hosts and displays these pictures for the provider and does not check them before they are published.
Profiles and chat messages can be reported in the app. Gallery photos, posters and Listing pictures cannot yet be reported in the app: if you appear in such a picture and did not agree to it, write to privacy@choozme.com with the picture and where you saw it. We will review it and may remove it, and we may share your request with the provider who uploaded it. Taking or publishing pictures of people without their consent can be a criminal offence in the UAE.
7. Who we share data with
- The other side of a booking: providers see what they need to deliver the Activity (participant names, attendance, the booker's contact for the booking). Providers are independently responsible for how they use that data.
- Other users, as you choose: your public profile, Listings, reviews and requests are visible to other users; your messages go to the people you write to.
- Authorities: courts, regulators or police where a valid legal request or a legal obligation requires it. We check each request and disclose only what is required.
- A buyer or successor if the Platform's business is reorganised or transferred, under equivalent protections.
- Service providers acting for us are listed in section 8.
We do not sell personal data, and we do not share it for third-party advertising.
8. Service providers and where data goes
Our servers and database are hosted outside the UAE. The table shows each provider and the country we can state.
| Provider | What for | Data | Where | Transfer basis (PDPL Arts. 22-23) |
|---|---|---|---|---|
| Hetzner (servers and database host) | Application servers, the main database, our own database copy of audit and request logs | All account data | Germany | Transfer needed to run the contract with you (Art. 4(9)) and your consent at sign-up |
| Cloudflare | Website, API gateway, bot check (Turnstile), DNS, security, and R2 object storage for photos and face-check pictures | Request metadata, IP address, photos and face-check frames | Global network; R2 storage location is as configured in our Cloudflare account | Same as above |
| Stripe | Payments and provider payment accounts (providers' business, identity and bank details are collected by Stripe) | Payment and payout data; for providers, email and country | Stripe's own locations | Same as above |
| AWS (Logbook) | Audit, security and service logs | User ids, actions, IP address, device and network details, paths, status, error text (no message bodies, no tokens, no passwords) | AWS, configured for the Middle East (UAE) region me-central-1 | Where stored in the UAE, no transfer; otherwise as above |
| ip0 (mail.ip0.ch) | Sending all emails (sign-in and reset codes, receipts, booking notices, waiting-list mail, support reports) | Email address, message | ip0's servers | Same as above |
| Google (Firebase Cloud Messaging) | Push notifications, when push is switched on | Push token, notification content | Google's own locations | Same as above |
| OpenFreeMap | Map tiles | Your IP address and request details when a map loads | OpenFreeMap's servers | Same as above |
| OpenStreetMap Nominatim (web version only) | Place search and reverse lookup | The place or position you search for (sent from our gateway, cached there for up to 30 days) | OpenStreetMap's servers | Same as above |
| Google or Apple (your phone's geocoder) | Turn your approximate position into a city and country | Your approximate position | Provided by your phone's operating system | Your consent (phone permission) |
| Google ML Kit (on your phone) | Face detection on the device | None leaves your phone | n/a | n/a |
The PDPL allows transfers abroad to places with adequate protection or with safeguards or listed exceptions (Arts. 22-23). Where a provider's exact location is not shown above, we have not stated it because we cannot confirm it.
9. How long we keep data
| Data | Kept for |
|---|---|
| Account and profile | While your account is open, then closed as described below |
| Face check data | As set out in section 4 |
| In-app notifications | 30 days |
| Bookings, attendance, payment and refund records | Kept without a set end date; after you close your account, names stored in them are not yet replaced automatically (see below) |
| Chat messages | Kept without a set end date, including after you close your account |
| Sign-in history, signed-in and trusted devices | Kept without a set end date |
| Push tokens | Removed when you sign out or the token is replaced; not yet removed when an account is closed |
| Audit, request and security logs in the log service (Logbook) | 2 years |
| Service error logs in the log service (Logbook) | 14 days |
| Request records in our own database | No automatic deletion at present |
| Unfinished photo uploads and rejected photos | 7 days |
| Reports of profiles and messages | Kept without a set end date |
| Waiting-list email | Confirmed addresses until you unsubscribe, then deleted at once; unconfirmed addresses are deleted after 24 hours |
| Backups | Deleted or changed data may remain in our backups until they expire |
Closing your account: you can close your account in the app. It is first deactivated for a grace period of 90 days, during which you can come back by signing in. After that, a daily job replaces or removes your name, email, phone, username, password, profile and brand photos, brand name, nationality, area, interests, the reason you gave for leaving and your biography and links as a provider, and deletes your face template. It does not currently remove or replace your date of birth, gender, city, country, language or time zone, your chat messages, your sign-in history and devices, your push tokens, or the names and contact details held in bookings, attendance, reviews and conversations. Bookings, payments, refunds, credits and collaboration shares are also other people's records and are kept. We are working to close these gaps; until then, you can ask us at privacy@choozme.com to look at specific data, and we will tell you what we can and cannot remove.
10. Security
We protect personal data with measures such as encryption of traffic between your device and our edge, hashed passwords, short-lived access tokens (30 minutes) with revocable sign-in sessions, optional two-step sign-in by email code (6 digits, valid 10 minutes), access controls with audit logs, and limited staff access. Logs do not contain message bodies, tokens or passwords. No system is completely secure.
11. Cookies and device storage
- Web app: strictly necessary sign-in cookies, __Host-cm_at (access) and __Host-cm_rt (refresh). They are HttpOnly, Secure and SameSite=Strict, and the web app keeps you signed in for up to 30 days.
- Website: a short-lived strictly necessary cookie (cm_flash) used to show a confirmation message, and browser session storage (cm_code) that holds an invitation code while you use the page.
- Bot check: Cloudflare Turnstile loads a script from Cloudflare when you join the waiting list or sign in, and may store its own data in your browser.
- Apps: sign-in credentials are kept in your phone's secure storage; biometric unlock, if you use it, is handled by your phone and is not sent to us.
We do not use advertising cookies or third-party analytics.
12. If something goes wrong
If a data breach affects you in a way that harms your privacy, confidentiality or security, we will tell you and the UAE Data Office as the law requires (PDPL Art. 9), within the period set by UAE law and its executive regulation.
13. Your rights
Under the PDPL you may ask to:
- be told what we hold and why, and get a copy (Art. 13);
- receive your data in a usable format to move it (Art. 14);
- correct or erase your data (Art. 15);
- restrict (Art. 16) or stop (Art. 17) its use, including for marketing;
- object to decisions made only by automated processing (Art. 18). The face check can refuse a sign-up automatically; see section 4 for what you can ask.
You can also withdraw consent at any time (for example to the face check, which may mean the account cannot continue). Apart from closing your account, there is no self-service export or erasure in the app: write to privacy@choozme.com and we will handle your request by hand. We may need to verify your identity, and we may keep some data where the law requires or allows, such as payment records and safety records. We will reply within the period required by UAE law.
If you are not satisfied, you may complain to the UAE Data Office (Art. 24).
14. Changes
We may update this policy when the Platform, our vendors or the law change. We will publish the new version with its version number and effective date and give notice or ask for consent where the law requires.
15. Contact
Privacy contact: privacy@choozme.com (write from the email address of your account so that we can find it quickly)
Operator: ChoozMe
Data protection officer: No data protection officer is appointed