Security review

Data-flow map

Where call, message, dialer and audience data travels through Finn’s subprocessors — the data category each receives and whether it may carry PHI. Prepared for enterprise security reviews; read it with our Data Processing Addendum.

Last updated: October 16, 2026

How region works. Data at rest — call recordings, transcripts, chat conversations, dialer records and other stored data — stays in the region agreed for the workspace (USA, India, Singapore, UAE, UK or Germany (EU); India by default); dialer call recordings are kept by the telephony provider. Real-time processing (telephony, messaging, speech and AI models) uses each provider’s endpoint for that region where one exists, as listed on our subprocessors page, and WhatsApp messages are also processed by Meta. Any transfer outside the workspace region is governed by the Standard Contractual Clauses in our DPA.

Live call pipeline

A single call flows top to bottom. Audio is processed in memory; only recordings and transcripts come to rest, in the region agreed for the workspace. Steps marked “Finn” run on Finn-operated infrastructure and are not third-party subprocessors. Each call touches only the providers in its agent’s configuration; the providers themselves are listed on our subprocessors page.

Call ingress / egress

End caller (public telephone network)

Inbound or outbound voice call over the public telephone network.

PHI:: —
Region:: Caller's network

Telephony

Telephony providers

Live call audio, phone numbers and caller ID. Downstream carrier networks carry calls in transit only and are not subprocessors.

PHI:: Only under a signed BAA
Region:: Workspace region where the provider has one; otherwise USA or EU

Speech-to-text

Finn and speech providers

Caller audio, transcribed in real time. Audio is processed in memory.

PHI:: Only under a signed BAA
Region:: Workspace region; some providers in the USA or EU

AI models

Finn and AI model providers

Transcript text and the agent's instructions; returns the reply. Speech-to-speech models, where an agent uses them, receive call audio instead of a transcript. Customer data is excluded from model training.

PHI:: Only under a signed BAA
Region:: Workspace region for supported models; other models outside it

Voice

Finn and voice providers

The text the agent speaks; returns generated audio. Does not receive caller audio.

PHI:: Only under a signed BAA
Region:: Workspace region where available; otherwise provider's region

Storage

Cloud hosting provider

Recordings (where recording is on) and transcripts at rest, encrypted, in the region agreed for the workspace.

PHI:: Only under a signed BAA
Region:: USA · India · Singapore · UAE · UK · Germany (EU)

Chat message pipeline

A conversation on WhatsApp, website chat, SMS or email flows top to bottom. Messages are stored in the workspace’s chat inbox, which Finn hosts itself. When a business disconnects WhatsApp, Finn stops receiving its messages and its access to the business’s WhatsApp account is removed.

Message in

WhatsApp · Website chat · SMS · Email

Message text and files; the sender's phone number, WhatsApp profile name or email address; delivery and read status. Website chat also receives the page visited and browser/IP data.

PHI:: Not for PHI unless agreed in writing
Region:: Channel provider · website chat: workspace region

Inbox & storage

Finn chat inbox (self-hosted)

Conversations, contacts, attachments, team replies and notes, at rest in the region agreed for the workspace. When a team member takes over a conversation, the AI stops replying.

PHI:: Not for PHI unless agreed in writing
Region:: Workspace region

AI reply

AI model providers

The conversation so far and the agent's instructions and knowledge base; returns the reply. Customer data is excluded from model training.

PHI:: Not for PHI unless agreed in writing
Region:: As listed on /subprocessors

Reply out

The same channel the message came in on

The AI's or a team member's reply and the recipient's number or address. On WhatsApp: free-form replies within 24 hours of the person's last message, approved templates after that.

PHI:: Not for PHI unless agreed in writing
Region:: As step 1

Rep Parallel Dialer

A separate service, with its own database, for a business’s own sales reps, who call leads from the browser or their own phone. Each call touches only the features switched on for that workspace; voicemail detection runs on every answered call.

Rep & dialer

Rep's browser or phone · Finn dialer service

The leads the rep picked (name, number, uploaded columns, consent flags), rep actions, notes and outcomes. Call audio passes through in memory.

PHI:: Not for PHI unless agreed in writing
Region:: Workspace region

Telephony

Telephony providers

Live audio of both sides, lead and rep phone numbers, caller ID. Plays the recording notice when the call is recorded; the telephony provider stores dialer call recordings.

PHI:: Not for PHI unless agreed in writing
Region:: As listed on /subprocessors

Speech-to-text

Speech provider

The first ~15 seconds of each answered call, to detect voicemail; both sides of recorded calls for live transcripts; the AI screener's conversation where AI screening is on.

PHI:: Not for PHI unless agreed in writing
Region:: As listed on /subprocessors

AI model

AI model provider

Transcript text for voicemail detection, call summaries, suggested outcomes and coaching; the AI screener's turns; for lead briefs, the lead's first name, the product and company facts. Customer data is excluded from model training.

PHI:: Not for PHI unless agreed in writing
Region:: As listed on /subprocessors

Voice

Voice providers

The text the AI screener speaks (AI screening only). Does not receive lead audio.

PHI:: Not for PHI unless agreed in writing
Region:: As listed on /subprocessors

Storage

Cloud hosting provider

Call records, outcomes, notes, transcripts, AI summaries, lead names and numbers, callbacks and voicemails, at rest in the region agreed for the workspace. Recordings stay with the telephony provider.

PHI:: Not for PHI unless agreed in writing
Region:: Workspace region

Lead briefs (dialer side path)

Company-research provider

A company domain (from the lead's work email or website) or a company name only; returns public company facts. No lead names, numbers or call content.

PHI:: No PHI
Region:: As listed on /subprocessors

Audience enrichment path

A separate flow, triggered only when a customer uploads an audience for enrichment. It does not touch the live call pipeline or any call content.

Audience enrichment (separate path — not the call pipeline)

Contact-enrichment provider

Customer-uploaded contact identifiers; returns business email and professional profile data only. No PHI, and no voice or call content.

PHI:: No PHI
Region:: As listed on /subprocessors

Platform operations

Supporting services. None receive call audio, call transcripts, customers’ chat conversations or PHI. Chats people start on hirefinn.ai stay on our own Platform.

Payments

Payment providers

Customer billing identity and payment metadata. No call content.