Privacy Policy
Last updated 28 October 2026
Blumeo builds and runs AI systems for service businesses: answering calls, texting new leads, asking customers for reviews, and reporting the results back. Running those systems means handling information, and this page says plainly what we handle and why.
Who this covers
Two different groups, with different relationships to us.
- Our clients. The businesses who hire us. We are the ones deciding how their account information is used, so for that information we are the data controller.
- Our clients' customers. The people who call, text, or fill in a form for one of our clients. That information belongs to our client. We only process it on their instructions, as their service provider.
What we collect from clients
- Business details: company name, contact name, email, phone, service area, opening hours.
- How you want your systems to behave: pricing lines, transfer numbers, tone of voice.
- Billing records. Card details go straight to Stripe and never reach us.
- Portal usage: when you sign in, and what you look at.
What we process on our clients' behalf
- Calls. Caller phone number, the time and length of the call, a written transcript, and a short summary. Where a recording is kept, it is kept because our client asked for it.
- Messages. Texts sent and received when following up a lead or chasing a quote, including the phone numbers involved.
- Bookings and enquiries. Name, contact details, and what the job is.
- Reviews. Public review text and ratings, and the replies posted to them.
Recording and consent
Some states require every party on a call to be told it is being recorded or transcribed. Where that applies, our systems announce it at the start of the call. Our clients are responsible for the laws that apply to their own business, and we will configure the announcement for any jurisdiction on request.
Why we use it
- To run the service our client is paying for.
- To show our client their own numbers in their portal.
- To bill, to support, and to fix things when they break.
- To meet a legal obligation, when one applies.
We do not sell personal information. We do not share it for advertising. We do not use one client's data to work on another client's account.
Who we share it with
Only the companies that make the service run, and only the part each one needs:
- Google: if you connect Google Calendar, to check your availability and add the bookings your receptionist makes (see Google user data).
- Stripe: payments. Stripe holds the card details; we see amounts and status.
- Hosting and database providers (Vercel, Supabase, Netlify): where the website, the Blumeo app and its data run.
- Telephony and AI providers (Twilio, Retell AI, Anthropic): placing and answering calls and texts, turning speech into text, and drafting replies.
We may also disclose information where the law requires it, or to protect someone's safety.
Google user data
If you connect a Google account to Blumeo, this is exactly what we access, how we use it, who it is shared with, how we protect it and how long we keep it.
What we access
- Sign-in (if you choose "Continue with Google"): your basic Google profile (name, email address and profile picture), used only to create your Blumeo account and sign you in.
- Google Calendar, free/busy (
calendar.freebusy): the busy and free time ranges on your primary calendar. We see only when you are busy, not what your events are called or who is in them. - Google Calendar, events (
calendar.events): permission to add the bookings your Blumeo receptionist makes to your primary calendar, and to read your calendar's time zone so bookings land at the right hour. We do not read, change or delete any of your other events.
How we use it
Only to provide the booking feature you switched on. While a customer is on the phone asking for an appointment, Blumeo checks your free/busy times so the receptionist only offers times you are actually open, then adds the job the customer picks to your calendar with the customer's name, phone number, address and what the job is. You see every booking in your Blumeo dashboard.
We do not sell Google user data, use it for advertising or lending, or use it to develop, improve or train generalized AI or machine-learning models. People at Blumeo do not read it unless you ask us to for support, or where it is needed for security or required by law.
Who it is shared with
- Our hosting and database providers (Vercel and Supabase), which store and run the Blumeo app, under contracts that limit them to providing that service.
- Our voice AI provider (Retell AI), which runs the phone conversation. During a call it receives only the open appointment windows we worked out from your free/busy times, such as "Tuesday 8–10 AM", so the receptionist can offer them to the caller. It does not receive your calendar or its events. See AI services below for what Retell may do with call data.
We do not share Google user data with anyone else, and never with data brokers or advertisers.
AI services and Google user data
Blumeo itself never uses Google user data, raw or derived, to create, train or improve AI or machine-learning models. Blumeo uses two AI providers:
- Retell AI (pay-as-you-go plan) runs the receptionist's phone conversations. Of your Google data it receives only the open appointment windows described above, which the receptionist may say to the caller. Retell runs each conversation on OpenAI GPT models, through OpenAI's API or Microsoft Azure OpenAI (occasionally Amazon Bedrock), under zero data retention agreements, so those model providers neither keep nor train on it. Retell's own terms for our plan let Retell use call data, after de-identifying and aggregating it, to develop and improve its AI models, and that call data can include the appointment times said on a call. Retell offers a commitment not to do this only under an Enterprise agreement, which Blumeo does not have.
- Anthropic (the Claude API, under Anthropic's commercial terms) powers other Blumeo features, such as the support chat and drafted text replies. It never receives Google Calendar data, and under those terms Anthropic does not train on data we send.
We do not use self-hosted or offline AI models with Google user data.
How we protect it
Your Google access token is encrypted (AES-256-GCM) before it is stored, and decrypted only at the moment Blumeo calls Google for you. All data travels over encrypted connections (TLS). Each business's data is separated by database row-level security, so one account can never read another's, and only a small number of Blumeo staff can reach production systems.
How long we keep it and how to delete it
We keep your Google access token only while Calendar is connected. Free/busy times are used during the call and not stored, apart from the few windows offered to that caller, kept with the call record. Booking details (time, customer and job) are kept with your call history for as long as your Blumeo account is open, so you can see what was booked.
Revoking access and deleting data: disconnect Google Calendar in your Blumeo account settings, or remove Blumeo at myaccount.google.com/permissions. Either one stops our access immediately, and we delete the stored token at once. When you close your Blumeo account, or if you write to hello@blumeo.ai, we delete the Google user data we hold within 30 days.
Limited Use
Blumeo's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs (including Google Calendar) will adhere to the Google User Data Policy, including the Limited Use requirements.
Text messaging
Blumeo sends text messages on behalf of the businesses that use it, and to those businesses' owners and staff.
- What we send: replies to missed calls and to new enquiries, booking confirmations and reminders, appointment updates, and, for business owners, account alerts such as urgent-call notifications.
- How numbers are collected: a customer's number reaches us when they call, text, or send an enquiry to a business that uses Blumeo, and the messages are about that enquiry or booking. Business owners give us their mobile number when they sign up and confirm it with a code.
- Consent to receive text messages is not a condition of any purchase.
- Message frequency varies. Message and data rates may apply.
- Reply STOP to opt out at any time, or HELP for help.
- Support: hello@blumeo.ai or app.blumeo.ai/support.
Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are excluded from every sharing category above and will not be shared with any third parties.
How long we keep it
Call transcripts, messages, and the daily numbers behind the dashboards are kept while the account is open, so you can look back at your own history. When an account closes, we delete the account's data within 90 days unless you ask for it sooner or we are legally required to hold it longer. Billing records are kept as long as tax rules require.
Security
Passwords are stored hashed and salted, never in a readable form. Access to client data is limited to the people who need it to do the work. Connections are encrypted in transit. No system is perfect, and we will tell affected clients promptly if something goes wrong.
Your choices
You can ask us to show you what we hold, correct it, delete it, or hand it over in a portable file. Write to hello@blumeo.ai and we will answer within 30 days.
If you are one of our clients' customers rather than a client yourself, the business you called or texted controls that information. Ask them directly, or write to us and we will pass it on.
To stop receiving texts, reply STOP to any message. That works immediately and permanently for that number.
Children
Blumeo is sold to businesses. It is not directed at children and we do not knowingly collect information from anyone under 13.
Changes
If this policy changes in a way that matters, we will update the date at the top and tell active clients by email.
Contact
Questions about any of this go to hello@blumeo.ai.