Security FAQ

AtlasGTM operates on Google Cloud. The public website and the signed-in application run as separate application hosts.

Access is gated by authentication, role-based permissions, and company scoping. Encryption, logging, and related controls are described in this Trust Center.

Selected application secrets are encrypted at rest. Broader data-store encryption is available to enterprise reviewers through the Documents request process.

Yes. The public site and application hosts are served over HTTPS (TLS).

Users can sign in with Google, which supports multi-factor authentication at the identity provider. Email-and-password sign-in does not currently require a second factor.

Yes. AtlasGTM uses role-based permissions, groups, and per-user grants. Privileged security capabilities cannot be turned on by default.

Yes. AtlasGTM records platform activity, developer API requests, and governance events in dedicated audit logs.

AtlasGTM orchestrates governed workflows around approved AI providers such as Anthropic, Google, OpenAI, and MCP-connected clients. Data handling follows each provider’s configuration and agreements.

AtlasGTM does not publish a blanket claim that customer data is never used to train models. Provider-specific data-use terms are confirmed during enterprise security review.

External APIs are authenticated and authorized by assigned scopes, with rate limiting and abuse protections. MCP clients use OAuth 2.1. Connector permissions are limited to the customer’s tenant.

SOC 2 Type II preparation is underway, with a target of Q1 2027. AtlasGTM is not currently SOC 2 certified.

Use the Documents page to request additional security documentation. Restricted materials, including the Security Overview, are provided after AtlasGTM security reviews the request.