Fonsent

How Fonsent handles your data

A CRM holds your customers' emails and your pipeline. This page says what the app loads in your browser and where your data goes.

No trackers in the app

The app loads no advertising, analytics or session-recording scripts. Its content security policy only lets the browser load code, styles, fonts and images from Fonsent itself, and only talk to Fonsent and your workspace's own database. A third-party script added by mistake would be blocked by the browser.

Fonts are served from Fonsent, not from a font service.

Where your records live

Records, emails you sync, notes, drafts and the change history are stored in your workspace's database. Every table enforces row-level security: people only see the workspaces they belong to, and only what their role allows.

Services Fonsent talks to, and when

Mail and calendar (Google or Microsoft), only after someone in your workspace connects an account, to read new messages and events.

An AI model provider, when you use chat, AI fill or an automation step. The request contains the records and text needed for that task.

An email delivery provider, only for an email a person has approved in For review, sent exactly once.

Services your admins connect in Settings › Connectors, only when the agent uses one of their tools in chat. Each tool asks before every call unless an admin allows it; once a reply has read anything from outside, it asks again before any further outside call. Every call is logged with what was sent and kept for 90 days.

What AI can and cannot do

AI can update records inside your workspace. Every change is recorded with what it was based on and can be undone. It cannot send email or message anyone on its own: outbound messages wait as drafts until a person approves the exact text.

This describes how the software behaves. It is not a legal privacy policy. Back to Fonsent