What gets stored
Every call produces several artifacts, and they do not all live for the same length of time.
| Artifact | Contents | Default retention |
|---|---|---|
| Audio recording | Full call audio, both legs | 90 days |
| Transcript | Text version of the call | 90 days |
| Call metadata | Timestamps, caller ID, duration, outcome | 90 days |
| Post-call analysis fields | Extracted fields defined on the Finn | 90 days |
Recording is on by default. Retention is configurable up to 7 years for regulated industries. Set it under Settings → Privacy, where the retention dropdowns control the window for recordings and transcripts.
After the retention window passes, artifacts are permanently deleted. There is no recovery step, no soft-delete window, and no support path to restore them. If you need call audio for a dispute or an audit that may open months later, set retention long enough to cover it before the calls happen. Shortening retention applies going forward and to material already past the new window.
See call-logs for what the stored artifacts look like when you read them back, and post-call-analysis for how the analysis fields are produced.
Turning recording off
You can disable recording in two places:
- Per Finn, under that Finn's Call Settings.
- Globally, under Settings → Compliance.
Disabling recording stops audio capture. Transcripts and metadata are still produced, because the agent needs the transcript to run the conversation at all. If your goal is to hold no audio, disabling recording is the correct control. If your goal is to hold no text either, retention is the lever, not the recording toggle.
In two-party-consent jurisdictions you must disclose recording at the start of the call. See recording-consent.
Redaction
PII redaction is opt-in under Settings → Compliance → PII Redaction. It removes items like SSNs and full credit card numbers from transcripts.
The audio recording is not affected. A redacted transcript sitting next to an unredacted recording of the same call is a common and avoidable mistake. If the audio itself must not contain the sensitive value, your options are to delete the recording for that call or to design the Finn so the value is never spoken aloud.
Deleting on request
Under GDPR, a person can ask you to delete their data and you have 30 days to comply. Deletion is available through the dashboard and through the API.
The dashboard path is the one to use when you are handling a one-off subject request. Find the calls for that contact in call-logs and delete them there.
For programmatic deletion, use the calls API. Deletion removes the recording, transcript, metadata, and analysis fields for that call.
curl -X DELETE https://api.hirefinn.ai/v1/calls/call_01HXYZ \
-H "Authorization: Bearer $FINN_API_KEY"
See authentication for how to obtain and scope the key, and api-calls for the full call resource.
Two things to check before you treat a subject request as closed:
- Deleting a call does not remove the contact from the audience it was called from. If the contact stays in the audience, a later campaign will call them again. Remove them from the audience as well, or add them to the suppression list.
- Anything you have already exported or forwarded is outside the platform. Webhook payloads delivered to your own endpoint are your copy to delete. See webhooks.
Opt-out is not deletion
These are separate mechanisms and people conflate them.
| Suppression list | Deletion | |
|---|---|---|
| Effect | Number is never called again | Artifacts are removed |
| Scope | Global, every audience and deployment | Per call |
| Past call records | Kept | Removed |
| Triggered by | opt_out post-call field, or manual add | Dashboard or API |
Enable Settings → Compliance → Auto-Suppress on Opt-Out so a detected opt-out adds the number to the global suppression list without manual work. A person who asks to stop being called has not necessarily asked you to erase their records, and a person who asks for erasure has not necessarily asked to stop being called. Handle both requests as stated. See compliance.
Where data lives
Retention interacts with region. If you have EU customers, set the account region to EU at signup, because that is when the choice is made. See data-residency.
What is not settled here
The following are not established by the current platform documentation and should not be assumed:
- Whether deleted artifacts are purged from backups on the same schedule as live storage.
- Whether a bulk deletion endpoint exists for clearing an entire audience's call history in one request.
- Retention behaviour for artifacts after an account is closed.
Contact support before designing a process that depends on any of these.