Privacy policy

How Callaroo handles information when a business signs up, when staff use the dashboard, and when the assistant answers a call or sends a text.

Last updated 13 November 2026

On this page

The short version

This page is the legal record of how Callaroo handles personal information. A shorter, plain language version is on our Data use page. This short version is a summary only. The sections below are the full policy.

  • We collect account details, business details, call records, messages, billing details and technical details. See Information we collect.
  • Calls are answered by a virtual assistant, not a person. Recording is on by default. The assistant does not announce recording at the start of a call today.
  • We share data with the providers listed under Who processes information. We do not sell personal information.
  • Call data is kept while the workspace is active. There is no fixed retention period for it today.
  • Deleting your account does not delete your workspace, your calls, your orders or your recordings. See Your choices and rights.
  • Questions and requests go to [PRIVACY CONTACT]. That address is a placeholder until a real, monitored mailbox is set up.

What this means for you: read the short version to get the shape of the policy, then read the section that applies to you. If you are a caller, start with Callers, transcripts and your responsibility. If you are in India, the EU or California, read the section for your place as well.

On this page

  • The short version
  • What this policy covers
  • Information we collect
  • Callers, transcripts and your responsibility
  • How we use information
  • Who processes information
  • Where information is processed
  • How long we keep it
  • How we protect it
  • If there is a security breach
  • Your choices and rights
  • If you are in India
  • If you are in the EU
  • California residents
  • Children
  • Changes to this policy
  • Contact
  • What changed

What this policy covers

This policy explains how Callaroo handles personal information when you visit our website, create a workspace, use the dashboard, or let our AI assistant answer calls and messages for your business. It covers three groups of people: the business that signs up, the staff who use the workspace, and the callers who speak to the assistant.

It does not cover other companies' websites or services, even when we link to them. It also does not change any agreement you have with us about the service itself. That is in our Terms.

Callaroo is operated by [LEGAL ENTITY], [ADDRESS]. A data controller is the person or business that decides why personal information is collected and how it is used. A data processor is a person or business that handles personal information only on a controller's instructions. For calls, your business is the controller and we are the processor. See Callers, transcripts and your responsibility.

Questions about this policy can go to [PRIVACY CONTACT]. We answer privacy requests from the account owner or an admin on the workspace. [PRIVACY CONTACT] is a placeholder. Do not use it until a real, monitored mailbox is set up and this page is updated with it.

Information we collect

Account and sign-in information

  • Your name, email address and a hashed password. We never store passwords in readable form.
  • Session and security information needed to keep you signed in and to detect unusual sign-in activity. Sign-in sessions expire after 90 days.
  • Workspace membership, your role (owner, manager or staff) and the business you belong to.
  • If you sign in with Google, your name and email address from your Google account.

Business and workspace information

  • Business name, phone number, opening hours, address and the free-text instructions you write for the assistant.
  • Your menu: categories, items, prices, modifiers and availability.
  • Reservation settings, blocked numbers, transfer destinations and messaging settings.
  • Team members you add, and the role each one has.

Call information

  • The caller's phone number, the time of the call and how long it lasted.
  • A transcript of what was said, a short summary and the outcome of the call (an order, a reservation, a callback, a transfer or no result).
  • Anything the caller chose to share: a name, items ordered, pickup time, party size, a callback number and notes.
  • Allergy or health notes that a caller or a business gives us. We keep them only as part of the call record. We do not use them for any other purpose.
  • Voice minutes used, which feed the usage page and your billing.
  • Provider call identifiers needed to reconcile calls with our telephony provider.

What this means for you: recording is on by default for every workspace. When recording is on, the audio is recorded from the moment the call is answered. The assistant does not announce recording at the start of the call today. The assistant answers about recording only when a caller asks. There is no way for a caller to decline recording on the call yet. We are adding an opening announcement and a way to decline recording. Until then, do not promise callers that they are told about recording, because they are not. A recording is not guaranteed for every call. The written transcript is saved separately and is the record your team reviews.

