Trust center

Honest about the AI on the line. And about what we don’t have yet.

Sí Call tells callers they’re talking to an AI in the opening words of each call. This page sets out that notice, what we keep from a call, the security practices in place, and what we haven’t built or earned yet.

Plans open at launch. Nothing can be bought yet, and features marked “Coming soon” aren’t built yet.

Join the Founding 50Try it in your browser
The AI and recording notice

Callers are told it’s an AI in the opening words.

The AI part is built into the greeting and can’t be turned off. The recording part has two settings, and both tell the caller what happens to the call.

The first words

One sentence before your greeting.

With the default settings, Sí Call says one sentence before your greeting: “You’re speaking with an AI assistant, and this call is recorded and transcribed.”

The AI half can’t be switched off. If your own greeting already says it’s an AI, for example “you’ve reached our AI assistant”, it isn’t said twice. If a caller asks later whether they’re talking to a person, Sí Call is instructed to say plainly that it’s an AI.

You can reword the recording half in your settings. The AI half stays as it is.

Example · Fictional business
The dashboard’s recording setting with its default choice, and the opening a fictional business’s callers would hear. Intro and hints reworded to match what each choice does. A settings card titled Recording disclosure with two choices: Record calls (default), selected; and Don’t record calls, which records no audio and saves no transcript to the call history, though the call is still transcribed in real time. The disclosure message reads: This call is recorded and transcribed. Below it, the opening a caller hears: You’re speaking with an AI assistant, and this call is recorded and transcribed. Then the business greeting.

The recording notice has two settings.

“Record calls” is the default: the call is recorded and transcribed, and the default notice says so. Choose “Don’t record calls” and no audio is recorded, and no transcript is saved to your call history. The call is still transcribed as it happens so Sí Call can answer, and the default notice says “This call is transcribed in real time.” instead. Neither setting goes by state: the notice plays wherever your business or your caller is.

What each setting does

Both open the call with a notice, wherever your business or your caller is.

SettingCallers hear first (default wording)Audio recordedSaved to your call history
Record callsDefaultThe AI sentence and “This call is recorded and transcribed.”YesA link to the recording, the transcript and a summary
Don’t record callsThe AI sentence and “This call is transcribed in real time.”No. The call is still transcribed in real time so Sí Call can answer.No recording or transcript

If a caller objects to being recorded, Sí Call is instructed to offer to take their number so a person can call back, and not to press them to stay on the line.

This describes how the product behaves. It isn’t legal advice, a lawyer’s review of these settings is still pending, and the recording rules that apply to your business are yours to check.

See how a call works, start to finish
Call data

What we keep from a call, and what we strip out.

When a call ends, Sí Call files a record in your dashboard. Here’s what goes in it, what’s removed before it’s saved, and how long it’s meant to stay.

The call record

What each record holds.

  • If recording is on, the transcript, turn by turn, and a short summary.
  • The caller’s number, and when the call came in and how long it lasted.
  • An outcome, such as “Follow-up needed”. It’s worked out from keywords in the call, so treat it as a first guess.
  • If recording is on, a link to the audio. The audio file itself is kept by our voice platform, not in our database.

A call that qualifies also files a separate lead in your leads list, with what the caller wanted, a score from 0 to 100 and a stage. The call record doesn’t show or link to it.

Example · Fictional business

CallsToday

Saved 2:15 PM

Dana Reyes

(415) 555-0188Today, 2:14 PM · 52 s

Follow-up needed
Reason

Water heater leaking

Summary

The water heater in Dana’s garage is leaking at the base. Wants a service visit soon; home weekday mornings.

Suggested next stepFollow up within 24–48 hours

Transcript excerpt

  1. Sí Call0:00

    AI notice You're speaking with an AI assistant, and this call is recorded and transcribed. Thanks for calling Cedar & Main Plumbing. How can I help?

  2. Dana0:07

    My water heater is leaking all over the garage floor. Can someone come today?

  3. Sí Call0:13

    I’m sorry to hear that. I can’t confirm a same-day visit, but I can take a message so the team can call you back. What’s your name?

Card numbers and Social Security numbers are removed from the stored transcript and summary.

When a call qualifies, a separate lead is filed in Leads with a score from 0 to 100.

Example call record for Cedar & Main Plumbing, a fictional business. Caller Dana Reyes, (415) 555-0188, called today at 2:14 PM for 52 seconds about a leaking water heater. The record shows the reason, a two-line summary, the outcome (follow-up needed), the suggested next step (follow up within 24 to 48 hours) and the first lines of the transcript, which open with the AI notice. A note under the record says that when a call qualifies, a separate lead is filed in Leads with a score from 0 to 100.

Redaction

Card and Social Security numbers, removed.

Before a transcript or summary is saved, anything shaped like a 16-digit card number or a 9-digit Social Security number is replaced with a marker.

