Security & Trust
How Atlas.Moda is designed to protect connected work data.
Read-only first
Google onboarding requests read-only Workspace scopes. This reduces the blast radius of a compromised or mistaken workflow during initial use.
Scoped authorization
Atlas.Moda uses OAuth authorization rather than asking users to share Google passwords. Access can be revoked through the user's Google Account.
Server-side controls
Authentication and connected-source tokens are handled server-side, and the application uses HTTPS, row-level database security, and private server-side service identities for protected operations.
Action gating
Low-risk reversible work may be automated only when trust conditions are met. Sensitive, consequential, irreversible, financial, legal, security, or account-changing actions are designed to require stronger review controls.
Data minimization
Atlas.Moda is designed to favor compact derived context over unnecessary raw source-data duplication and to keep connected workspaces logically isolated.
Google Limited Use
Use of information received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.