Message information

  • The number a confirmation is sent to, the message body, the time and the delivery status reported by the carrier.
  • Opt-out state, so we do not keep texting someone who has asked us to stop.
  • Confirmation texts for an order or a booking end with Reply STOP to opt out. Reply STOP, STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT to stop messages from that business. Reply START, UNSTOP or YES to start them again. A STOP reply blocks later sends until the customer sends START.
  • There is no HELP reply today. A caller who texts HELP gets no answer. There are no quiet hours and no send window today. A confirmation text can be sent at any time of day or night, including at 2am. We do not send marketing texts.

Billing information

  • Your plan, billing period, invoice status and the last four digits or brand of the payment method.
  • Full card numbers and security codes are handled by our payment processor. They do not pass through our servers and the assistant is instructed never to ask a caller for them. That is an instruction to the assistant, not a guarantee about what any caller may say on a call.

Web search and knowledge files

  • If web search is switched on for a call, the caller's question, including any location the caller states, is sent to the voice model provider and onward to web sources to find an answer.
  • If you upload a document to the knowledge base, it is stored in our database and also sent to the voice model provider so the model can retrieve it during a call. It is kept in a private collection for your workspace.

Studio test chats

  • Text turns, a title and how long the browser line was open. Studio test chats have no audio and no phone minutes.

Technical information

  • IP address, browser and device type, pages visited and the time of the request.
  • Error and diagnostic logs. These are written to help us fix problems, and we avoid placing passwords, tokens or full card details in them.
  • Cookie and local-storage values used for sign-in, theme choice and remembering that you dismissed a notice. A sign-in cookie keeps you signed in for up to 90 days, or 180 days if you choose remember me. A short-lived value confirms your age before a sign-up with Google, and it lasts 10 minutes. The full list, every value, what it does, and how long it lasts, is on our Cookies page at /cookies.

We ask before analytics starts only when your browser timezone is on a list of European timezones. If your browser timezone is outside that list, analytics starts without asking, unless you have declined before. If the consent check fails to read your choice, analytics also starts. That is a fail open, and we say so here instead of hiding it. There is no way to change your choice in the dashboard today. To change it today, clear your browser storage for this site and reload the page. We are adding a Cookie settings link. The full cookie summary is on our Cookies page at /cookies.

Callers, transcripts and your responsibility

For the calls the assistant handles, your business decides why the information is collected. An order, a booking, a callback. We process that information on your instructions to run the service. In privacy terms, you are the controller of your callers' data and we are the processor.

That means you are responsible for telling callers what they need to know. If calls are recorded or transcribed, or if you send confirmation texts, check what notice and consent your jurisdiction requires and put it in your greeting or your published policy. Today the product does not give that notice for you. The assistant does not announce recording at the start of a call, and it says it is a virtual assistant only when a caller asks. You can hand-write a notice into your own greeting text. Nothing in the product tells you to do that, and the default greeting does not have it.

What this means for you: if you are a business, do not assume the product tells callers about recording or about the assistant. It does not do that today. If you are a caller, you speak to a virtual assistant, not a person. The assistant will answer honestly if you ask whether it is a person or whether the call is recorded. The correct answer is: No. I am not a person. I am [business name]'s virtual assistant, powered by Callaroo. The assistant does not claim to be human, and it does not invent a personal life story.

We do not use call content for advertising, and we do not sell it. We use it to answer the call, carry out the request, show the record to your team, measure usage and keep the service secure. We do not use call content to train our own models. Whether the voice model provider trains on call audio or conversation context, or how long it keeps it, has not been confirmed from that provider's own terms yet. We will state the confirmed position here once it is recorded. Do not read our sentence about our own models as a statement about the provider.

If you are a caller and you want to see, correct or delete a record of your call, contact the business you called first. The business decides what to do with its own records. We will help the business respond to your request. If you cannot reach the business, contact [PRIVACY CONTACT] with the business name, the number you called and the date, and we will pass the request on.