It works on the text we save. The audio recording isn’t redacted, so it still holds what was said, and neither is the copy of the transcript our voice platform keeps. Because it matches patterns, it can miss a number read out in an unusual way. Sí Call doesn’t take payments over the phone.

Example · Fictional business
A caller line to a fictional business, as spoken and as saved. The number is a standard test card. On the call, the caller reads out a card number. If recording is on, the audio keeps it as spoken. In the saved transcript the number is replaced with the marker [CARD REDACTED], and it is removed from the summary too.

How long records stay.

Call records and transcripts are meant to be deleted after a retention period set by your plan, 90 days by default. The code that deletes them is written, but the schedule that runs it isn’t switched on yet. Until it is, nothing is deleted automatically.

  • 1 at launch
  • 3 coming soon

Keeping, exporting and deleting

What you can do with your records, and what isn’t running yet.

  • Download your call list and your leads as CSV filesAt launchFrom the dashboard. The files open in any spreadsheet.
  • Call records and transcripts deleted after 90 daysComing soonThe period is set by plan; this is the default. The deletion job is written, but its daily schedule isn’t on.
  • Delete your whole workspace from settingsComing soonThe request works, with 7 days to change your mind. The job that carries it out isn’t running yet.
  • A full export of your workspace dataComing soonThe request works. The job that builds the file isn’t running yet.
Security

Security practices we can point to in the code.

Each item here is something the code does today, described no more broadly than it’s true. If we can’t point to it, it isn’t on this list.

  • HTTPS, enforced.

    The site and your dashboard load only over HTTPS, and browsers are told to insist on it:

    HTTPS enforced by HSTS (max-age 1 year, includeSubDomains, preload)

    Phone calls travel over the phone network, which HTTPS doesn’t cover.

  • Encrypted at rest by default.

    Your records are stored on Google Cloud and Firebase, which encrypt stored data by default. We don’t run separate keys of our own on top.

  • Secrets kept out of our logs.

    Our logger masks API keys, tokens, passwords and other credentials it recognizes before a line is written. In production it also masks email addresses, phone numbers and card-shaped numbers.

  • Dashboard changes checked for forgery.

    A change you make while signed in has to come from our own site. That stops another website from sending one in your name.

  • Outside services prove who they are.

    Payment events from Stripe are signature-checked. Call events from our voice platform must carry a shared secret, compared in a way that doesn’t leak it through timing.

  • The owner holds the big switches.

    Only the owner of a workspace can ask for a full export of its data or for the workspace to be deleted.

Found a problem?

Report a security problem.

Email security@sicall.ai with the steps to reproduce it, what it lets someone do, and any proof of concept.

  • Give us a reasonable window to fix it before you publish anything.
  • While testing, don’t access other people’s data, destroy data or slow the service down.
  • We’ll confirm we have your report and keep you posted while we fix it.
  • We won’t pursue legal action over good-faith research that follows these rules.
/.well-known/security.txt
# Security policy for Sí Call (RFC 9116)
# If you believe you have found a security vulnerability, please report it
# to the contact below. We appreciate coordinated disclosure.

Contact: mailto:security@sicall.ai
Expires: 2027-06-11T00:00:00.000Z
Policy: https://sicall.ai/security
Canonical: https://sicall.ai/.well-known/security.txt
Preferred-Languages: en
Our security.txt file as published, at the address security tools check first, less a maintenance note to ourselves. It points reporters at the security mailbox.
Said plainly

What we don’t have yet.

A security review goes quicker when the gaps are written down. These are the ones we know of, as of today, including a few a reviewer might not think to ask about.

  • No SOC 2 report

    None

    We hold no SOC 2 report, haven’t engaged an auditor, and have no examination under way. We’ll start one when a customer’s security review needs it, and this line will change when an audit window actually opens.

  • No FedRAMP authorization

    None

    We hold none and haven’t applied. Google Cloud’s authorizations belong to Google and don’t pass to the software that runs on it.

  • No two-step sign-in or single sign-on

    Not yet

    Business accounts sign in with an email and password, or with Google. There’s no second step, such as a code from an app, and no single sign-on through your company’s identity provider.

  • No uptime figure, and no service credits

    Not measured

    We don’t publish an availability figure because we don’t measure uptime yet. There are no outside checks and no alerts that would wake anyone if calls stopped being answered. Today, you telling us at support@sicall.ai is how we find out.

    We’re a small team without a round-the-clock rota, so we don’t promise a response time. Your fallback doesn’t depend on us: you can switch call forwarding off with your carrier.

  • Recordings aren’t redacted

    Not yet

    Card and Social Security numbers come out of the transcripts and summaries we save, not out of the audio recording, so it still holds what was said.

  • Our voice platform’s copy isn’t redacted or deleted

    Not yet

    Vapi, the platform that runs each call, keeps its own copy of the transcript, and of the audio when recording is on. That copy isn’t redacted, and our deletion code doesn’t reach it yet, so deleting a record here doesn’t delete it there.

  • Automatic deletion and full exports aren’t running

    Not yet

    The daily jobs that remove expired records, carry out workspace deletions and build full exports are written but not switched on. Nothing is deleted on a schedule until they are.

  • No lawyer’s review yet

    Pending

    Counsel hasn’t reviewed the notice settings, our terms or our Data Processing Addendum yet. The addendum is published as a template, marked as pending legal review.

  • No healthcare calls

    Not offered

    We don’t take calls for medical or dental practices. That waits until we reach HIPAA readiness and have a Business Associate Agreement a lawyer has reviewed, and we have neither today.

