Security you can read. What is in place, and what isn’t claimed.
No badges and no adjectives. Each line below is something the product does today, and the last section lists what it doesn’t have.
Your workspace is yours alone
- Isolation
- Workspaces are isolated in the database. Every table enforces row-level security: people see only the workspaces they belong to, and only what their role allows.
- Roles
- Four roles: Owner, Admin, Member and Viewer. A Viewer is read-only.
- Sources
- A source can’t be edited once it is read in, and evidence is only ever added, never changed or deleted.
Signing in
- Methods
- You sign in with an email address and a password. Single sign-on (SAML) isn’t set up.
- Passwords
- A new password is checked against known breaches before it is accepted.
- 2-step verification
- Fonsent supports 2-step verification with an authenticator app, and a workspace can require it for everyone.
- Sessions
- Sign out other sessions, or sign out everywhere, from Settings → Security.
What AI may do
- On its own
- Fonsent reads freely and makes small, reversible changes on its own, each recorded with an Undo. Deleting, merging, bulk stage changes and new automations are drafted for a person. Email is always a draft.
- Approving
- An agent can’t approve a draft. Only a person can.
- Sending
- Nothing customer-facing leaves unless a person approved that exact message, and it leaves at most once.
- Integrations
- A request made with an API key or through the MCP server is treated as an agent’s request. The same rules apply, and it can’t approve a draft.
Records of what happened
- Audit log
- The audit log lists every change in the workspace, by people, the agent, automations and API clients, with before and after values and undo status.
- API keys
- Fonsent has a REST API and an MCP server. Keys are read-only or editor, and each key is limited to 120 requests a minute.
- Connected accounts
- The tokens for accounts you connect are encrypted before they are stored.
- Trackers
- The app serves its own fonts and loads no third-party trackers.
Where you set it. Account security, as it appears in the product.
Plainly
What Fonsent doesn’t claim.
A security page that lists only strengths tells you little. These are the gaps you would find anyway.
- Certifications
- Fonsent holds no security certification and has not had an independent audit.
- Single sign-on
- Single sign-on (SAML) isn’t set up.
- Password reset
- There is no self-service password reset yet.
Questions
Can someone in another workspace see our data?
No. Every table enforces row-level security: people see only the workspaces they belong to, and only what their role allows.
Can the AI send something without us knowing?
No. Nothing customer-facing leaves unless a person approved that exact message, and an agent can’t approve a draft.
Do you have SOC 2 or ISO 27001?
No. Fonsent holds no security certification and has not had an independent audit. If your review needs something specific, tell us.
How do I report a security problem?
Use the contact form and choose Security. Please don’t include passwords, API keys or customer data in the message.
Can we take our data out?
Yes. Export any object as CSV, or the whole workspace as JSON.
Start with your own records.
Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.
Early access. No payment details are asked for.