How we use information

  • To provide the service: answer calls, take orders, check availability, book tables, queue callbacks, send confirmations and show the results in your workspace. Legal basis where the law asks for one: contract, and we act on your business instructions as a processor for caller data.
  • To run your account and workspace: sign-in, roles and workspace membership. Legal basis: contract.
  • To record and transcribe calls: so the team can follow up and keep quality up. Legal basis: to be confirmed by counsel. We have not confirmed the legal basis for recording and transcription yet, and we do not state one here until counsel confirms it.
  • To keep call records, orders and SMS after the call: so the team can review what was agreed. Legal basis: to be confirmed by counsel, with a fixed retention period. See How long we keep it.
  • To authenticate users, apply roles and keep one business's data away from another's. Legal basis: contract.
  • To measure voice minutes, calculate plan usage and administer billing. Legal basis: contract.
  • To send service email such as sign-in links, receipts, security notices and important changes. Legal basis: contract.
  • To diagnose faults, investigate abuse and improve reliability. Legal basis: legitimate interests, balanced against your privacy. You can object. See Your choices and rights.
  • To meet legal, tax and accounting obligations, and to respond to valid legal requests. Legal basis: legal obligation.
  • For dashboard analytics and session replay: to see how the dashboard is used so we can fix what is broken. Legal basis: your consent, given through the cookie banner, where the banner applies. See our Cookies page at /cookies.
  • For allergy or health notes you or a caller provides: we keep them only as part of the call record. Legal basis and condition: to be confirmed by counsel.

Where the law requires a legal basis, we rely on the basis listed next to each purpose above. We do not use one basis to cover every purpose. We do not make decisions about a caller based only on automated processing, and we do not profile callers for marketing.

What this means for you: the two purposes with no confirmed basis yet are recording and allergy or health notes. We say so here instead of inventing a basis. Counsel must confirm both before we state them.

Who processes information

We share information with service providers that perform a specific function for us. They are only given what that function needs, and they are not permitted to use it for their own marketing.

  • Supabase: database, authentication and file storage for workspace data. It can see all workspace data, auth data and recordings in the default bucket.
  • Stripe: subscription billing, invoices and payment method handling. It can see plan, invoice and payment status, and the last four digits and brand of the payment card. Card numbers go to Stripe directly.
  • Telnyx: phone numbers, call delivery, call recording and SMS delivery. It can see phone numbers, call audio, SMS bodies and delivery status.
  • xAI: the real-time voice model that holds the conversation, and knowledge retrieval from files you upload. It can see live audio, conversation context, instructions, tool results and uploaded knowledge files.
  • Resend: transactional email such as receipts and security notices. It can see email addresses, receipts and security notices.
  • PostHog: product analytics and session replay of dashboard use. It can see dashboard usage events and screen recordings. It does not receive call content directly, but a replay can show caller data that is visible on screen in the dashboard.
  • Cloudflare R2: storage for call recordings and transcript files. It can see call audio and transcript objects.
  • Sentry: error and performance reports. It can see request paths and internal identifiers, with call content scrubbed.
  • Vercel: hosting for the dashboard. It can see dashboard requests and data shown in the dashboard.
  • Railway: hosting for the backend. It can see calls, audio and keys held by the backend.
  • Upstash Redis: rate limiting and caching. It can see session, ticket and rate limit data.
  • Google reCAPTCHA: bot protection on sign-in. It can see IP address and browser signals on sign-in.
  • Google sign-in, where you choose it: sign-in with Google. It can see your name and email address from your Google account.
  • Instatus and Slack webhook: status page and internal alerts. They receive status alerts, not call content.

Session replay

PostHog records screen sessions of dashboard use, a replay of where the mouse went and what was clicked, so we can see a confusing page the way you saw it. Text you type into a form is masked in the replay, because maskAllInputs is true. Text shown on screen, such as a caller name, a number or an order shown in the dashboard, is not masked. Replay can also include content from other sites shown inside dashboard frames, because recordCrossOriginIframes is true. A replay does not include a phone call, a transcript file or a recording file, but it can show call data that is visible on screen.

