close

Security, without the marketing copy.

How Fluent protects your conversations: what we encrypt, what we never train on, who processes your data, how long we keep it and how deletion works. We list only what we can back up, including what we don't have.

What's true today

Encrypted in transit and at rest.

We use encryption in transit and at rest, and we limit access to production systems.

No training on your conversations.

We don't use your conversations to train AI models. We don't sell your data, and we don't share it for advertising.

Private to your account.

Your conversations are private to your account unless you share them.

Limited staff access.

Staff don't access your conversation content except at your request, to keep the service secure, or when the law requires it.

Who processes your data

We use service providers for hosting, AI processing, transcription, sign-in, email, analytics, crash reporting and payments. They process data only on our instructions and only to run Fluent. The current list is on our sub-processors page. We also share information if required by law, or as part of a merger or sale of the business.

Details of what we collect and why are in the privacy policy.

How long we keep it

Your conversations and account data

Kept until you delete them or your account.

Voice profiles

A person's voice profile is deleted when you delete that person. Deleting your account deletes all voice profiles and this voice data.

Calendar data

Kept only for a short window around your meetings. Disconnecting the calendar deletes it.

Billing records

Our payment provider keeps billing records as the law requires.

Deleting your data

Delete your account in the app under Settings › Delete Account. Deletion is permanent. Our payment provider keeps billing records as the law requires.

For any other request, use our contact page.

What's on the roadmap, not shipped

Per-user encryption keys.

Keys derived from your passcode, so even Fluent's infrastructure operators couldn't read your data. Not shipped yet. We'll say so on this page until it is.

On-device processing.

Audio processed locally on the phone for the parts that don't require cloud compute. In development.

What we don't claim

"You hold the keys."

Not yet — encrypted in transit and at rest today, per-user keys on the roadmap.

"Subpoena-resistant."

Not without per-user encryption. Don't store anything in Fluent you couldn't respond to a subpoena about.

"HIPAA-compliant" or "HIPAA-friendly."

Fluent is not a HIPAA-certified service. We are not pursuing HIPAA certification. Don't use Fluent for protected health information.

"SOC 2 / ISO 27001 certified."

Not yet. Fluent itself does not currently hold those certifications.

"Zero-knowledge architecture."

Not today. The architecture would need per-user encryption first.

Questions

Security questions, vulnerability reports, or curiosity about the implementation: security@becomefluent.io.

Related help: Your data: export and delete · Recording consent