Foo AI Corp.

Your recordings stay yours

New recordings keep their source audio on your device. If you choose workspace processing, the audio is streamed temporarily through Voicecape to Soniox for real-time transcription. Voicecape does not store the audio in the cloud, and Soniox does not retain the stream. The resulting workspace transcript and summary are stored as encrypted text.

Last updated 2026-08-05

No model training

Workspace processing is optional and starts only after you choose it and confirm the workspace processing notice. Voicecape reads the saved local source in bounded pieces and streams it through the Relay to Soniox in real time. The Relay forwards audio without storing it; Voicecape requests Soniox’s no-storage real-time mode, and neither side keeps source audio from that stream. The transcribed text is then sent to the language-model provider our server is set to — currently OpenAI, L.L.C., reached through the Cloudflare AI Gateway — which produces the summary, decisions and action items. Audio is not sent to that provider.

Which companies those are, and what each one receives, is set out in the Privacy Policy and generated host by host in the Trust Center.

Storage scoped to your organization

Workspace text — the transcript, summary, decisions and action items — is stored in encrypted envelopes in the Voicecape database operated by Supabase, Inc. (Seoul region, ap-northeast-2). Authorized Voicecape services open that text only while performing an allowed workspace operation. Source audio is not part of this storage.

Who can open what

Five roles — owner, admin, manager, member, viewer — with departments that mirror your org chart and access control at the folder level. A viewer can be granted read and nothing else; the database enforces that, not only the interface.

When someone creates a share link, that summary becomes readable by anyone holding the link until it is revoked. That is the one path by which a summary leaves the roles above, and it is deliberate.

How long it stays

New recording source audio has no Voicecape or Soniox cloud copy; you control the device copy. Encrypted workspace text remains until you delete it or the workspace retention policy removes it. Recordings made by retired versions may still have historical cloud-stored audio. Those historical objects remain covered by the workspace Trash and retention rules: deletion can be restored for up to 30 days unless a shorter retention policy applies, then the audio, transcript and summary are removed.

You can delete a recording, a summary, or the whole account from inside the product. Account deletion is described step by step in the Privacy Policy.

Masking personal identifiers

An admin can switch on pattern-based masking of personal identifiers in new transcripts, on any plan. It is off until someone turns it on, and it applies going forward — it does not rewrite transcripts you already have.

What it replaces, and with what: card numbers become [card number], account numbers [account number], phone numbers [phone number], and national identity numbers [national ID]. Card numbers are Luhn-validated in any format, so a number that cannot be a card is left alone. Account numbers are matched at 9 to 19 digits and only next to a banking word, which is why an amount or a date is not touched. Phone and identity patterns follow your workspace language setting rather than the language of the sentence.

Where the full list lives

This page says what we do. The Privacy Policy is the legally operative document and names every recipient in legal terms; the Trust Center is generated from the code and lists every host the app can reach. If those three ever disagree, write to us — that is exactly the report we want.

Back to voicecape.com