Privacy Policy
Confirmed (operated by Razaq Ltd, a company registered in England and Wales, company number 17057410)
Razaq Ltd is registered with the Information Commissioner's Office (ICO), registration number ZC103225.
What changed — October 2026
Section 3 now lists every task Google's Gemini AI model performs: besides planning each turn and reading photos, it runs short checks on a message (for example whether it concerns someone else, or is sensitive), writes the one-line note the business sees on each conversation, and writes the reply when OpenAI is unavailable; OpenAI, in turn, plans a turn when Gemini is unavailable. The photo tables now name day spas, and section 2 and the retention table in section 6 say that a record made before 1 October 2026 may hold a nail colour or pattern, or hair details read from a covered head.
What changed — September 2026
Photos. When you send a photo to a hair, nail or beauty salon, a barbershop or a day spa whose owner has chosen that business type, it is now read by Google's Gemini AI model, and a short form of style details, each picked from a fixed list, is saved with your enquiry. The photo itself is not stored. At the same moment a second look checks it for writing, for signs of a condition and for whether the head is covered: a photo of skin, with writing or with a possible condition is not described at all — only that kind of photo is recorded, and where the head is covered nothing about hair is recorded. No nail colour or nail pattern is recorded. Photos sent to clinics and every other kind of business are not sent to any AI model. A record made before 27 September 2026 may instead hold one short sentence about the photo, and one made before 1 October 2026 may also hold a nail colour or pattern, or hair details read from a covered head; both are deleted with the enquiry. "Photos you send" in section 2, the AI table in section 3 and the retention table in section 6 are updated.
What changed — August 2026
We now name every AI provider that sees your data, and say plainly what each one receives — including that our planning model is sent the customer name and phone number in a conversation, and that the salon-facing AI Consultant sends recent customer messages to OpenAI.
We have replaced the old blanket claim that data is kept for 12 months. The honest position, set out in the retention table below, is that most conversation and booking data is kept for as long as the salon keeps its account, and is deleted on request or when the account ends.
We have also added the channels the product now covers (WhatsApp, Instagram, SMS and the AI phone line), corrected the list of providers we use, and stopped implying that your data stays in the UK or the EU. It generally does not.
1. Who We Are
Confirmed is an AI front desk for service businesses ("salons" or "business customers"). It answers messages on a salon's website chat, WhatsApp, Instagram and SMS, answers its phone line, takes bookings, and can take a deposit. This policy explains what happens to personal data at each of those points.
Controller for end-customer data: the salon whose chat, inbox or phone line you are using is the controller for your personal data. Razaq Ltd acts as its processor.
Controller for salon-owner account data: Razaq Ltd is the controller for information about salon owners and their staff accounts.
We have not appointed a Data Protection Officer, as we are not required to. Data protection enquiries go to privacy@razaq.ai.
2. What Personal Data We Collect
From end customers
We handle the same kinds of data whichever channel you use — the salon's website chat widget, WhatsApp, Instagram direct messages, SMS, or the AI phone line:
- Contact details: name, phone number (stored in full international format), email address
- Channel identity: the WhatsApp number, Instagram account or phone number you message from, so the salon can reply on the same channel and recognise you next time
- Booking information: service requested, date and time, your notes, and your booking history with that salon
- Conversation content: the messages you exchange, plus any notes salon staff add to the conversation
- Photos you send: see below
- Payment information: deposits and payments are processed by Stripe, with the salon as the merchant. We do not see or store your card details. We keep a reference to the booking and the payment.
- Technical data: IP address and browser or device type. IP addresses in our access logs are shortened before they are stored, and the keys we use for rate limiting are hashed rather than kept as raw numbers or addresses.
Phone calls
Calls to the AI phone line are recorded by our voice provider (Retell AI). Confirmed itself does not store the audio: what is said is turned into text and kept as a transcript in the same way as any other conversation, and the calling number is kept in our record of the call. The audio recording is held by Retell AI under its own retention arrangements. Because calls are recorded, callers must be told — the AI greeting states that the caller is speaking to an AI assistant and that the call may be recorded, and salons must not disable or replace that notice.
Photos you send
You can send a photo into a conversation — usually a style reference. We do not store the photo itself. What happens next depends on the kind of business you are messaging:
- Hair, nail and beauty salons, barbershops and day spas whose owner has chosen that business type: the photo is sent to Google's Gemini AI model twice, at the same moment: once to fill in a short form about the style it shows, and once to check it for any writing, for any mark on the nails, skin, scalp or hair themselves, and for whether the head is covered. For that check the model copies out any words it sees in the picture; they are used only to decide that the photo is not described, and are never saved. Every answer on the form is picked from a fixed list: for hair, the colour, length, cut and texture; for nails, the shape and length, and a plain glossy, matte or chrome finish only on nails the check sees as polished (no nail colour is recorded, and no pattern such as nail art, glitter or a French or ombré finish); for brows, the shape and tint; for lashes, the style and tint. Those style details are saved with your enquiry so the business's team can see them, and the photo is then discarded. The form has no space for words, so it cannot record your face, your age, your skin, your religion or ethnicity, anything you are wearing, any words in the picture, a price, a diagnosis or whether a treatment suits you — those are for the business to confirm. If the photo shows skin, might show a condition of your hair, scalp, skin or nails, or has any writing in it (a caption, a label, a note, a screenshot), none of it is described: we record only that kind of photo was sent. If your head is covered (a scarf, hijab, turban, hat or cap), nothing about hair is recorded. The assistant's reply to you may repeat the style details, and that reply is part of the conversation transcript like any other message. A record made before 27 September 2026 may instead hold one short sentence the model wrote about the photo, and one made before 1 October 2026 may also hold a nail colour or pattern, or hair details read from a covered head; both are deleted with the enquiry.
- Clinics and every other kind of business — and a salon, barbershop or day spa whose owner has not yet chosen its business type: the photo is not sent to any AI model and is not stored. The assistant tells you it cannot open photos, and the business sees only that a photo was sent. The same happens if a conversation, or the salon's day, has already sent more photos than a set limit.
Salons must not ask customers for health information through the Platform. Please do not send anything more than you need to for the booking.
From salon owners and staff
- Name, email address, phone number
- Business name, address and website
- Subscription and billing information, handled through Stripe
- Payment account setup: to take deposits, you complete Stripe's own onboarding directly with Stripe
- Calendar data, where Google Calendar, Outlook or an iCal feed is connected
- Business configuration: services, opening hours, branding, and the answers you give the AI to use
- Content imported from your public website when you set the account up. This import reads your website only; it involves no customer data.
3. How We Use Your Data
End-customer data
| Purpose | Legal Basis |
|---|---|
| Answering your messages and calls, and taking your booking | Contract (taking steps at your request) |
| Sending booking confirmations, reminders and changes | Contract / legitimate interests (service delivery) |
| Taking a deposit or payment where the salon requires one | Contract |
| Keeping your history with the salon so it can serve you | Legitimate interests (service delivery) |
| Follow-up messages after your appointment, including review requests | Legitimate interests, subject to your right to opt out (see section 8) |
| Preventing fake bookings, abuse and fraud, and keeping the service secure | Legitimate interests |
| Keeping records of bookings and payments for tax and accounting | Legal obligation |
Salon-owner data
| Purpose | Legal Basis |
|---|---|
| Providing and managing your Confirmed account | Contract |
| Billing and subscription management | Contract |
| Service communications about your account | Contract / legitimate interests |
| Reporting and insights about your own salon's performance | Contract |
| Platform security and abuse prevention | Legitimate interests |
AI processing — which providers see what
Confirmed is built on AI models run by other companies. To answer a message, the relevant part of the conversation is sent to them. This is the part of our processing customers most often do not expect, so we set it out in full:
| Provider | What it receives | What it is used for |
|---|---|---|
| Google (Gemini) | The conversation turn, including anything the customer types, such as their name or phone number, and, where known, the name already held for the customer. A phone number already on file is not sent — only whether there is one. | Working out what the message is asking for and producing a plan of what to do next |
| Google (Gemini) | A photo the customer sends to a hair, nail or beauty salon, a barbershop or a day spa whose owner has chosen that business type — never to a clinic or any other business | Filling in a short form of style details about the photo, each picked from a fixed list, saved with the enquiry; and a second look that checks the photo for writing, for signs of a condition and for whether the head is covered, so that such a photo is not described and a covered head's hair is not recorded. The photo itself, and any words the check copies out of it, are not stored. |
| Google (Gemini) | The customer's message (and, when they are asked which booking they mean, those bookings: service, day, time and whom each is for); for the conversation note, recent messages from both sides, with phone numbers and email addresses masked in the customer's own messages; when OpenAI is unavailable, what OpenAI would receive | Short checks (for example whether the message concerns someone else, or is sensitive); the one-line note the business sees on each conversation; writing the reply when OpenAI is unavailable |
| OpenAI | The conversation content, including the style details recorded from a photo sent to a hair, nail or beauty salon, barbershop or day spa (never the photo itself) | Writing the wording of the reply; planning a turn when Gemini is unavailable |
| OpenAI | Booking and performance figures for the salon | Producing the salon's insights report |
| OpenAI | A snapshot for the salon's AI Consultant that includes up to ten recent customer messages word for word. Phone numbers and email addresses in that snapshot are masked; names are not. | Answering the salon owner's questions about how their salon is doing |
The AI never carries out an action itself. It reads the conversation and proposes a plan; our own code checks that plan and then performs the booking, the payment or the message. A member of salon staff can take over any conversation at any point.
Automated checks that can refuse a request
We run automated abuse controls: obviously invalid or throwaway phone numbers are rejected, and there are caps on how many bookings can be made from one phone number or IP address in a period. These can stop a booking going through. They are anti-abuse measures rather than decisions about you, and a human can always override them — contact the salon, or us, and a person will look at it.
We do not use your data for automated decision-making that produces legal or similarly significant effects, and we do not sell personal data.
Anonymised, aggregated statistics
We record one summary per salon per day — figures such as diary utilisation, no-show rate, repeat-client rate, confirmed revenue and number of bookings. That summary contains no customer data and stays within that salon's own area of our system. We do not combine salons' data today.
We reserve the right to produce and use anonymised, aggregated statistics derived from use of the Platform — for example to benchmark performance, and to run and improve the service — including after an account ends. Such statistics never identify a salon or any individual, and are not personal data. The corresponding right for business customers is set out in our Terms of Service.
4. Who We Share Your Data With
We use the following providers (sub-processors). Some are used only where a salon turns the relevant feature on.
| Provider | Purpose | Location | Safeguard |
|---|---|---|---|
| Google Cloud / Firebase (Firestore, Storage) | Database, file storage and account authentication | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Google Gemini API | AI planning, message checks, conversation notes, photo reading and fallback replies (see section 3) | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| OpenAI | Reply writing, insights reports, AI Consultant | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Meta Platforms | WhatsApp and Instagram messaging | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Twilio | SMS messaging and voice telephony | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Retell AI | Running the AI phone line | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Railway / Render | Hosting for the voice service | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Stripe (including Stripe Connect) | Deposits, payments and subscription billing | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Resend | Transactional email delivery | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Vercel | Application hosting | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Sentry | Error monitoring. EU-hosted, and configured to strip personal data before it is sent. | EU (Germany) | EU hosting; no transfer to the USA |
| Firecrawl | Reading a salon's public website during setup. No customer data. | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Square / Timely | Optional per salon: syncing with the salon's existing booking system. Receives customer name, phone number and email address. | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Google Calendar / Microsoft Outlook | Optional per salon: writing appointments into the salon's own calendar, including customer name and phone number. | USA / global | UK IDTA / UK Addendum to the EU SCCs |
| Amazon Web Services (S3) | Fallback storage for uploaded files | USA / global | UK IDTA / UK Addendum to the EU SCCs |
We may also disclose data where required by law, court order or a regulator.
5. International Data Transfers
Your salon's database and uploaded files are stored in the United Kingdom — Google Cloud's London region (europe-west2). Our error monitoring is hosted in the EU (Germany). However, most of the providers listed above are based in the United States or route data globally, so parts of a conversation — including message content sent to the AI providers — are processed outside the UK.
Where data leaves the UK we rely on the UK International Data Transfer Agreement (IDTA), or the UK Addendum to the EU Standard Contractual Clauses, in our contracts with those providers. We are happy to discuss the arrangements for a specific provider with any salon that asks.
6. How Long We Keep Your Data
Some records are deleted automatically after a fixed period. The rest are kept while the salon's account is open, and deleted on request or when the account ends.
| Data | How long we keep it | Automatic? |
|---|---|---|
| SMS message logs | 24 hours | Yes |
| Late SMS replies | 24 hours | Yes |
| Duplicate-message checks for WhatsApp and Instagram | 5 minutes | Yes |
| Waitlist offers | 24 hours | Yes |
| Sign-in states for connecting an integration | 10 minutes | Yes |
| Rate-limiting counters | 24 hours | Yes |
| Booking risk records | 180 days | Yes |
| Leads imported by a salon | 18 months | Yes |
| Conversation transcripts, across every channel | While the account is open | No |
| Notes staff add to a conversation | While the account is open | No |
| Bookings and booking history | While the account is open | No |
| Customer records (name, phone, email) | While the account is open | No |
| Channel identities (WhatsApp, Instagram, SMS, phone) | While the account is open | No |
| Call records, which include the caller's number | While the account is open | No |
| Call audio | Not stored by Confirmed | — |
| Photos sent into a conversation | Not stored — only the style details are kept, with the enquiry (see the next row) | — |
| Style details of photos sent to a hair, nail or beauty salon, a barbershop or a day spa (and, for records made before 27 September 2026, a one-sentence description; records made before 1 October 2026 may also hold a nail colour or pattern, or hair details read from a covered head), kept with the enquiry | Up to 18 months, with the enquiry | Yes |
| The same details, where the assistant's reply repeated them | With the conversation transcript — while the account is open | No |
| Daily salon summary figures | While the account is open | No |
| SMS opt-outs (STOP) | Kept indefinitely, on purpose — see section 8 | No |
| Booking and payment references | 7 years, for tax and accounting | No |
| Salon account data | While the account is open, then deleted in line with our Data Processing Agreement | No |
"While the account is open" means we keep the data until the salon asks us to delete it, until you ask and the salon agrees, or until the salon closes its account. Stripe keeps its own record of payments under its own retention policy. Where an automatic deletion rule is not yet switched on in a particular environment, the data is covered by the position above rather than deleted on the shorter timetable.
7. Your Rights
Under UK GDPR you have the right to:
- Access — get a copy of the personal data held about you
- Rectification — have inaccurate or incomplete data corrected
- Erasure — have your data deleted
- Restriction — have processing limited in certain circumstances
- Portability — receive your data in a portable format
- Object — object to processing based on legitimate interests, including marketing
- Withdraw consent — where processing relies on consent
How to make a request
If you are a customer of a salon, that salon is the controller of your data. The quickest route is to ask the salon directly. If you contact us instead, we will pass the request to the salon and help them act on it — in most cases we can carry out the deletion or export ourselves once the salon confirms.
Write to privacy@razaq.ai. We will acknowledge your request and respond within one month. If a request is complex, or if you have made several, we may extend that by up to two further months and will tell you why within the first month. We may ask you to confirm the phone number or email address the conversation used, so that we return the right person's data.
If you are unhappy with our response you can complain to the Information Commissioner's Office: ico.org.uk | 0303 123 1113.
8. Cookies, Tracking and Marketing Messages
Cookies
The Confirmed chat widget sets no cookies. It keeps your conversation for the length of your visit to the page. The salon dashboard uses your browser's own storage — not cookies — to keep staff signed in and to remember display preferences. Neither the widget nor the dashboard uses advertising or tracking cookies.
Our marketing pages can be configured to use Google Analytics to count visits. Where that is switched on, Google sets its own analytics cookies in your browser; where it is not, no analytics cookies are set.
Marketing and messaging
Most messages we send on a salon's behalf are service messages: confirmations, reminders and changes to a booking you asked for. Where a salon sends anything promotional, the salon is responsible for having a lawful basis to do so under UK GDPR and PECR.
You can stop SMS at any time by replying STOP, and start again by replying START. We honour STOP as soon as we receive it. We keep opt-out records indefinitely and by design: the suppression list is how we know never to message you again, so it survives even when other data about you is deleted. It holds only what is needed to recognise the number and that it opted out.
9. Children's Data
Our services are not directed at children under 13, and we do not knowingly collect their personal data. If you believe a child has provided us with personal data, contact privacy@razaq.ai and we will delete it promptly.
10. Security
The measures we actually have in place:
- Encryption in transit (TLS), and encryption at rest provided by our hosting and database providers
- Application-level AES-256-GCM encryption of the tokens that connect a salon's messaging channels and integrations
- Complete separation between salons: every record lives under a single salon, and a request is always checked against the signed-in account rather than any salon identifier the browser supplies
- No direct database access from browsers or apps — our database rules deny all client access, so every read and write goes through our server
- Dashboard access requires a verified sign-in token
- Logging that strips personal data, enforced by an automated test that fails the build if it is broken
- IP addresses shortened before they are written to access logs
- Cryptographic, timing-safe verification of incoming webhooks from Meta, Twilio and Stripe
- Signed, single-use states when connecting an integration
- Defences against requests being redirected to internal systems when a salon supplies a URL
- Rate limiting keyed on hashed — never raw — phone numbers and IP addresses, plus caps that limit booking abuse
We do not hold ISO 27001 or SOC 2 certification and we do not claim one. No system is completely secure. If there is a breach that poses a risk to your rights and freedoms we will notify the ICO within 72 hours and affected individuals without undue delay.
11. Changes to This Policy
We update this policy as the product changes. When something material changes we update the date at the top and summarise the change in the "What changed" note, so you can see what is different without re-reading the whole document.
12. Contact Us
Razaq Ltd (company number 17057410, England and Wales)
Data protection: privacy@razaq.ai
Contracts and terms: legal@razaq.ai
Anything else: hello@razaq.ai
Website: razaq.ai
Business customers can find the processing terms that apply between us in our Data Processing Agreement. This policy and any dispute about it are governed by the laws of England and Wales.