Privacy Policy
1. Who we are
MUAH ("MUAH", "we", "us", "our") operates the MUAH mobile application (the "App"), a marketplace that connects clients ("Clients") with independent beauty professionals ("Service Providers") for makeup, hair, nail and related beauty services.
For the purposes of UK data protection law, the data controller for the personal data described in this policy is:
- Controller: muah-app LTD
- Company number: 17331321, registered in England & Wales
- Registered/operating address: 66 Paul Street, London, EC2A 4NA
- ICO registration number: ZC195084
- Contact for privacy matters: privacy@muah-app.co.uk
Our role in the marketplace. MUAH is an intermediary: we facilitate introductions, bookings and payments between Clients and Service Providers. The Service Providers are independent providers, not our employees or agents, and they deliver the beauty services themselves. We are the controller of your platform and account data (as set out below); the Service Provider is a separate, independent controller of the personal data you share with them to receive their service.
This policy is governed by the laws of England and Wales, and we process personal data in accordance with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
2. Who this service is for
MUAH is intended only for adults aged 18 or over. The App is not directed at children, and we do not knowingly collect personal data from anyone under 18. We check the date of birth you give us at registration and reject registrations that do not meet the age requirement (see section 3), and we will remove accounts we find to belong to under-18s.
3. The personal data we collect
We collect only what we need to run the marketplace safely. Data is deliberately separated by sensitivity: some is held on your public profile (visible to other users for discovery), some is held privately (accessible only to you, and to our systems and moderators where necessary), and the most sensitive categories are held in dedicated, restricted stores.
3.1 Identity and contact details
Full name, email address, phone number, and (for Service Providers) a business/correspondence email and profile photo. Purpose: to create and operate your account, identify you to the people you book with, and contact you about your bookings. Lawful basis: performance of a contract (UK GDPR Article 6(1)(b)).
3.2 Date of birth and age
Your date of birth, which we use to confirm you are 18 or over. Registrations that do not meet the age requirement are rejected, and we run a periodic check that removes accounts which no longer meet it. Your date of birth is stored privately and is not shown on your public profile. Lawful basis: performance of a contract and compliance with our age-restriction obligations (Article 6(1)(b); and our legitimate interest in operating an adults-only service, Article 6(1)(f)).
3.3 Location
Location is handled in graduated steps to protect your privacy:
- Before a booking (public): an approximate location only — your coordinates are coarsened to roughly a 110-metre grid, together with a general service-area label (such as a postcode district). This is what other users see when discovering providers nearby.
- Privately: your precise coordinates and full postcode, used to deliver the service accurately.
- Once a booking is confirmed and paid for: for bookings at a Service Provider's premises, the provider's exact address is revealed to you only once your booking is confirmed and you have paid; and for bookings at your location, your exact address is shared with the provider for that booking only from that point. If a Service Provider accepts a request you have not yet paid for, neither address is shared.
- During a booking: for mobile ("we come to you") bookings, while the provider is actively travelling to you their approximate location is shared with you so you can see them approaching, and their arrival is confirmed by a short-range distance check together with a 6-digit arrival code that you share with them. If a provider has enabled only approximate location, we may ask them to allow Precise Location for the duration of that active booking, so their progress and arrival at your address can be confirmed. For bookings at the provider's premises, arrival is confirmed by the arrival code alone and your location is not used. We do not continuously track your location: location is used only for the specific purposes above — provider discovery, and (for mobile bookings) while a provider is actively en route to you — and tracking stops the moment they arrive.
Purpose: provider discovery, accurate service delivery, and arrival confirmation. Lawful basis: performance of a contract (Article 6(1)(b)).
3.4 Payment information
A payment-provider customer identifier and, for Service Providers, a connected-account identifier and payout/verification status. Your card details are handled and stored by our payment processor (Stripe) and never touch MUAH's servers — we receive only tokens and identifiers, not card numbers. Purpose: to take payment, calculate fees, and pay Service Providers. Lawful basis: performance of a contract (Article 6(1)(b)). When a booking needs a later payment (the remaining balance after your appointment), your card is saved securely with Stripe so it can be charged then, or if you choose to save it at checkout. You can remove saved cards at any time in Settings, except in the two hours before an appointment that will use it.
3.5 Identity verification (Service Providers)
Service Providers may complete identity verification through Stripe Identity, which processes their name, date of birth, address and identity-document images (and may process biometric data derived from an identity document). MUAH receives only the verification outcome and timestamp, not the underlying documents. Purpose: trust and safety, and to meet payment-provider requirements. Lawful basis: performance of a contract and our legitimate interest in a safe marketplace (Articles 6(1)(b) and 6(1)(f)).
3.6 Special-category data (Article 9)
- Beauty attributes: Clients may share their skin-tone range and hair-texture preferences, and Service Providers may share their skin-tone and hair-texture expertise, to improve matching. Because these can reveal information about racial or ethnic origin, we treat them as special-category data under Article 9. They are stored in a restricted, owner-readable store; only a coarse, generalised version is published to support discovery. We do not infer ethnicity or any demographic characteristic from your photographs.
- Condition relied on: your explicit consent (Article 9(2)(a)) — you choose whether to share these attributes, and you can use the App without doing so.
- Health-related information you provide before a service: when you book, you may be asked a short pre-service checklist (for example, allergies, sensitive skin, skin conditions, or eye sensitivity) so the Service Provider can perform the service safely. You are asked not to include medical diagnoses or detailed health information. Where you do provide such information it may amount to health data under Article 9. Purpose: your safety during the service. Condition relied on: your explicit consent (Article 9(2)(a)) — you choose whether to provide any of this information after being told why we ask, and you can leave it blank. This information is shared with the Service Provider assigned to your booking so they can perform the service safely. It is deleted automatically 90 days after the booking ends, or straight away if you delete your account.
3.7 Device and technical data
Push-notification tokens, app-attestation tokens (used to confirm requests come from a genuine copy of our App), crash-diagnostic data (device model, operating-system version, and error information, via Firebase Crashlytics), and your language/locale. Purpose: to deliver notifications, prevent abuse, keep the App stable, and show it in your language. Lawful basis: our legitimate interest in a secure, reliable service (Article 6(1)(f)), and performance of a contract for notifications you have set up (Article 6(1)(b)).
3.8 Content you create
Service-provider portfolio images, in-app chat messages, and reviews. Purpose: to operate the marketplace and let users make informed choices. Lawful basis: performance of a contract and our legitimate interest in a trustworthy platform (Articles 6(1)(b) and 6(1)(f)).
3.9 Marketing preferences
If you opt in, your consent to receive marketing emails, together with the date, time, IP address and policy version at the moment you consented (kept as evidence of consent). Purpose: to send you offers and updates you asked for. Lawful basis: consent (Article 6(1)(a); and the Privacy and Electronic Communications Regulations).
3.10 Records of your permissions
We keep an internal, tamper-evident log of the permissions and acceptances you give — for example when you accept our Terms, acknowledge this policy, or grant or withdraw a consent — recording what you agreed to, when, and from which IP address. Purpose: to demonstrate we handle your data lawfully (accountability, Article 5(2)). Lawful basis: compliance and legitimate interest (Articles 6(1)(c) and 6(1)(f)).
3.11 How you use the App
Information about how you use the App — for example, screens viewed and actions taken — collected as usage and diagnostic events. Purpose: to understand how the App is used, fix problems, and improve the service; this information is analysed only in a privacy-scrubbed, aggregated form. Lawful basis: our legitimate interest in maintaining and improving the App (Article 6(1)(f)).
3.12 Purchases in the App (Service Providers)
If you buy Premium, a Grow your diary pass, Spotlights, insight reports or CSV exports, Apple processes the payment. We receive from Apple the purchase details, not your card: the product, quantity, transaction identifiers, purchase and expiry dates, and whether Apple has refunded or revoked it. We use them to give you what you bought and keep a record of your credits, monthly allowance and pass days, and every change to them. We also keep a count of purchase checks that failed for your account each day, to detect problems and abuse; each count is deleted after 2 days. Purpose: to provide what you bought, handle Apple refunds, and keep financial records. Lawful basis: performance of a contract (Article 6(1)(b)); for the failed-check count and the records kept after account deletion, our legitimate interest in preventing fraud and keeping accurate financial records (Article 6(1)(f)).
3.13 Search and profile activity used for Service-Provider insights
To show Service Providers how they are doing, and to make Spotlights work, we keep the following. None of it stores a Client's name or account identifier.
- Daily counts per Service Provider: how many times their profile was viewed from search, and how many times clients looked for times they don't offer. These are counts only, with no viewer or Client identifiers, and are kept for 400 days.
- Spotlight viewers: while a Spotlight runs, we record each distinct viewer as a pseudonymous code (a keyed hash that we cannot turn back into an account), so a viewer is counted once. These codes are deleted when the Spotlight ends and its views are counted, shortly after the hour. A similar code, used so a viewer is counted once a day in the daily counts, is deleted after 2 days.
- Searches by area: a daily count of client searches in each area of about 5 km square, with no identifiers, kept for 30 days. Service Providers see it as the number of searches near them in the last 7 days. A code used so each browsing session is counted once is deleted after 2 days.
Purpose: insight reports, the Spotlight "no views, you get it back" rule, and showing demand near a Service Provider. Lawful basis: our legitimate interest in providing these features and a fair Spotlight (Article 6(1)(f)).
3.14 Insight reports and CSV exports (Service Providers)
- Monthly insight report. A Service Provider's report is built from their own data: their bookings, earnings, ratings, the counts in section 3.13, and how many of their Clients were new or returning (as numbers, never names). It contains nothing about other Service Providers. Past reports are listed in the App to the Service Provider who owns them, and no one else can see them. Each report is kept for 24 months after it is made and then deleted automatically.
- CSV export. A Service Provider can export a file of their bookings and earnings. It includes each booking's date, reference, service, amounts and the Client's name. We keep a copy for 30 days so the Service Provider can download it again, and then delete it. Once a Service Provider saves the file, that copy is theirs, and they are responsible for it as an independent controller.
Lawful basis: performance of a contract (Article 6(1)(b)). For Clients, the use of your name in a Service Provider's export is based on our legitimate interest in letting Service Providers keep records of their own business, including for tax (Article 6(1)(f)).
3.15 When you last opened the App (Service Providers)
If you are a Service Provider, when you open the App it runs a security check with our servers, and we record the time. We do not record this for Clients. We keep only the most recent time: each new one replaces the last, so this is not a history of your use. We use it for Instant bookings: if a Service Provider has not opened the App for about 7 days, Instant moves to Request, so Clients are not confirmed into bookings with someone who may no longer be checking the App. We also keep a note of any warning we sent about this, and of when and why Instant was moved to Request, together with the version of the Instant booking terms the Service Provider accepted and when. Purpose: to keep Instant bookings reliable for Clients, as described in the Instant booking terms. Lawful basis: performance of a contract — the Instant booking terms the Service Provider accepts (Article 6(1)(b)); and our legitimate interest in Clients being able to rely on bookings confirmed at payment (Article 6(1)(f)). These details are kept on your account and deleted when you delete it.
3.16 Your in-app Notifications
The App keeps a list of Notifications for you: short entries about your bookings and your account (for example, a booking request, a cancellation, a change of time, or a payment that needs your attention). An entry can name the other person on the booking. Purpose: so you can see what happened, and what still needs you to act, even if you missed a push notification. Lawful basis: performance of a contract (Article 6(1)(b)). Notifications are kept for 90 days; one that asks you to act is kept at least until the day after its deadline, if that is later. You can clear an entry yourself unless it still needs you to act. If you delete your account, your Notifications are deleted, and the other person's entries about your bookings stop showing your name.
4. How we use your data and our lawful bases — at a glance
| What we do | Lawful basis |
|---|---|
| Create and run your account; take bookings and payments; deliver and support the service | Contract — Article 6(1)(b) |
| Your Terms acceptance, cancellation-policy acceptance, and Service-Provider licence/insurance declarations and identity verification | Contract / contractual representation — Article 6(1)(b) |
| Matching you using beauty-attribute preferences (special category) | Explicit consent — Articles 6(1)(a) + 9(2)(a) |
| Keeping the platform safe: content moderation, contact-masking, image-safety checks | Legitimate interest — Article 6(1)(f) (not consent) |
| Importing a Service Provider's free/busy calendar to prevent double-booking | Legitimate interest — Article 6(1)(f) (not consent) |
| Security, abuse prevention, crash diagnostics, service reliability | Legitimate interest — Article 6(1)(f) |
| Marketing emails | Consent — Article 6(1)(a) |
| Keeping records to demonstrate compliance | Legal obligation / legitimate interest — Articles 6(1)(c), (f) |
| Premium, passes, Spotlights, reports and CSV exports; credit records | Contract — Article 6(1)(b) |
| Counting profile views, Spotlight viewers and searches by area (no Client identifiers) | Legitimate interest — Article 6(1)(f) |
| Keeping in-app purchase records after account deletion, with your identifier replaced by a pseudonym | Legitimate interest — Article 6(1)(f) |
| Recording when a Service Provider last opened the App (Service Providers only), to move their Instant booking to Request after about 7 days away | Contract — Article 6(1)(b); legitimate interest — Article 6(1)(f) |
| Your in-app Notifications list | Contract — Article 6(1)(b) |
A note on moderation and calendar import. Keeping the marketplace safe, and preventing double-bookings, are things we do under our legitimate interests — they are not optional add-ons you consent to. This means they continue for as long as you use the service, and turning off an optional consent does not switch them off. You do, however, have the right to object to processing based on legitimate interests (see section 7). We have carried out a legitimate-interests assessment for these activities.
Future features. From time to time we may introduce new features. Where a new feature needs additional data or a new permission from you, we will ask you at that point and, where the law requires it, seek your consent before the feature processes your data.
5. Who we share your data with
We do not sell your personal data. We share it with the parties below so the service can work.
Other users. Your public profile (and, once a booking is made, the details needed to complete that booking, with exact addresses only once it is confirmed and paid for — see section 3.3) is shared with the Clients or Service Providers you interact with. Once a booking is under way (the Service Provider or the Client is on the way to the appointment, has arrived, or the service has started), we show the Service Provider the Client's phone number, and for appointments at the Service Provider's own premises we show the Client the Service Provider's number, so you can call each other; we remove it as soon as the booking ends.
Our service providers (processors and other recipients). We use carefully selected suppliers who process personal data on our behalf, or receive it to perform their own service:
| Recipient | What they do for us | Data involved |
|---|---|---|
| Google / Firebase (Google Cloud) | App infrastructure: sign-in, database, cloud functions, file storage, push notifications, abuse prevention (App Check), crash reporting, and analytics | Effectively all platform data; analytics is exported only as a privacy-scrubbed summary |
| Stripe | Card payments, provider payouts (Stripe Connect), identity verification (Stripe Identity), subscriptions | Payment tokens and identifiers, amounts; for verification: name, date of birth, address, identity documents |
| Apple | Subscription and in-app purchase processing (Premium, the Grow your diary pass, Spotlights, reports and CSV exports) and refunds, push-notification delivery, Sign in with Apple, and maps/address look-up | Purchase and subscription identifiers, device identifiers, authentication tokens, and coordinates sent for address look-up |
| SendGrid (via our email tool) | Sending transactional emails (e.g. booking confirmations) | Your email address and the content of the message |
| Google Cloud Vision | Automated safety check of uploaded images | Image content |
| External calendar feeds (chosen by a Service Provider — e.g. Google, iCloud, Booksy) | Reading a provider's free/busy times to prevent double-booking | We fetch the provider's own calendar link; no Client data is sent out |
We put appropriate contracts in place with these suppliers as required by UK GDPR.
Legal and safety disclosures. We may disclose personal data where we are legally required to, or where it is necessary to protect the safety of our users or the public, to prevent fraud, or to establish or defend legal claims.
6. International transfers
Some of our suppliers process personal data outside the United Kingdom (for example, Stripe, Apple, Google and SendGrid operate internationally). Where personal data is transferred outside the UK, we rely on appropriate safeguards — such as UK adequacy regulations, the UK International Data Transfer Agreement / Addendum, or Standard Contractual Clauses — so that your data continues to be protected.
7. Your rights
Under UK data protection law you have the right to:
- access the personal data we hold about you;
- ask us to correct inaccurate data;
- ask us to erase your data ("right to be forgotten");
- restrict or object to certain processing (including processing based on our legitimate interests, and direct marketing at any time);
- request portability of data you gave us; and
- withdraw consent at any time where we rely on consent (this does not affect processing done before withdrawal).
How to exercise them in the App:
- Delete your account and data. You can delete your account from the App's privacy settings. This runs a full erasure process: we cancel any upcoming bookings on the same terms as if you had cancelled them yourself (see our Terms), remove your services, availability, portfolio images and files, replace the text of the messages you sent with "[Message from deleted account]" and remove your name and written comments from the reviews you left (so the other person's history stays intact but no longer shows who you are), replace your identifier in our Glam points records with a pseudonym, and delete your account and profile — including your special-category data, condition checklists, permission logs, Notifications and notification tokens.
- Booking records are kept, because the other person's history and our financial records need them. We remove your name, profile photo and your address or location from each one. The record still holds the internal account number your account had, so it is pseudonymised, not anonymous. If a payment on a booking is disputed with a bank, we keep that booking's exact address while the dispute is open and for about 18 months after it closes, as evidence.
- Safety and problem reports are kept, with your identifier replaced by a pseudonym, so that safety concerns and disputes can still be handled.
- Some other information may be retained where the law requires (for example, limited transaction records). For Service Providers, deleting your account also deletes your credits, allowance and pass days, your Spotlights, your daily counts, your insight reports and any stored CSV exports. Records of your in-app purchases are kept as financial records, and so that a later Apple refund can be handled, but your account identifier in them is replaced with a pseudonym.
- Get a copy of your data. You can request an export of your personal data from within the App. To protect other people, the export leaves out information about them that is not yours to receive: it never shows who made a report about you, and a Service Provider's export does not include a Client's address or payment details from their bookings.
- Manage consents. You can withdraw marketing consent, and any optional feature consents, at any time in settings.
You also have the right to complain to the Information Commissioner's Office (ICO) — ico.org.uk — though we would welcome the chance to resolve your concern first: privacy@muah-app.co.uk.
8. How long we keep your data
We keep personal data only for as long as we need it to provide the service, meet our legal obligations, and resolve disputes. In general, your account data is kept for as long as your account is active and is erased when you delete your account (subject to the limited exceptions in section 7). Certain records are kept for shorter, fixed periods — for example, transactional emails, security and moderation records, and payment-event records are each kept for a limited time and then automatically deleted.
For Premium, purchases and provider insights we keep these periods:
- insight reports: 24 months after each report is made;
- stored CSV export files: 30 days after the export;
- daily profile-view and missed-booking counts: 400 days;
- area search counts: 30 days;
- Spotlight viewer codes: until the Spotlight's views are counted, shortly after its hour ends; daily view and search codes: 2 days;
- the daily count of failed purchase checks: 2 days;
- in-app purchase records: 6 years after the end of the financial year (which ends on 31 March) in which the purchase was made or, if Apple later refunds it or reverses a refund, in which the latest of those took place, then deleted; on account deletion your identifier in them is replaced with a pseudonym.
For other records we keep these periods:
- in-app Notifications: 90 days; one that asks you to act is kept at least until the day after its deadline, if that is later;
- the pre-service condition checklist (section 3.6): 90 days after the booking ends;
- a booking's exact address, where a payment on it is disputed with a bank: while the dispute is open and for about 18 months after it closes;
- booking records: 6 years after the end of the financial year (which ends on 31 March) in which the booking's last payment or refund took place, then deleted, together with the records linked to it. We keep a booking longer only while something about it is still open: a payment dispute, an unresolved charge or refund, a report about it that is still within its own period, or a legal hold;
- records under a legal hold (kept when a booking is, or may become, part of a legal claim, investigation or request from an authority): kept until the hold is lifted, then deleted with the booking on the normal schedule. They still show which accounts took part, even if one of them has since been deleted, because a claim cannot be answered without knowing who was involved;
- the time a Service Provider last opened the App (section 3.15; Service Providers only): only the latest time is kept, and it is deleted with the account;
- entries in our moderation review queue (flags raised by our automated safety checks, such as on messages and images, for a moderator to review): 18 months after each entry is made, then deleted automatically. If you delete your account, an entry about you keeps this end date, with your identifier replaced by a pseudonym.
9. How we protect your data
We use technical and organisational measures appropriate to the risk, including: encryption in transit (HTTPS/TLS) and at rest; strict access controls so private data is readable only by you and, where necessary, our systems and trained moderators; secure device storage (Keychain) for sensitive values on your phone; app-attestation and rate-limiting to prevent abuse; and identity checks on our internal task processing. No system is ever completely secure, but we work to protect your data and to detect and respond to incidents.
10. Automated processing
We use automated checks to keep the platform safe — for example, scanning uploaded images for unsafe content and masking contact details in messages to discourage off-platform contact. These checks support human review; they do not make decisions that produce legal or similarly significant effects about you without human involvement.
11. Changes to this policy
We may update this policy from time to time. When we make significant changes we will update the version number and "last updated" date, make the new version available in the App, and — where appropriate — ask you to acknowledge it. Your continued use of the App after an update means the current version applies to you.
12. Contact us
Questions about this policy or your data:
- Email: privacy@muah-app.co.uk
- Address: 66 Paul Street, London, EC2A 4NA