Privacy Policy

Last updated: September 7, 2026

1. Overview

Sarase, a product of Mangu Dev LLC (“Sarase,” “we,” “our”), provides an AI operations platform for local service businesses. Its AI agents support customer communication, scheduling, CRM, payments, follow-up, social messaging, and online booking while the business owner keeps visibility and control. Mangu Dev LLC is the legal entity responsible for the information described in this policy. This Privacy Policy explains what information we collect, how we use it, and the choices you have regarding your information. It applies to both the businesses that use Sarase (“Customers”) and the end users who call or text those businesses (“End Users”).

2. Information we collect

From businesses (Customers)

  • Account information: name, email, password hash, business name, website.
  • Business configuration: business hours, services offered, pricing, receptionist personality settings, custom instructions.
  • Billing information: processed by our payment provider (Stripe); we do not store full card numbers on our servers.
  • Phone number provisioning data: the Twilio phone number assigned to the business and its identifiers.
  • Google Calendar authorization tokens (OAuth), free/busy availability results, and Sarase appointment event data if the Customer or a staff member chooses to connect Google Calendar. For unrelated calendar events, Sarase receives only whether a time is busy or free, not the event title, description, attendees, or other event details. Free/busy results are used during the availability check that requested them and are not stored. Section 5 covers Google user data in full.

From end users (callers and texters)

  • Phone number (the number the end user is calling or texting from).
  • Name and email, if provided during the booking flow.
  • Call transcripts and voice recordings of conversations with the AI receptionist.
  • SMS message content exchanged with the AI receptionist.
  • Appointment details: date, time, requested service, special notes you provide.
  • Call metadata: duration, timestamps, and the phone number that was dialed.

From website visitors

  • Usage analytics: pages viewed, links and buttons clicked, approximate location derived from IP address, and device and browser type. We use this to understand how visitors move through the site and where they abandon it. Google Analytics runs across all of sarase.com, including pages you see once signed in. Heap and Contentsquare are limited to the public marketing pages, and Contentsquare additionally to the signup flow.
  • Session replay, which reconstructs how a visitor moved through a page. Only Contentsquare does this, and only on the marketing pages and the signup flow. Fields where a visitor types personal information — name, email, business name, phone number, and verification codes — are masked in the browser, so their contents are never transmitted or recorded. Heap is configured with session replay and on-page text capture turned off.
  • Neither Heap nor Contentsquare runs in the business dashboard or on end-user booking pages.

3. How we use information

  • To operate the AI receptionist: route inbound calls and texts to the correct business, understand what the end user is asking for, and generate a helpful response.
  • To create, modify, and cancel appointments on behalf of the business, and to sync them with the business’s calendar if connected.
  • To check free/busy availability on a connected primary Google Calendar so Sarase does not offer times that are already occupied.
  • To send appointment confirmations, reminders, and status updates to end users via SMS or email.
  • To provide the business with a dashboard showing call history, transcripts, customer contact information, and analytics.
  • To detect abuse, prevent fraud, and comply with applicable laws and carrier regulations (including U.S. A2P 10DLC rules).
  • To improve the quality and accuracy of the AI receptionist through aggregated, anonymized metrics. We do not use individual conversation content to train third-party AI models.

4. How we share information

We share the minimum information needed with the following categories of service providers, each under a data processing agreement:

  • Twilio - telephony carrier for phone numbers, SMS delivery, and voice routing.
  • LiveKit - real-time voice infrastructure for AI phone calls.
  • Deepgram - speech-to-text transcription of voice calls.
  • Google Gemini - the large language model that powers the AI receptionist’s understanding and responses.
  • Cartesia - text-to-speech synthesis for the AI receptionist’s voice.
  • Stripe - payment processing for business subscriptions.
  • Google Calendar - if the business opts in to calendar sync, Sarase reads free/busy availability and creates, updates, or deletes events for appointments managed by Sarase.
  • Google Analytics - aggregate traffic measurement across sarase.com, including signed-in pages. It receives page addresses and interaction events, not call, message, or appointment content.
  • Heap - product analytics on our public marketing pages. Configured with session replay and on-page text capture disabled, and with URL parameters, page titles, and referrer values removed before events are sent.
  • Contentsquare - website analytics and session replay on our public marketing pages and signup flow, used to measure how visitors move through the site. It does not run in the business dashboard or on end-user booking pages, and receives no call, message, or appointment data.
  • Railway - hosting and database infrastructure.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not share conversation content with any third party for purposes other than operating the service.

