Privacy policy

Two different relationships, worth keeping apart

When a business hires Sonora AI, that business decides what its callers' data is used for: it is the controller. We process it on their behalf and on their instructions, as a processor.

When you use this site or the portal — as a client or as a partner — we are the controller, CODEFORGE LLC.

What is processed during a call

The call audio and its transcript. A summary of what was asked and whether it was resolved. The number the person called from and, if given, their name. The details of any appointment, order or message left.

Card details are never taken by voice. When there is a payment, a link from the payment provider is sent and the card is entered there, never in our systems.

Recording and notice

The assistant announces at the start of the call that the conversation is being recorded. It is recorded to handle the request, keep a record of what was agreed, and review the quality of the service. The call is processed on behalf of the business that answers it, which decides on that data. Anyone who does not wish to continue can hang up, and can ask for access to what was recorded, its correction or its deletion at contact@sonoravoice.com. It is kept for 90 days.

How long it is kept

Recordings, transcripts, summaries and free text tied to a contact are kept for 90 days and then removed from the records. Minimal billing data and usage records are kept as long as accounting and tax rules require.

Who it is shared with

Only the providers needed to run the service. Which ones take part in a call depends on the voice engine that answers it.

Voice: Google (Gemini, the model that listens to the call, transcribes it and replies; it is the main engine) and LiveKit (carries the audio between the phone line or browser and that model). Calls answered by the second voice engine go through transcription, language-model and speech-synthesis providers, also over LiveKit. Vapi (call processing, which in turn uses language-model and speech vendors) answers calls for businesses still on that platform and calls from the web link, and is the fallback when the main engine is unavailable.

Telephony and messaging: DIDWW (carrier for Argentine numbers), Twilio (other numbers and text messages), Meta (WhatsApp; replies on that channel are generated by Google or Vapi) and Resend (email).

The rest of the service: Cloudflare (storage for recordings and each call's records), Render (hosting and database), Stripe and Mercado Pago (payments), Microsoft (Azure OpenAI: language models for classifying the documents the client uploads to set up their assistant), Sentry (technical error monitoring), and — when the client connects a calendar or CRM — whichever provider they chose: Cal.com, Google Calendar, Calendly or GoHighLevel.

We do not sell personal data and do not share it for advertising.

Where the data is and international transfers

Sonora's services run in the United States: the database, the portal and the voice service are hosted on Render, Oregon region, and recordings are stored on Cloudflare. That means call data is transferred out of Argentina, to a country that Argentina's data protection authority (AAIP) does not currently list as providing an adequate level of protection.

For that transfer, Sonora offers each business customer the model international data transfer contract for service provision (Annex II of Disposición DNPDP 60-E/2016): it requires Sonora to process the data only on the business's behalf and to provide the service, to protect it, to assist people's requests, and to return or destroy it at the end. You can ask for a copy at contact@sonoravoice.com.

Data protection

Communication between our systems and the providers listed above travels encrypted (TLS). The telephone leg is the exception: between the caller's phone, the carrier and the platform that answers, audio travels as it does on any phone call, without encryption on our part. Data at rest — recordings, transcripts, access tokens and everything else stored in our database — is also stored encrypted.

Access to that data is restricted to those who need it to run the service or resolve a specific issue; there is no general team access or exports outside that purpose.

The use of raw or derived user data received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.

Google Workspace data (when Google Calendar is connected)

If the client connects their Google Calendar, the app accesses that calendar only, under two permissions: reading availability, and creating or changing the appointments the assistant books. It does not access mail, contacts, files, Google Photos or any other data in the account.

Use of that information is limited to operating the scheduling feature the client can see: checking free times, creating an appointment, and rescheduling or cancelling one at a caller's request. It is not used for advertising, is not sold, is not shared with third parties for marketing, and is not used to train artificial-intelligence models — ours or anyone else's, whether raw, aggregated or derived. No human reads it, except where strictly necessary to resolve a technical problem the client has reported, to comply with a legal obligation, or to investigate a security incident.

Access tokens are stored encrypted, and the client can disconnect the integration at any time, which deletes them.

Site measurement

We count how often each page is viewed and how far down people get, so we can tell whether the site makes sense. The measurement is our own: there is no third-party provider, the data stays in our database, and it is not shared.

Nothing is stored on your device — no cookies, no local storage — and no identifier is recorded: not your IP, not your browser, not a session number. We keep only which event happened, on which page, in which language, and whether the screen was phone- or desktop-sized.

That is why there is no consent banner: there is nothing to consent to. These measurements are about pages, not people, and an individual visit cannot be reconstructed from them.

Your portal account data

To create and keep your account we store your email, your role, your password (only as an encrypted hash, never in clear) and a log of your sign-ins and failed attempts, with the IP address and time. Sign-in attempt logs are kept only as long as needed to stop abuse.

When you accept the Terms of Service and this policy, we store which version you accepted, when, from which IP address and with which browser (user agent). It is the proof that you accepted, and we use it only for that. It is kept while the account exists and for five years after.

We are the controller of this data, CODEFORGE LLC. To request access, correction or erasure, see "Your rights".

Your rights

You can request access, correction or erasure at contact@sonoravoice.com. We can export and erase everything tied to a phone number.

In Argentina the Agencia de Acceso a la Información Pública supervises personal data (Ley 25.326) and you may address it directly.