Privacy Policy
Last updated: 2026-11-11 · OpenSassy is operated by ANDUMA Intelligence Group Ltd (Company No. 17180471)
1. Who we are, and our two roles
OpenSassy is a product of ANDUMA Intelligence Group Ltd, a company registered in England and Wales.
We hold two distinct roles, and which one applies depends on who you are:
- Controller — for our own users: business owners and staff who sign up to OpenSassy, people using the Sassy client app for their Passport account and platform discovery, visitors and leads on the-sassy.com, and any data about the founder/platform itself. We decide why and how this data is processed, and this policy is about that role.
- Processor — for client and staff records a business customer manages through OpenSassy. The business decides how those records are used and is their controller; we process them on its behalf under our Data Processing Agreement. This is separate from our controller role for platform user accounts. For records held on a business's behalf, look to that business's privacy notice first. The data-flow detail below also describes our processing for it.
Contact: hello@the-sassy.com
2. What data we collect
Account data (business owners, staff and client Passport holders):
Name, email, phone, password (hashed) or Supabase-managed authentication, business/organisation details. Collected at sign-up.
End-customer data (your business's clients, where we act as processor):
Name, email, phone, booking history, appointment notes, consent records, marketing preference. Collected when a client books, signs up for their own account, or is imported by the business.
Voice call data:
If a business enables the AI voice receptionist ("Ara"), inbound calls are answered, recorded, and transcribed to identify the caller's booking intent. This includes the caller's phone number and the audio/transcript of the call.
Ara phone voice uses xAI (Grok realtime voice). This is separate from Sassy client live voice, which uses OpenAI, and the personal Sassy In AI call test described in §4c.
Chat content:
Messages sent to our AI assistant ("Sassy"), by business owners/staff, by their clients, or by guests on the-sassy.com. This may incidentally contain personal data you mention in conversation (e.g. a client's name in a request).
On the website (salon booking pages and web client chat), Sassy sends your messages, recent conversation, text attachments and the booking details needed for your request to Anthropic (Claude). If Anthropic is unavailable, the request goes automatically to OpenAI and, if that is also unavailable, to xAI; none is used to get around a refusal. Images and PDFs are read only by Claude.
Sassy client discovery, maps and voice:
You can browse as a guest and enter a town, postcode or area instead of sharing device location. If you allow foreground location, we use the current coordinates and reported accuracy to find nearby places while the search screen is active. We do not build a movement history. Search locations and queries are sent to our search service; external place searches send the search area and query to Google Maps. A UK postcode you enter may be resolved by Postcodes.io. Some town and city results use GeoNames data.
Typed AI discovery sends your message and selected town or area labels to Anthropic (Claude). In app versions that show the AI notice dated 2 October 2026 and after you agree to it, if Anthropic is unavailable (for example out of credit or down) the same message goes automatically to OpenAI (GPT-6.1 Sol) and, if that is also unavailable, to xAI (Grok 4.7) — only one of them answers each message, and none is used to get around a refusal. Older app versions keep using Anthropic only. Live voice uses OpenAI for conversation and discovery reasoning. If you ask live voice to prepare a visit, the request and the relevant spoken conversation are also sent to the same typed chat chain through the signed-in confirmation flow. Structured device coordinates are excluded from the chat model input. Google Maps listings appear in attributed result cards and are not sent to the language model. Opening an external website or Maps link is subject to that service's own privacy notice.
Public web search (opt-in): Sassy can search the public web with Tavily only after it shows you a notice in the chat and you reply “Use web search”. Tavily then receives a short search question that Sassy writes, which can include a place you asked about. We do not send your full chat history, structured device coordinates or account identifiers, and a heuristic screen blocks queries that look like credentials, contact details or IDs — this screen reduces risk but is not a guarantee. Public search does not connect to private accounts such as email or university systems. Say “No” or “Stop web search” at any time; ordinary discovery and bookings keep working without it. Tavily handles searches under its own privacy policy and terms: it says queries may be used to improve its responses and shared with third-party search indexes, and it keeps data for as long as it needs rather than for a fixed period, so we cannot promise a deletion deadline for Tavily.
Live voice starts only after you choose Talk to Sassy and agree to the applicable AI notice and microphone permission. While it is on, your microphone audio and words are sent continuously to OpenAI, which replies with an AI-generated voice. You can interrupt naturally. Tap End conversation, leave the conversation screen or put the app in the background to stop the microphone. What you and Sassy say appears in the conversation; signed-in transcripts may be saved with your chat history. Preparing a visit does not book, change or pay for it: you must review and approve the request in the app. Ordinary search and typing remain available.
Where dictation is available, OpenAI transcribes a recording you start into a draft you can edit before sending. Optional playback sends reply text to OpenAI to generate speech. These separate controls do not start a live microphone session.
The Google Maps SDK also processes technical information such as IP address, device and app metadata, SDK identifiers, usage and diagnostic information to provide and improve maps. Its processing is described in the Google Privacy Policy, which applies to the Google Maps features.
Payment data:
Stripe is our payment processor (and Stripe Connect for businesses taking their own payments). We never see or store full card numbers — only Stripe-tokenised metadata, customer email/name for receipts, and transaction records.
Usage data:
Pages visited, features used, timestamps, IP address, browser type, collected via server logs. We do not use cookies or third-party analytics/advertising trackers — see our Cookie Policy for the full, code-audited list of what's actually stored in your browser (it's localStorage, not cookies).
Guest/lead data:
If you chat with Sassy on the public landing page before signing up, we keep the conversation and, if you give it, your email, to follow up.
Communications:
Emails and support messages you send us.
3. Lawful basis for processing
Contract performance: Running your account, providing bookings/CRM/payments, answering calls — the core service you (or your business) signed up for.
Consent: Account sign-up captures a specific, versioned choice for AI processing (`ai_processing`). Guest discovery asks you to agree in the current session before sending messages to AI; you can choose ordinary Search instead. Location and microphone access require their own device permissions. Marketing communications are opt-in and can be withdrawn at any time.
Legitimate interests: Keeping the platform secure, detecting fraud/abuse, and personalising the AI assistant's memory of your business (minimised — see retention below). We've assessed that this doesn't override your rights.
Legal obligation: Retaining billing records as required by UK tax law.
4. The AI behind OpenSassy
OpenSassy's AI assistant ("Sassy") and voice receptionist ("Ara") are built on third-party large language model providers. To generate a response, the relevant message content (and necessary business context) is sent to one of these providers:
- TypeSafe (Jev) — optional fast navigation routing for business and client Sassy. Live voice and typed chat have separate notices and choices naming TypeSafe; agreeing to voice does not enable typed routing. Where typed routing is available and you allow it, a short, filtered command and limited context (your role and a fixed screen key) may be sent to decide whether you want to open a screen, scroll or go back. Earlier typed messages, raw audio, attachments, business records and account identifiers are not attached to that typed request. We try to mask common identifiers and withhold requests detected as sensitive; filtering does not guarantee anonymous text. TypeSafe cannot approve, book, send or charge anything. You can decline or withdraw typed routing in the Sassy chat where it is offered or in Account on the web. Withdrawal applies from your next message, and you can keep using normal Sassy. Located in the United States. Our account has zero data retention for request and response content; operational billing and usage telemetry remains. OpenSassy's own diagnostic logs are separate — see §7.
Optional Sassy In AI fast personal reads are separate from screen navigation and off until you explicitly opt in by text. Text FAST ON to read the notice, then YES FAST READS within 24 hours; FAST OFF withdraws it. Only your current short, filtered SMS request is sent to TypeSafe to choose whether you want to read all your own upcoming reminders or saved preferences. Your phone number, account/member IDs, conversation history and saved reminder/preference details are not attached. Filtering does not guarantee anonymous text. The actual details are read by OpenSassy and returned through our existing text service; TypeSafe cannot create, change, approve or send anything. Memory preferences are read only while your memory choice remains on. Other requests continue through normal Sassy, and you can keep texting without this option. Withdrawal and newer instructions are checked before a fast result is saved or delivered. Diagnostic timings and action labels exclude message/record content. This is an SMS feature, separate from calls or recorded voice notes. No member is enabled by an older AI notice, a business routing choice or an administrator acting for them.
- Anthropic (Claude) — our primary AI brain for business and client chat, analysis, and building features. For Sassy In AI it answers members’ texts first, and its own web-search tool is the first used when Sassy searches the web or reads a page for a member (§4c). Located in the United States.
- xAI (Grok) — the brain behind the voice receptionist, and Grok 4.7 as the second automatic backup for business and client typed chat when both Anthropic and OpenAI are unavailable (for clients, only in app versions whose AI notice names it and after you agree). On the website (salon booking pages and web client chat), when both Anthropic and OpenAI are unavailable, a Grok model answers automatically. For Sassy In AI it is the second backup for texts, and its own web-search tool is used for a member’s web search when Anthropic’s and OpenAI’s fail (§4c). Located in the United States.
- Google (Gemini) — image analysis and memory/embeddings. If Google Gemini is unavailable, photo analysis uses OpenAI, then Anthropic. Located in the United States.
- OpenAI — reasoning for the founder’s own tools, the fallback voice that reads Sassy’s replies aloud when ElevenLabs is not enabled, Sassy client live conversations, discovery reasoning, optional dictation and spoken replies, and GPT-6.1 Sol as the first automatic backup for business and client typed chat when Anthropic is unavailable (for clients, only in app versions whose AI notice names it and after you agree, and automatically on the website: salon booking pages and web client chat). For Sassy In AI it is the first backup for texts when Anthropic is unavailable, and its own web-search tool is used for a member’s web search or web page when Anthropic’s fails (§4c). Located in the United States.
- ElevenLabs — text-to-speech for Sassy’s spoken replies, where enabled. Located in the United States.
- Tavily — web search, used by the assistant on our public site, for research tasks, and for Sassy client public web search only after you opt in (§2). For Sassy In AI it is the backup, used only when the AI provider’s own web-search tool fails (§4c). See Tavily’s privacy policy and terms. Located in the United States.
- Moonshot AI (Kimi) — long-context analysis. Located in the People’s Republic of China.
Several of these providers publish business or API terms saying they do not train their models on data sent through those services, but we have not completed a contractual verification of every provider, so we do not promise that no provider uses your data for training. In particular, Tavily’s own policy and terms allow search input and output to be used to improve and train its AI functionality. Sending or making personal data accessible to a recipient outside the UK can be a restricted international transfer — see §6.
4a. Google user data
Some OpenSassy features connect to a Google account through Google sign-in (OAuth). This section describes exactly what we access, how we use it, where it is stored, who it is shared with, and how to disconnect. OpenSassy’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Business Google Calendar connection (business owners and admins)
If you connect your business’s Google Calendar from OpenSassy settings, we request the Google Calendar events scope (not full calendar access). The scope allows reading and managing events on your calendars. What OpenSassy actually does with it today: Sassy reads events in the date range you ask about (title, start and end time, description) to answer questions about your day, and creates appointment events when you ask her to. Creating an event is a write action: Sassy shows you what she will do first and nothing is written to your calendar without your approval. Sassy does not currently edit or delete your Google events; you do that in Google Calendar. We do not read your contacts or any other Google data under this connection.
We store the OAuth access token and refresh token Google issues, the token expiry time and the Google account email address, in our database (Supabase, EEA region) alongside your business record. Tokens are protected by our database’s encryption at rest and access controls; we do not apply a separate application-level encryption to them. We keep no separate copy or mirror of your calendar: events are read from Google when needed. The event details Sassy read or created in a conversation can remain in that conversation’s stored record and in approval records, under the retention periods in §7.
Google Calendar as your appointment diary (Ara phone bookings)
If you choose Google Calendar as the diary our voice receptionist Ara books into, we request the Google Calendar events and free/busy scopes. We read free/busy information and existing events to offer times, and we create appointment events whose title and description contain the service, the time, the caller’s name and phone number as given on the call, and any notes. The refresh token is stored on your business record in our database (same protections as above). When you disconnect this diary we delete the stored token and ask Google to revoke it.
Business Gmail, Google Business Profile and Google Ads connections
These optional business connections require separate setup and Google permissions before they become available. If enabled and you connect Gmail, we request read-only and compose permissions: Sassy can find and read messages, create drafts and send an email you approve. Message headers, excerpts and plain-text bodies may be included in your conversation with Sassy. Attachments are not downloaded by this connection. If you connect Google Business Profile, we request business management permission to read your managed accounts, locations and reviews, and publish review replies you approve and update the business website, primary phone or weekly hours after your approval. If you connect Google Ads, we request the Ads permission; OpenSassy currently uses it only to read accessible accounts and campaign performance, including spending, clicks and conversions. This connector cannot create campaigns or change budgets.
Each connection belongs to your business and uses the account you authorise, never the founder’s account. Owners and admins of that business can use the connection, so choose an account appropriate for shared business access. We also request and store that account’s email address so you can see which account is connected and approve actions for that account. These three connectors encrypt access and refresh tokens at the application level before storing them in our database. We retain Google action identifiers, request hashes and outcome records to prevent duplicate sends; we do not keep a separate inbox mirror. Disconnecting removes stored tokens and pending sign-in state but keeps action receipts. It does not delete messages or drafts already stored in Gmail, or replies already published on Google. Data included in Sassy conversations is handled by the AI providers and retention periods described below. Gmail data is not used for advertising or audience targeting.
Founder tools (Gmail and Calendar, read-only)
The OpenSassy founder’s own Google account can be connected to the founder console with read-only Gmail and Calendar scopes and the account email address. This connection is only ever to the founder’s own account, is used to read recent messages and calendar events into the founder’s private assistant, and is never offered to businesses or clients. Tokens are stored as described above.
How Google data reaches our AI providers
When Sassy answers a question or acts on your connected Google services, the relevant calendar details, email headers and text, Business Profile details and reviews, or Ads performance results are included in the conversation sent to the AI providers listed in §4 (primarily Anthropic, with the fallbacks named there), as with any other business data you ask Sassy about. We use Google data only to provide and improve the features you asked for. We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI models. The providers’ own handling of data sent to them is described in §4, including what we have and have not verified about their training terms. Human access to Google data by our staff is limited to security, abuse or support investigations with your consent, or where required by law.
Retention and disconnecting
Tokens are kept until you disconnect, or until your account is deleted (§7). You can disconnect the business Google Calendar connection at any time from OpenSassy settings, which deletes our stored tokens; you can also remove OpenSassy’s access from your Google Account permissions, which invalidates the tokens we hold. Conversations in which Sassy used your calendar are kept under the AI conversation and routing-log retention periods in §7. Nothing in this section changes your rights in §10.
4b. WhatsApp through Meta
The earlier manual Meta WhatsApp integration is restricted to an authorised pilot business and a verified test recipient. Connecting other businesses’ own numbers is not yet enabled. When the authorised owner sends a message or an approved template from OpenSassy, we send the recipient’s phone number, message text or template parameters to Meta for delivery. Creating a template sends its name, body and example values to Meta for review; it does not send a message.
For permitted incoming messages, we store the sender number, provider message reference, receipt time and a short message summary in the business’s database record. The current pilot stores up to 500 characters including the channel label, rather than a complete conversation archive. Send-operation references and outcomes are also retained to prevent duplicate sends and to distinguish accepted, refused and uncertain delivery. That manual pilot does not send WhatsApp content to an AI model or automatically reply to incoming messages.
The platform access token, App Secret and webhook verification secret are stored in Google Secret Manager for use by the OpenSassy backend, not in chat. Detaching the line stops its use and inbound collection for that business; delivery records and platform credentials are retained for reconciliation and administration under §7. Detaching does not delete Meta’s own records or templates. Retention and deletion requests are described in §7 and §10, with instructions at our data-deletion page. Meta processes messages through its own systems; our primary hosting location does not guarantee that Meta processes or retains data only in the UK or EEA.
SassyIN WhatsApp booking/support pilot.
This is a separate pilot for invited existing members, subject to provider approval, testing and account linking. When enabled for you, you must sign in to your OpenSassy account and explicitly accept the WhatsApp booking-channel notice. Meta processes your WhatsApp number, message content and delivery information. OpenSassy sends the booking/support request to the AI providers named in §4c to answer it. This channel can help with OpenSassy business services and bookings, and booking changes require your confirmation. It cannot access your personal SassyIN chats, saved personal preferences, vault or connected apps, and does not grant business owner or staff access.
The booking/support conversation is encrypted and kept separately from personal SassyIN history. Its saved conversation content is cleared after 30 days without channel activity. Temporary incoming and pending reply content expires after five minutes and is removed when processed or by cleanup; minimal replay and delivery records remain for fourteen days. Reply STOP in that WhatsApp chat, or use its signed-in connection page, to disconnect the channel and revoke pending work. This clears our channel conversation, not Meta’s own records. Deleting your SassyIN account removes its associated WhatsApp channel records. New-member WhatsApp sign-up, WhatsApp sign-in codes and scheduled WhatsApp reminders are not enabled by this pilot.
4c. Sassy In AI
What we collect.
- Your mobile number (verified by a one-time code) and your name.
- The invite you used, and your consents: texts, the terms version, 18+, and the AI notice version.
- For optional fast reads, the offered notice version and time and, while enabled, your agreed notice version and consent time.
- Your messages with Sassy, and the replies.
- Reminders you set.
- Preferences you ask her to remember. She only saves one after you say YES.
- Usage counts for your monthly allowance.
Who processes your messages. To answer you, your message and recent conversation go to these AI providers (all in the United States; see §4 and §6):
- Anthropic (Claude) first.
- If Anthropic is unavailable, OpenAI (GPT), then xAI (Grok).
You agree to these providers in the AI notice when you join.
Optional fast personal SMS reads use TypeSafe (Jev) in the United States, separately from the providers you agree to at join. Only a short current SMS request from a limited vocabulary is sent, not your phone number, account identifiers, conversation history or saved reminder/preference details. Text FAST ON to read the separate notice, then YES FAST READS to allow this option. FAST OFF or STOP withdraws it. TypeSafe only chooses between reading all your own upcoming reminders or saved preferences; it cannot make changes. OpenSassy reads the actual details, and preferences are available only while your memory choice is on. The join notice alone does not enable fast reads (see §4 and §6).
Web search and web pages.
- When Sassy searches the web or reads a page for you, she sends a short search question or the page address to the AI provider’s own web-search tool (Anthropic, OpenAI or xAI). If that fails, she sends it to Tavily.
- Web search runs only while OpenSassy has switched it on for Sassy In AI.
- We do not send your exact location, postcode, phone number or name in searches. Sassy does not send a search that contains them; this check reduces risk but is not a guarantee.
- Search providers handle searches under their own terms. Tavily’s terms allow search input and output to be used to improve its AI.
Training.
- OpenSassy does not use your Sassy In AI messages to train AI models.
- We have not contractually verified every provider’s training terms, so we don’t promise that no provider uses the data (see §4).
SMS delivery services.
OpenSassy delivers texts through Twilio or AWS End User Messaging, depending on the enabled service. AWS SMS is restricted to testing until registration, configuration and phone checks are complete. Its configured service region is London. AWS and participating mobile carriers process phone numbers, message content, routing information and delivery records; their own records follow their settings and policies. This is not a guarantee that all provider or carrier processing stays in the UK. Changing the delivery service does not change your AI, memory, research or business permissions. Reply STOP to stop OpenSassy SMS, or email hello@the-sassy.com for help.
For the AWS personal SMS inbox, temporary incoming and pending reply content is encrypted, expires after five minutes, and is removed when processed or by cleanup. Minimal replay markers, opaque delivery references and outcome records remain for eight days. Your saved SassyIN conversation, memories and preferences follow their existing retention and choices below. These periods describe our application records, not the providers’ own records.
Reminders and texts.
- Reminders are only ever sent to your own verified number.
- If your number changes, pending reminders are not sent.
Optional linked messaging channels (private testing).
- RCS testing is limited to invited testers. Apple Messages for Business is awaiting approval and is not available yet. Neither registration alone connects your account. You must sign in to your existing SassyIN account, accept the channel notice and return a linking code in the original conversation before that conversation can access your SassyIN history or preferences.
- For RCS, AWS End User Messaging in London processes the message text and routing details, and Google and participating carriers deliver the messages. These providers may retain message or service records under their settings and policies. The linked conversation uses your existing SassyIN memory and research choices; it does not grant business owner or staff access.
- Queued incoming message content expires after seven days and is removed at the next hourly cleanup, or earlier when processed. Minimal identifiers remain for eight days to prevent duplicate processing. Pending outgoing replies and routing details are encrypted, expire after ten minutes and are removed at the next cleanup or when the send attempt finishes. Saved conversation history follows the existing SassyIN retention above. Deleting your account removes its associated channel links and delivery records.
- Reply STOP in RCS to disconnect that channel; this does not stop your SMS account. You can also disconnect a linked channel from its connection page while signed in. Approval codes for proposed changes must currently be sent in your existing Sassy SMS conversation. Optional TypeSafe fast reads remain SMS-only. This text-only RCS pilot does not automatically open attachments or enable recorded voice notes.
Calls with Sassy (invite-only preview).
- Calls are off until you text CALLS ON and then reply YES CALLS. Text CALLS OFF (or STOP) any time to turn them off; that also ends a call in progress.
- When you call, Sassy texts a one-time code to your verified number and you type it on the keypad. The code is never heard by the AI or written into your conversation.
- Your voice goes live to xAI (Grok voice) in the United States so Sassy can listen and talk back (see §4 and §6). To answer what you ask, the words are also handled like a text message by the AI providers above.
- We don’t record or keep call audio. What you ask and Sassy’s answers are saved as text in your Sassy conversation, the same as texts, and deleted after 30 days without use.
- Call records (time, length and minutes used) are kept for 90 days, for your allowance and for safety. Deleting your account removes them with the rest of your Sassy In AI data.
- Up to 10 minutes of calls a month during the preview. Sassy warns you before the time runs out, then ends the call.
- Sassy can prepare a booking change or reminder on a call, but she texts you the exact change with a YES code. Nothing changes until you reply YES and the code by text; saying “yes” on the call is not enough.
Voice notes (optional).
- If you turn voice notes on (text NOTES ON, then YES NOTES), you can text NOTE to get a private link. It works for 30 minutes and only after you sign in with your Sassy In number; a link on its own opens nothing.
- Your recording is sent to xAI (Grok) to turn your speech into text. We delete the recording as soon as it has been turned into text and never keep a copy.
- We keep the text of what you said, with passwords, codes and card numbers removed, and Sassy’s reply. They are kept in your Sassy In conversation like your texts, and on the voice note for up to 30 days. Sassy’s spoken reply is made by xAI from her written reply; we keep it encrypted for 24 hours so you can play it, then delete it.
- xAI turns speech to text and text to speech. To write the reply, Sassy uses the same AI providers as for your texts. The enabled SMS delivery service described above delivers the text messages: your link; the reply as a text if a spoken reply can’t be made or you ask for one; the full answer, or the exact change with a YES code, when Sassy’s reply needs one; and a text if your note couldn’t be transcribed or if you left the page before Sassy answered.
- Text NOTES OFF at any time: voice notes stop and any saved reply audio is deleted at once. STOP stops everything. Your data export includes the text of your voice notes, not audio. Deleting your account deletes them.
- Each voice note counts as one of your monthly messages, like the texts around it. Recordings can be up to 60 seconds. OpenSassy does not use your recordings to train AI models.
How long we keep it.
- Your conversation with Sassy is deleted after 30 days without use.
- Reminders are deleted 30 days after they are done.
- Unconfirmed actions are deleted after a day.
- If you delete your account, we delete your Sassy In AI data straight away. That covers membership, conversation, reminders, saved preferences and codes. Providers’ own records follow their retention (see §7).
Your rights. You have the same rights as for the rest of OpenSassy: access, correction, deletion and objection (see §10). Text STOP to stop all texts.
Who’s responsible.
- OpenSassy (ANDUMA Intelligence Group Ltd) is the controller for Sassy In AI.
- When you book with a business, that business is also the controller for its own booking records.
5. Data storage and residency
Our application hosting runs on Google Cloud Platform's europe-west1 region (Belgium), within the EEA. Our database is hosted by Supabase in an EEA region. These locations describe our primary hosting, not a guarantee that every provider stores or processes data only in the UK/EEA. AI, maps, messaging and payment providers may process or retain data elsewhere under their own service terms and applicable retention controls (§4, §6 and §7).
6. International transfers
Our primary EEA hosting is outside the UK. Transfers to the EEA are covered by UK adequacy regulations; that does not automatically cover a provider's access from, or onward transfer to, another country. The recipients and processing locations in §4 and §8 include the United States and China as well as UK/EEA services.
A restricted transfer needs a valid route under UK GDPR Chapter V. Where applicable adequacy regulations do not cover it, a contractual route can use the UK International Data Transfer Agreement (IDTA), or the EU Standard Contractual Clauses together with the UK Addendum. EU clauses alone are not sufficient for a UK restricted transfer. These safeguards require a transfer risk assessment (the statutory data protection test) and any additional measures it identifies. US adequacy is limited to eligible recipients and data covered by the UK Extension to the EU-US Data Privacy Framework; a US address alone does not qualify.
Verified TypeSafe arrangement: we accepted TypeSafe's DPA, EU Standard Contractual Clauses and UK Addendum on 4 October 2026, and received confirmation of account zero data retention on 7 October 2026. This covers request and response content, not operational billing and usage telemetry. Zero data retention does not itself establish a lawful international transfer.
Other provider evidence: our review of the account-specific contracts, transfer safeguards and related assessments for the other providers is not complete. A reference to a standard provider DPA is not confirmation that a particular transfer arrangement has been verified. This notice does not replace the safeguards required by law or authorise an otherwise unlawful transfer.
Moonshot AI (Kimi) is based in the People’s Republic of China, which has no UK adequacy decision. Its transfers therefore need a separate assessment and a valid Chapter V route; the US arrangements do not cover China.
You can ask for details or a copy of the safeguards applying to your data at hello@the-sassy.com. We may redact confidential information while explaining the protection provided. The ICO explains the IDTA and UK Addendum and adequacy regulations.
7. Data retention
Active accounts: Data is retained for as long as your subscription is active.
Booking/customer records: The duration of the business relationship plus 6 years (UK limitation period).
Voice call recordings/transcripts: Retained for up to 90 days, then deleted.
Client discovery and voice: Device location is transient search context. Recent searches store your query and selected area locally, not a trail of GPS fixes; saved places store identifiers and any nickname you choose. You can clear this discovery history in the app. Temporary client recording and playback files are removed after use or cancellation; the new transcription service does not add the audio to a conversation ledger. Dictation produces an editable draft that enters chat when you send it. Live voice displays spoken turns as they happen; signed-in turns can enter the saved conversation and, when you request a visit, the server task used to prepare it for your review.
Voice provider retention: Removing our temporary files does not delete a provider's records. OpenAI currently lists no application-state or abuse-monitoring retention for its audio transcription endpoint. Its live conversation, reasoning and speech-generation endpoints ordinarily retain abuse-monitoring data for up to 30 days, subject to the exceptions in its data controls. We request no stored application state for live conversations and their OpenAI reasoning requests; that does not disable provider abuse-monitoring retention. Account settings can affect processing; we do not claim verified zero-data-retention for our account. See OpenAI API data controls.
AI conversation memory: Our assistant's longer-term memory of facts decays automatically (90-day half-life) and is minimised by design.
Routing diagnostics: OpenSassy's diagnostic logs can include filtered request text, the routing decision, timing and usage information. Our application log storage is configured to retain these logs for 30 days. Filtering is not a guarantee of anonymity, and these logs are separate from TypeSafe's zero-retention treatment of request and response content.
Guest chat / leads: Retained for up to 12 months, then deleted.
After account cancellation: Data is retained for 30 days to allow export, then deleted, except billing records (7 years, UK tax law).
You can request earlier deletion at any time — see Your Rights below.
8. Who we share data with
Supabase: our database host.
Google Cloud Platform: application hosting and infrastructure (europe-west1, Belgium).
Google Maps: maps and optional external place searches, including the requested search area and query, and SDK technical information described in §2.
Postcodes.io: lookup of UK postcodes you enter, where supported. See Postcodes.io.
Stripe: payment processing — PCI-DSS compliant, itself a controller for fraud/AML purposes.
Twilio: SMS and voice calling where enabled (US-based — see §6).
Amazon Web Services (AWS End User Messaging): RCS and, when activated, SMS delivery, including phone numbers, messages, routing information and delivery records as described in §4c. The configured messaging service is in London; carriers and providers may process or retain their own records elsewhere. Ara’s AWS phone-call connection is not available yet.
Meta (WhatsApp Business Platform): recipient phone numbers, WhatsApp message or template content and delivery information for the pilots described in §4b, subject to their separate availability and consent requirements. Meta’s own processing is separate from our primary hosting (§5 and §6).
Anthropic, xAI, Google, OpenAI, ElevenLabs, Tavily, TypeSafe: AI processing, speech and web search as described in §4 (US-based — see §6). For Sassy In AI, a member’s searches and web-page addresses go to the web-search tool of Anthropic, OpenAI or xAI, with Tavily as the backup (§4c).
Moonshot AI (Kimi): AI processing for long-context analysis as described in §4 (based in the People’s Republic of China — see §6).
Resend: sends our transactional emails (welcome, booking confirmations, one-time codes).
We do not sell your personal data to anyone, ever.
9. Automated processing
Our AI assistant can propose actions (like sending a message or rescheduling a booking), but anything involving money or an irreversible/destructive change requires a human to approve it before it happens — it is not a "solely automated decision" in the UK GDPR Article 22 sense.
10. Your rights under UK GDPR
You have the following rights regarding your personal data:
- Access: Request a copy of all data we hold about you
- Rectification: Correct inaccurate data
- Erasure: Request deletion of your data ("right to be forgotten")
- Portability: Receive your data in a machine-readable format
- Restriction: Request we limit how we process your data
- Objection: Object to processing based on legitimate interests
- Withdraw consent: For any processing based on consent, including AI processing
If you are a business owner/staff member, you can also manage and erase your own data via your account. If you are a client of a business that uses OpenSassy, you can manage your bookings yourself via your business's booking page, and request erasure either from that business directly or from us. To exercise any right, email hello@the-sassy.com. We will respond within one month, as UK GDPR requires.
11. Children
OpenSassy is a business tool, not directed at children. You must be at least 18 to create a business account.
12. Complaints
If you believe we have handled your data unlawfully, you have the right to lodge a complaint with the Information Commissioner's Office (ICO): ico.org.uk or 0303 123 1113. We'd appreciate the chance to resolve any concerns directly first.
13. Changes to this policy
We will notify you by email and update the date above when we make material changes. Where a change requires your consent, we will ask for it before applying that processing. Continued use or publication of this policy does not replace a specific consent choice required in the platform.