Subprocessors and legal documents

Who handles a call, and the documents behind it.

A call passes through a handful of providers on its way to your dashboard. Each one is named on our subprocessors page, along with its data protection terms.

Providers

Named, with their terms.

On a live call, Twilio carries the call and Vapi runs the conversation. Deepgram turns speech into text, OpenAI decides what to say and Microsoft Azure speaks it. Google Cloud and Firebase store the record. Our subprocessors page names each of them, with its region and its data protection terms.

Our Data Processing Addendum commits us not to sell personal data, or to share it for advertising that follows people across other sites and apps.

It’s published as a template pending legal review. To sign a copy for your business, write to legal@sicall.ai. For questions about personal data, write to privacy@sicall.ai.

See all our legal documents
Illustrative
The path of a call
  1. Phone networkTwilioCarries the call to Sí Call.
  2. Voice platformVapiRuns the conversation. Keeps its own copy of the transcript, and of the audio when recording is on.
  3. Speech to textDeepgramTurns what the caller says into text.
  4. Language modelOpenAIDecides what to say next, from your business info.
  5. VoiceMicrosoft AzureSpeaks the reply.
  6. Your dashboardGoogle Cloud and FirebaseStores the call record, transcript and summary.
Simplified from our subprocessors page, which is the full list, with each provider’s region and data protection terms.
  • Legal

    Subprocessors

    Each provider that processes customer data, what it does, where, and its data protection terms.

  • Legal

    Data Processing Addendum

    Our commitments as a processor of your customers’ data. Published as a template pending legal review.

  • Legal

    Privacy policy

    What we collect from visitors and customers, why, and who to write to about it.

  • Legal

    Terms of service

    The agreement that covers using Sí Call, including billing and cancellation.

Questions

What owners and reviewers ask us.

Short answers. The sections above have the detail.

Does Sí Call tell callers they’re talking to an AI?

Yes. The opening words of each call say so, and that part can’t be switched off. If your own greeting already says it’s an AI, it isn’t repeated. If a caller asks later in the call, Sí Call is instructed to confirm plainly that it’s an AI assistant.

Can I turn call recording off?

Yes. Choose “Don’t record calls” and no audio is recorded, and no transcript is saved to your call history. Calls are still transcribed as they happen so Sí Call can answer, and by default the opening notice says so: “This call is transcribed in real time.” The AI notice stays on whichever you choose. “Record calls”, the default, records and transcribes the call, and its default notice says that.

What happens if a caller doesn’t want to be recorded?

If asked, Sí Call is instructed to say plainly whether the call is recorded: with “Record calls”, that it’s recorded and transcribed; with “Don’t record calls”, that it isn’t recorded and is transcribed in real time. If the caller objects to being recorded, it’s instructed to offer to take their number so someone from your business can call back, and not to press them to stay on the line.

Do you have a SOC 2 report?

No. We hold no SOC 2 report and no examination is under way. We’ll start one when a customer’s security review needs it. Until then, this page and the documents it links to are what we can show you, and we’d rather say so than hint at an audit.

Where is our call data kept?

Call records, transcripts and summaries are stored on Google Cloud and Firebase. Our voice platform, Vapi, also keeps its own copy of each call’s transcript, and of its audio when recording is on, and your call record links to that audio. Its copy isn’t redacted, and our deletion doesn’t reach it yet. The subprocessors page lists each provider, what it does, where it runs and its data protection terms.

Can we sign a Data Processing Addendum?

Yes. Our addendum is published as a template pending legal review, and you can ask for a signed copy at legal@sicall.ai. It commits us not to sell personal data or share it for cross-site advertising, and it points to our subprocessors page for the providers we use.

Get started

Let Sí Call pick up. Plans open at launch.

Pledge a Founding 50 spot to hold 20% off Starter, Growth or Pro for 12 consecutive months, or talk to it in your browser first. Pledging is free and needs no card.

Join the Founding 50Try it in your browser
  • PricingPlans from $75 a monthMinutes, calls at once and overage for each plan, what is coming soon, and how billing works.
  • Founding 50Hold 20% off before launch50 spots. Free to pledge, no card, withdraw any time. Confirmed pledgers are invited in pledge order when plans open.

Sí Call — the front desk, answered.

© 2026 Sí Call · All rights reserved