What this means for you: session replay is not the same as counting page views. It shows screens. If a screen shows caller data, that data can appear in a replay. We say that here so you can decide what to show on screen while replay is on.

We may also disclose information if we are required by law, if it is necessary to protect someone's safety, to investigate fraud or abuse, or as part of a merger or acquisition where the receiving party is bound to this policy. We do not sell personal information, and we do not share it with advertising networks. If we add a provider that can see personal data, we will add it to this list in the same change, and we will tell workspace owners by email or in the dashboard before it takes effect.

Where information is processed

Our providers operate in the United States and other countries. Your call data is processed in the United States by the providers listed in Who processes information.

We have not recorded a transfer mechanism per provider yet. We do not name a mechanism, a country or a region per provider here until it is confirmed from each vendor's own terms. We do not claim that a transfer mechanism exists for a provider until it is recorded. If you are in the EU, see If you are in the EU. If you are in India, see If you are in India.

What this means for you: do not read this section as a promise that your data stays in one country. It does not. The list of providers above is the list of who can see it. The country and the transfer mechanism for each provider are still to be confirmed.

How long we keep it

  • Workspace data, conversations, orders and reservations are kept while the workspace is active so your team can look back at them. There is no automatic deletion schedule for call data today. No retention clock exists for conversations, orders, reservations, transcripts, recordings or SMS. That means the data is kept indefinitely until it is deleted. We will publish a fixed retention period here once it is set.
  • Sign-in sessions expire after 90 days.
  • Stripe webhook events are kept for 30 days by default, and webhook security hashes for 7 days by default. Those two clocks only run if an external scheduler calls the cleanup routes, and no scheduler is committed today. Do not treat them as automatic.
  • Billing and tax records are kept for [NUMBER OF YEARS AND LAW TO BE CONFIRMED BY COUNSEL], even after an account is closed.
  • Recording links: a provider-only link expires on the provider's schedule. Audio copied to private workspace storage stays while the workspace is active. There is currently no way to delete a single recording.
  • Security and diagnostic logs are kept for [NUMBER OF DAYS TO BE CONFIRMED BY COUNSEL].
  • When data is removed from live systems, copies may remain in encrypted backups. We have not confirmed how long those copies remain. We will publish the number once it is confirmed.

If you need a copy of your data before closing an account, ask us before deletion. Once the workspace is gone we cannot reconstruct it. See Your choices and rights for what deletion does today.

What this means for you: if you ask how long we keep a call, the honest answer today is that we keep it until the workspace is deleted, and there is no date when it ages out on its own. That is indefinite retention by accident, not by decision. Counsel must set a clock for each type of data.

How we protect it

Traffic between your browser, our application and our providers is encrypted in transit. Stored data is encrypted at rest by our database provider. Access to business data is limited to the workspace it belongs to, enforced in the database for most workspace tables. We are completing that enforcement on the remaining workspace tables, and we will update this page when it is done.

  • Roles separate what owners, managers and staff can see and change.
  • Provider secrets and service keys stay on the server and are never sent to the browser.
  • Incoming telephony and payment webhooks are verified before they are acted on.
  • Payment card data is handled by Stripe. It does not enter our database.

No service can promise perfect security. We do not currently hold a published third-party security certification, and this page describes the controls in the code today rather than an audit result.

If we become aware of a breach affecting your information, see If there is a security breach.

If there is a security breach

If we learn that personal information was accessed without permission, we will tell the people affected and the authorities the law requires, in the most expedient time possible and without unreasonable delay. We will tell you what we know, what we are doing, and what you should do, even while the investigation is still open.

For New York residents, we will give that notice within 30 days of discovering the breach, and we will notify the New York Attorney General, the New York Department of State, the New York Division of State Police, and the New York Department of Financial Services. If more than 5,000 New York residents are affected, we will also notify the consumer reporting agencies. For California residents, we will notify the California Attorney General if more than 500 California residents are affected.