Google user data is covered in detail in section 5 below, including the scopes we request and our Limited Use commitments.

Mobile information and phone numbers collected as part of our SMS messaging program will not be shared with third parties or affiliates for marketing or promotional purposes. SMS opt-in data and consent records are not sold, rented, or shared with any third party under any circumstance. This restriction applies regardless of the legal basis under which the original phone number was collected.

5. Google user data and Limited Use

Connecting Google Calendar is optional and is always initiated by the Customer or a staff member from the Sarase dashboard. Everything in this section applies only while that connection is authorized.

Scopes we request, and the Google Calendar data they give us

  • calendar.freebusy - read-only free/busy lookups on the connected calendar. Sarase learns only whether a time range is busy or free. It does not receive event titles, descriptions, locations, attendees, or any other detail of events it did not create.
  • calendar.events.owned - lets Sarase create, update, and delete only the calendar events Sarase itself created for appointments booked through the platform. Sarase cannot read or modify events created by anyone else; the broader calendar.events scope is deliberately not requested.
  • Signing in with Google, which is separate from the calendar connection, uses the standard sign-in scopes and gives Sarase the account’s name, email address, and profile picture solely to create and authenticate the Sarase account.

How we use that data

  • To avoid offering appointment times that are already occupied on the connected calendar.
  • To keep Sarase appointments in sync with the connected calendar: creating an event when an appointment is booked, updating it when it is rescheduled, and deleting it when it is cancelled.
  • To show the Customer which Google account is currently connected.

Limited Use

Sarase’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we do not sell Google user data; we do not use it for advertising; we do not transfer it to others except as necessary to provide or improve the features the user authorized, to comply with applicable law, or as part of a merger or acquisition; and we do not use it to develop, improve, or train generalized or third-party AI or machine learning models. Human access to Google user data is prohibited except with the user’s explicit consent for a specific support request, where necessary for security or to comply with applicable law, or on aggregated and anonymized data for internal operations.

Retention and revocation

Google Calendar authorization tokens are encrypted with AES-256-GCM before storage and are retained only while the integration stays connected. Disconnecting Google Calendar from the Sarase dashboard - or, for staff members, from staff calendar settings - makes Sarase request revocation from Google and delete the stored token. Access can also be revoked at any time from the Google Account permissions page at myaccount.google.com/permissions. Free/busy results are used at the moment of the availability check and are not stored as calendar content; the appointment records Sarase keeps are described in section 6.

6. Data retention

Conversation transcripts, call recordings, and appointment records are retained for as long as the business remains an active Customer of Sarase. Once a business cancels its subscription, its associated data is deleted within 30 days, except where longer retention is required by law. End users may contact the business they interacted with, or contact Sarase directly, to request deletion of their specific information earlier.

Retention and revocation of Google Calendar authorization tokens are covered in section 5.

7. Your rights and choices

  • Opt out of SMS: end users can reply STOP to any SMS from a Sarase-powered business to immediately stop receiving further messages. Replying HELP returns support information.
  • Access and deletion: end users may request a copy of their data or its deletion by contacting the business directly or emailing [email protected].
  • Calendar disconnection: businesses can revoke Google Calendar access at any time from the Sarase dashboard. Staff members can disconnect their own calendar from their staff calendar settings.

8. Security

We use industry-standard safeguards including TLS encryption in transit, encrypted database storage at rest, application-level AES-256-GCM encryption for Google Calendar authorization tokens, scoped API keys with least-privilege access, and cryptographic signature verification on every inbound webhook. No system can be perfectly secure; we will notify affected users of a material breach in accordance with applicable law.

9. Children

Sarase is not directed to children under 13 and we do not knowingly collect information from them. If you believe a child has provided us with information, contact us and we will delete it.

10. International users

Sarase is operated from the United States and data is processed in the United States. If you are accessing Sarase from outside the U.S., you consent to the transfer of your information to the U.S.

11. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be announced on this page with an updated revision date. Continued use of Sarase after a change indicates acceptance of the updated policy.

12. Contact us

For questions about this Privacy Policy or to exercise your rights, contact us at [email protected].