Enterprise-grade protection, built in
From access controls to audit logs, every layer of Conversion is designed to keep your most sensitive marketing data secure.
SOC 2 Type II certified · GDPR compliant
Used by enterprise teams leaving
Marketo, Pardot, and HubSpot
How access stays under control.
Your identity provider decides who gets in, roles decide what each person can do, and every agent works inside the limits you set.
Generate a SCIM token
Ensure your identity provider (IdP) supports pushing new users and pushing user updates. You will only be able to view the generated token one time.
Provision from your identity provider
SCIM 2.0 creates and updates members from Okta, Microsoft Entra ID, or another provider, and deactivating someone ends their sessions.
Give each role the permissions it needs
Start from Administrator, Manager, Editor, or Viewer, or build a custom role one permission at a time, like editing contacts without deleting them.
Choose what each agent can do
Set every tool an agent has to run on its own, wait for your approval, or stay off. Deletes and edits to live assets ask first by default.
Erase a contact everywhere
Delete a contact from their record, a workflow step, or a request, along with their engagement data and, if you choose, their Salesforce record.
See who changed what, and when.
The audit log records every change across your workspace, from a role's permissions to a workflow going live, with who made it and when. Changes from API keys and agents are recorded the same way.
Audit log
A record of who did what, to which object, and when across your workspace.
Ready for your security review.
Conversion is SOC 2 Type II audited, and our DPA covers GDPR and CCPA. Request the report and review our subprocessors in the trust center.
Visit the trust centerSOC 2 Type II audited
Independent auditors test our security controls every year. Request the latest report from the trust center.
Zero data retention on AI
Every Conversion AI chat and agent model call runs with zero data retention, and your data never trains a model.
Encrypted and hosted in the US
Data is encrypted with TLS 1.2+ in transit and AES-256 at rest, on Google Cloud in the United States.
One thing I really appreciated about the Conversion team was their commitment to building a Salesforce extension that met our security requirements, included detailed logging so nothing fell through the cracks, and held up to our enhanced security standards in a post Salesloft-breach world.
Jayson Lindsley
Director of IT, MyOutDesk
4
Built-in roles, plus custom roles with the permissions you choose
3
Modes for every agent tool: auto-approve, require approval, or off
48h
To notify you of a confirmed breach, under our DPA
Common questions
What security and IT teams ask before they approve Conversion.
No. Customer data is never used to train, fine-tune, or improve AI models, ours or anyone else's, and our DPA says so. Every model call Conversion AI makes in chats and agents is routed with zero data retention enforced.
Request it through our trust center, where you can also find our subprocessor list and other security documentation, or email [email protected].
Any SAML 2.0 provider, with setup guides for Okta, Microsoft Entra ID, Google Workspace, and OneLogin. You can require SSO for the workspace and create accounts on first sign-in with just-in-time provisioning. SCIM 2.0 creates and updates members from your provider, and deactivating someone there ends their Conversion sessions right away.
Yes. Start from the built-in Administrator, Manager, Editor, and Viewer roles, or create a custom role and choose each permission it grants, across contacts, emails, workflows, forms, audiences, campaigns, and workspace settings. You can clone a built-in role as a starting point.
Yes. The audit log records who changed what, to which object, and when across your workspace, including changes made through API keys and by agents. Filter it by person, action, asset type, or date, open any event to see its old and new values, and export it as CSV or JSON.
Each tool an agent has is set to auto-approve, require approval, or disabled, and you can change any of them. Deletes, edits to live assets, and new contacts ask first by default. No agent can send a blast, publish a form, or turn on a workflow; your team does that. Plays send only the emails your team puts in their pool.
Yes. Every agent run is saved as a session with its full history of messages, tool calls, and approvals, and the changes an agent makes appear in the audit log next to your team's.
Customer data is stored and processed primarily in the United States, on Google Cloud (us-central1). It is encrypted in transit with TLS 1.2 or higher and at rest with AES-256.
Yes. Our DPA covers GDPR and CCPA, includes the EU Standard Contractual Clauses and UK addendum, and names our EU and UK Article 27 representatives. It commits us to notify you within 48 hours of confirming a breach.
Delete a contact from their record, with a Delete contact step in a workflow, or by request. Deleting a contact removes their engagement data too, and you can choose to delete the linked Salesforce lead or contact at the same time.
Bring your security questionnaire.
We'll walk your team through SSO, custom roles, the audit log, and our SOC 2 Type II report during the demo.