If you are in the EU and the incident is a personal data breach, we will tell the business controller without undue delay after we become aware of it, so the controller can notify the supervisory authority within 72 hours where that duty applies. If the breach is likely to result in a high risk to callers, we will help the controller tell the people affected without undue delay. If you are in India, see If you are in India for the breach route there.

To report a suspected breach or a compromised account, contact [PRIVACY CONTACT]. Include what happened, when it happened, and the workspace affected. Do not test against another business's data.

What this means for you: the 30 day New York clock and the 72 hour EU clock start at discovery, not at the end of an investigation. The contact above is a placeholder until a real, monitored mailbox is set up. Until then, there is no working channel to report a breach through this page.

Your choices and rights

Depending on where you live, you may have the right to see the personal information we hold about you, correct it, export it, delete it, restrict or object to certain processing, or withdraw consent you previously gave. You can also ask us not to send non-essential email. New York does not have a single comprehensive privacy law. The rights in this section are the ones we offer to every account owner, because we think they are the right thing to offer, not because a New York law requires each of them. California residents have additional rights when the business meets the tests described in California residents.

  • Most account and workspace information can be viewed and corrected directly in the dashboard.
  • You can ask for a copy of your records by contacting [PRIVACY CONTACT]. The self-serve export in settings returns only account identity, login history, sessions and activity. It does not include conversations, transcripts, orders, bookings, messages or recordings. For those, ask support and support will tell you what is included and how long it will take.
  • Deleting your account removes your sign-in profile and user-scoped records, but it does not delete your workspace, conversations, orders, messages or recordings. If you own a workspace, deletion currently fails with an error after your profile row is already gone, because the workspace still points at your account. The workspace is left untouched. Do not delete your account expecting the workspace to go with it. To remove a workspace, contact [PRIVACY CONTACT] before you delete your account, and export anything you need to keep first.
  • For an access, export or deletion request, contact [PRIVACY CONTACT] from the address on the account. We may ask you to verify control of the account or workspace before acting.
  • If you are a caller and want to reach the business you called, contact that business. We will help the business respond to your request, but we cannot decide what it should do with its own records.

What this means for you: account deletion is broken for owners today. It deletes your profile first, then fails, then leaves the workspace behind. That is worse than a refusal, because your sign-in is gone and your business data is still there. Use the support route in the list above until the deletion fix ships. Do not sign a data processing agreement that promises workspace deletion until the fix is tested.

We will not treat you differently for exercising a privacy right. If you are unhappy with our response, you can complain to your local data protection authority.

If you are in India

This section is for people in India. It is written as a standalone notice. If you are in India, we collect your phone number, the time and length of your call, a written record of what was said, and any order or booking details you give. We use these to take your order or booking, to let the restaurant follow up, and to keep a record the restaurant can review. We do not sell this information.

We are a young product, and our India pages are incomplete. Calls may be recorded and transcribed. We do not yet announce recording at the start of every call, and we do not yet offer a way to decline recording on the call. If you do not want your call recorded, please contact the restaurant by another method. We do not yet offer text confirmation for phone numbers in India. We have no DLT registration, no registered Indian header and no registered content template for SMS in India yet, so we do not send confirmation texts to phone numbers in India at this time.

