Skip to content
Savigo

Privacy Policy

Draft for legal review — not yet in force. Last updated: [date].

This policy explains what [Company legal name] ("we") collects, why, and what choices you have. It covers two groups of people: the businesses that use our service (and their team members), and the callers and website visitors who talk to a business's assistant.

1. What we collect

From businesses and their teams: name, email, password (stored hashed) or Google sign-in, business details (name, address, hours, services, answers), team members, plan and billing records. Card details are handled by our payment provider (Stripe); we never see or store card numbers.

From callers and chat visitors, on a business's behalf: what they say or type to the assistant, the transcript, their phone number (caller ID) and the details they give for a booking or message (such as name, phone, email, date and time). For phone calls: call times and length, and a recording of the call when the business's recording setting is on — callers are told at the start of the call.

Automatically: sign-in sessions, basic logs (IP address, browser) for security and abuse prevention.

From a connected calendar: see section 3a.

2. How we use it

  • To run the service: answer calls and chats, record bookings and messages, notify the business's team, send weekly reports.
  • To bill businesses and keep accounting records.
  • To keep the service secure and prevent abuse.
  • To improve the service, using de-identified data: transcripts with names, phone numbers, emails, addresses and other details replaced by placeholders, kept without any link to the business or the caller.

We don't sell personal information and we don't use callers' information for our own marketing.

3. Who we share it with

Service providers that help us run the service, under contracts that limit their use of the data:

  • Telnyx — phone numbers, calls, speech recognition and voice.
  • OpenRouter and the model provider it routes to — understanding what callers mean (text only).
  • Stripe — payments.
  • Our hosting and email providers.
  • Google, when a business connects its Google Calendar (section 3a).
  • Apps a business chooses to receive its new requests (Settings › Integrations, for example Zapier or its own CRM): each new booking, inquiry or message, with the details the caller gave, is sent to the address the business entered. That app's own terms and policy then apply; the business decides whether to use it and can remove it any time.

We may also share information if the law requires it, or to protect people's safety or our rights.

3a. Google Calendar

A business can connect its Google Calendar (Business settings › Calendars) so its assistant never offers a time that's already taken and confirmed bookings appear in the calendar.

  • What we read: only the times the calendar is busy, through Google's free/busy service. We don't read the titles, descriptions, attendees or locations of events.
  • What we write: only the bookings the assistant or the business's team confirmed, as events in that calendar: the customer's name, the service, the phone number, the booking's details and a link to it in our app. If a booking is cancelled in our app, we delete its event. We don't change or delete any other event.
  • What we keep: the Google account's email address, and an access token that lets us do the above, encrypted with a key kept apart from the database. Busy times are kept in memory for a few minutes, never stored. The IDs of the events we created are kept with their bookings so we can update or remove them.
  • Who sees it: the business's own team in our app. We don't share data from Google with anyone else, use it for advertising, or use it to train or improve AI models. People at our company can see it only to provide support the business asked for, to investigate abuse or security, or where the law requires.
  • Stopping: the business can disconnect in Business settings › Calendars, or remove our access in its Google Account (Security › Third-party apps). Disconnecting revokes our access at Google and deletes the token at once. Closing the business's account deletes the connection too.

[Company legal name]'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. How long we keep it

  • Conversations and recordings: while the business's account is active, subject to the business's retention setting and our recording setting (which can keep only the recordings of conversations flagged for review, for a limited time).
  • When a person deletes their own account (Settings › Security): their name, email and password are erased at once; the activity log keeps the account's ID only.
  • When a business closes its account: erased 30 days later; invoices and payment records are kept as tax law requires (usually 7 years); de-identified data may be kept.
  • Telnyx and our other providers keep their own copies under their own policies.

5. Your choices and rights

  • Businesses can view and correct their data in the app, download all of it in one file (Business settings › Data & export), change notification emails (every email has an unsubscribe link), and close their account.
  • Anyone with an account can delete it in Settings › Security (a business they alone own is closed first).
  • Callers and visitors can ask the business they contacted, or us, to access or delete their information. We'll help the business respond.
  • Depending on where you live (for example California), you may have additional rights; contact us to use them. We won't treat you differently for using them.

6. Cookies and browser storage

We use only what the service needs to work, plus one cookie that remembers how you found us, and nothing that tracks you across other sites: no advertising cookies, no third-party analytics, and no third-party scripts.

  • Sign-in cookie (rx_session): keeps you signed in; it can't be read by page scripts and is sent only to our site.
  • Google sign-in cookie (rx_oauth): links a "Sign in with Google" round trip to your browser for up to 10 minutes, then it's deleted.
  • Calendar connection cookie (rx_cal): the same, for connecting a Google Calendar.
  • How you found us (rx_src): when you arrive through a link with a referral or campaign tag, or from another website, it remembers that tag and the other site's name (never the page you were on) for up to 90 days. If you sign up, it's kept with your account, so we know which channels bring businesses to us. It's never shared and isn't used on other sites.
  • Browser storage for your choices: language, light or dark theme, and how you set up lists in the app.
  • Session storage (cleared when the tab closes): an open website chat, and the business type chosen on a page before signing up.

If we ever add analytics or advertising tools, we'll update this section and ask for consent where the law requires it.

7. Security

We use encryption in transit, hashed passwords, encrypted calendar access tokens, signed links and signed deliveries to connected apps, access controls by role and activity logs. No system is perfectly secure; we'll notify affected businesses of a breach as the law requires.

8. Children

The service isn't directed at children under 13, and we don't knowingly collect their information.

9. Changes

We'll post changes here and, for important ones, tell businesses by email before they take effect.

Contact

[Company legal name], [address]. Email: [privacy email]. Or use the Contact page.