This article answers the questions a security review asks first, in the order they usually arrive: how people sign in, who can do what, what has to be approved before it sends, what is recorded, how data requests are handled, and where the data sits. Every section describes what the product does today, nothing more. For plan limits, see plans and the free trial.
Single sign-on
Fuzegenai signs in through OpenID Connect. The Fuzegenai team configures the provider for your email domain; there is no self-service SSO settings page. Send us three values from the OpenID Connect application in your identity provider: the issuer URL, the client id and the client secret. Okta, Microsoft Entra ID and Google Workspace all issue these. If your provider's discovery document is not at <issuer>/.well-known/openid-configuration, send that address as well.
Once the provider is set, anyone with an email address on that domain chooses Continue with SSO on the login page, enters their work email and is sent to your identity provider. SSO only signs in people who already have a Fuzegenai account: the account is created first, through an invitation accepted with a password or Google, and SSO is then linked to it. Nobody gets an account by signing in through SSO alone.
Anyone who signs in with a password can turn on two-factor authentication from Settings → Profile. It uses an authenticator app (time-based codes) plus ten single-use backup codes. There is no SMS or email code. Fuzegenai's own platform administrators must have it on.
Seats and roles
Teammates join by invitation only, from Organization → General & members. The invitation names the role, and the person accepts it with the email address it was sent to. The roles are owner, admin, editor, member, viewer and client:
| Role | What it can do |
|---|---|
| Owner | Everything, including billing and deleting the organization. Assigned by ownership transfer only. |
| Admin | Everything except billing, ownership transfer and deleting the organization. |
| Editor | Runs campaigns, inboxes, warmup and replies. No organization, billing or member settings. |
| Member | Views and edits campaigns, leads, templates and replies. Cannot delete or archive. |
| Viewer | Read-only across campaigns, leads, analytics and deliverability. |
| Client | An external user who sees only the campaigns and inboxes assigned to them. |
Each role maps to a fixed list of permissions, and every request is checked against the caller's membership. Provisioning and removal are done by an admin on that page; there is no automated directory sync. Removing a member deletes their membership, and the permissions the app caches for them expire within a minute, so their access is gone by then at the latest.
Campaign approvals and policies
Organization → Policies has one switch, Require campaign approval. When it is on, a campaign created by anyone other than an owner or admin opens an approval request the moment it is created, and the campaign cannot launch until someone with the approval permission approves it. Admins and owners are notified of each request. A request can be assigned to a named approver or left for anyone with the permission. It records who asked, who decided, the decision note and when. If the campaign is edited after it was approved, the approval is marked stale so the reviewer can see the change.
Audit log
Two records are kept.
The security log records sign-ins (password, Google, SSO and magic link, successes and failures), sign-outs and revoked sessions, account lockouts, support impersonation (start and stop, with the reason given), API keys created or revoked, campaign approval requests, data requests and data exports. Each entry carries the actor, the time and the action; sign-in entries also carry the IP address. This log is held by Fuzegenai; ask us for your organization's entries when you send the questionnaire.
Organization → Audit logs shows workspace activity by member, by action and over time, and exports it as a file. Owners, admins and viewers can open it.
Audit history is kept for 365 days on Enterprise, 180 days on Professional and 30 days on Starter.
Data requests
Organization → Data & privacy is where data subject requests are handled. Create a request for a subject's email address with one of four types: export, delete, rectify or opt out. The queue shows open, overdue and in-progress requests against a 30-day deadline. From a request you can generate an export of everything the workspace holds on that address (leads, inbox messages and related records), or run the deletion. A consent register on the same page keeps what each contact agreed to and lets you revoke it.
Where data is stored
Fuzegenai runs on Amazon Web Services in the United States, in the N. Virginia region (us-east-1). The application and the database live there.
Google and Microsoft mailboxes connect through OAuth, so Fuzegenai never holds the mailbox password for them. Mailboxes connected over SMTP and IMAP keep those credentials in Fuzegenai's database for the send and sync workers to use. API keys are stored as a one-way hash and shown once, at creation. For the vendors that process data on our behalf, see the privacy policy.
What to send us
Three things, in any order:
- Your security questionnaire. We answer it from the sections above.
- Your identity provider details for SSO: the email domain, issuer URL, client id and client secret.
- Your contract terms, including a data processing agreement if you need one, and how you want to be invoiced.
Book a demo to start, or read the enterprise overview. The call covers your volume, your team and these controls, and the SSO setup is done alongside you.