The Digital Personal Data Protection Act 2023 is the Indian data law that applies to personal data in digital form in India, and to processing outside India when it is connected with offering goods or services to people in India. The DPDP Rules were still being finalised as of 2026, in the terms of the brief for this review. We do not claim the DPDP Act is fully operational, and we do not publish a DPDP compliance date. Counsel must verify the current Gazette position, the commencement dates and whether the Data Protection Board is accepting complaints before we publish a date or a duty as in force.

  • Notice: this section is the notice for India. It lists each item we collect and the purpose for that item. To withdraw consent, to use your rights, or to complain, contact [PRIVACY CONTACT].
  • Consent: we do not yet have a consent record for calls, and we do not yet ask for consent before recording starts. Do not read staying on the call as free and specific consent until counsel approves that framing.
  • Rights: you can ask for a summary of the personal data we hold about you, ask us to correct it, or ask us to delete it when the purpose for keeping it has ended. Send your request to [PRIVACY CONTACT] from the email address on your account, or ask the restaurant you called to send it for you. We will acknowledge your request and tell you what we need to check your identity. We do not publish a response time in days here, because counsel has not confirmed the times and the product cannot meet a deletion request today.
  • Grievance: if you have a complaint about how we handled your personal data, contact [PRIVACY CONTACT]. Tell us what happened, when it happened, and what you would like us to do. We will acknowledge your complaint and tell you the next step. We have not named a Grievance Officer yet, and we do not name a Data Protection Board complaint route here yet. Counsel must confirm both before we publish them.
  • Breach: if we learn of a breach of personal data, we will tell affected workspace owners without delay, tell them what we know and what we are doing, and tell the authority the law requires. We will help the workspace owner tell affected callers. We do not publish a 72 hour detailed report timing here until counsel confirms it and the runbook can meet it.
  • Transfers: if you are in India, your call data is processed in the United States by the providers listed in Who processes information. We transfer personal data outside India only to countries that the Central Government has not restricted. If that changes, we will update this policy. The United States is not whitelisted. It is simply not restricted on the date checked.
  • Children: a child in India is a person who has not completed 18 years. If you are under 18, please ask a parent or guardian to stay with you when you call. A parent or guardian can ask us to correct or delete a child's call record by contacting [PRIVACY CONTACT] or the restaurant that took the call. We do not yet have a verifiable parental consent flow.

What this means for you: if you are in India, do not rely on this section as a complete DPDP notice yet. It is the interim honest version. It tells you what we collect, what we cannot do yet, and who to contact. It does not promise a grievance officer, a Board route, SMS in India, or a deletion date that the product cannot meet.

If you are in the EU

If you are in the European Union or the European Economic Area, this section applies to you as well as the rest of this policy. The General Data Protection Regulation, called GDPR, applies to a business outside the EU when it offers goods or services to people in the EU, or monitors their behaviour in the EU. We have not decided whether to serve EU callers at launch. Counsel must decide that before we state a launch position here.

  • Lawful basis: the basis for each purpose is listed next to that purpose in How we use information. Recording and allergy or health notes have no confirmed basis yet.
  • Controller and processor: for calls, your business is the controller and we are the processor. We act only on your business instructions. We do not yet have a data processing agreement published. We will add a link here when counsel confirms it. We do not decide on our own to use caller data for another purpose.
  • Rights: you have the right to see the personal data we hold about you, to correct it, to ask us to delete it, to ask us to limit how we use it, to receive a copy in a portable form, to object to our use of it, and to withdraw your consent where we rely on consent. We will respond within one month. If your request is complex, we may extend this by two months and we will tell you why.
  • AI disclosure: the EU AI Act requires people interacting with an AI system to be told they are interacting with an AI system, in a clear way, at the latest at the time of the first interaction. Today the assistant says so only when a caller asks. We are adding a sentence at the start of every call that says the caller is speaking to a virtual assistant. Do not read this policy as a claim that the opening sentence exists today, because it does not.
  • Transfers: your personal data may be transferred outside the EU to the countries where our providers operate. We have not confirmed a transfer mechanism per provider yet. We do not claim Standard Contractual Clauses, adequacy or equivalent handling for any provider until counsel confirms the mechanism and the transfer impact assessment for that provider.
  • Breach: see If there is a security breach for the 72 hour supervisory authority route, which runs through the business as controller.
  • Cookies: if you are in Europe, we ask before analytics starts, where the banner applies. See our Cookies page at /cookies. Your answer is stored in your browser, and you can change it from the Cookie settings link in the footer once that link exists.
  • Children: a child can still phone a business. See Children for how a parent can ask for a child's call record to be deleted.

We have not named a Data Protection Officer, an EU representative or a lead supervisory authority. Do not read this page as naming one. Counsel must decide whether each role is required and name a real person before we publish a name.

