Skip to main content

Data handling

Your data, and our AI models

The two questions every AI review asks — “do you train on our data?” and “do your model providers keep it?” — answered plainly. The answer to both is no.

Last updated: July 18, 2026

No training on your data

Neither Finn nor our model providers train, fine-tune, or improve models on your calls, transcripts, or contacts.

Zero data retention

Model APIs run in zero-data-retention mode — providers process a request and retain nothing.

Transcript, not audio

Language models receive transcript text, not raw call audio — with one exception, noted below.

No training

Your calls are not training data

Finn does not use Customer Data — call recordings, transcripts, prompts, or uploaded contacts — to train or improve any model, ours or a third party’s. Your data is processed only to deliver the service you configured, and for nothing else.

Every model provider in our pipeline is engaged under an API tier whose terms prohibit training on inputs and outputs. This is contractual, not best-effort.

Zero data retention

Model providers keep nothing

Our language-model APIs are configured for zero data retention: the provider receives a request, returns a response, and does not store the prompt or the output. There is no rolling retention window on the provider side, and nothing to be logged, mined, or exposed later.

OpenAI

Zero-data-retention API; no training on inputs or outputs.

Anthropic

Zero-data-retention API; no training on inputs or outputs.

Google

Zero-data-retention API; no training on inputs or outputs.

Microsoft

Zero-data-retention API; no training on inputs or outputs.

What the models receive

Transcript in, response out

Language models receive transcript text and prompts — not raw call audio. The one exception is OpenAI’s Realtime API, a speech-to-speech path that ingests audio directly; where it is used, that is disclosed in our data-flow map. Speech-to-text and text-to-speech providers process only the audio or text needed for their step and return the result.

The full path — which provider receives which data category — is documented in our data-flow map, and the providers themselves are listed on our subprocessors page.

Retention & deletion

How long data is kept, and when it goes

Storage window

Recordings and transcripts are held in your workspace region for a configurable cache window — 90 days by default — then aged out. You can shorten it.

On termination

When an agreement ends, Customer Data is returned or deleted within 30 days, as set out in our DPA.

Per provider

Model APIs retain nothing (zero-data-retention). Telephony carriers apply their own regulatory retention to call metadata. Only your workspace storage holds to the cache window above.

Export & erasure

You can request export or deletion of Customer Data at any time — email [email protected].

These commitments are contractual. The training and retention terms sit in our Data Processing Addendum; the providers and their roles are on our subprocessors page. For a signed statement or a security-review copy, contact [email protected].

Get started

Hire Finn and scale with confidence.

Move from idea to live voice automation — securely, reliably, and without operational risk.

Book a Demo

Fort-nightly Launches

We move quickly and get you what you need

Powerful Tools

Pre-built dashboards, reports, automations, more