What this means for you: if you are in the EU, the two gaps that matter most are the same as everywhere else. Recording starts without an opening notice, and deletion does not work for owners. The EU rights above are real rights, but the product cannot meet a deletion request today. Use the support route in Your choices and rights.

California residents

California privacy law, the CCPA as amended by the CPRA, applies to a business that does business in California and meets any one of three tests: more than $26,625,000 in annual gross revenue; personal information of 100,000 or more California consumers or households bought, sold or shared in a year; or half or more of annual revenue from selling or sharing personal information.

[LEGAL ENTITY] does not meet any of those tests today. We are a small company, we earn our revenue from subscriptions, and we do not sell personal information. The volume test, the 100,000 consumer test, is under review, because we receive caller data from every business we serve. If we meet any of those tests in the future, we will update this page and put the rights process in place before we meet the test. You can still contact us about your personal information at [PRIVACY CONTACT], and we will answer. We do not claim CCPA compliance, because we are not a covered business today.

For the calls the assistant handles, your business decides why the information is collected. In privacy terms, you are the controller of your callers' data and we are the processor. We process caller information only to provide the service to your business, and we do not sell it or share it with advertising networks.

California law requires a business that collects personal information online to post a privacy policy. This page is our policy. California is an all-party consent state for recording. That means every party to a call must consent before a confidential call is recorded. Today recording starts without an opening notice and without a consent step, so do not read this page as a claim that California recording consent is collected on the call. It is not collected today.

Allergy and health notes can appear in shop notes and transcripts. Health information is sensitive personal information in California. You can ask for such a note to be removed by contacting the business you called, or [PRIVACY CONTACT]. See If there is a security breach for the California Attorney General notice route.

Children

The service is intended for businesses and is not directed to children. Accounts require the person accepting the Terms to be at least 18 years old. We do not knowingly collect personal information from children who create an account. If you believe a child has created an account, contact [PRIVACY CONTACT] and we will remove it.

A child can still phone a business that uses Callaroo. If a child calls, we treat the call the same way as any other call: we record and transcribe it only as described in Information we collect, we keep it only for the period in How long we keep it, and a parent can ask the business to delete it. If you are a parent and you want a record of your child's call deleted, contact the business you called, or contact [PRIVACY CONTACT]. We do not yet have a parental consent flow for child callers, and we do not claim that children are excluded from calling. In India, a child is a person who has not completed 18 years. See If you are in India.

Changes to this policy

We update this policy when the product, our providers or the law change. The date at the top shows the current version. If a change materially affects how we handle personal information, we will tell workspace owners by email or in the dashboard before it takes effect. We have not published a notice period in days yet. Each version of this policy is dated in What changed below.

Contact

Privacy questions, access requests, export requests, deletion requests and security concerns: [PRIVACY CONTACT]. Include the workspace name and the email address on the account so we can find the right records. Never send a password, an access token or card details in an email.

Callaroo is operated by [LEGAL ENTITY], [ADDRESS]. Questions about this policy, and requests to see, correct, export or delete your information, go to [PRIVACY CONTACT]. If you are a caller and you cannot reach the business you called, email [PRIVACY CONTACT] with the business name, the number you called and the date, and we will pass your request to that business.

Callaroo: AI business communications for restaurants and service businesses.

What changed

  • 13 November 2026: full rewrite. Added the short version, the table of contents, the breach section, the India section, the EU section, the California section and this changelog. Replaced the false account deletion promise with the honest deletion wording. Replaced the self-serve export claim with the honest export wording. Added the full provider list, including Cloudflare R2, Sentry, Vercel, Railway, Upstash Redis and Google reCAPTCHA, and described PostHog session replay and its masking. Added the honest recording, cookie and SMS wording. Replaced the support email with [PRIVACY CONTACT] as a placeholder until a real, monitored mailbox is set up.
  • 1 November 2026: previous version. The previous text is not archived here yet. We will keep prior versions here once the archive is set up.