Security
ONMO verifies identity, workspace membership, and authorization on every authenticated API request. Customer data, advertising credentials, and assets remain scoped to the workspace that owns them.
Authorization
Authorization is re-verified on every authenticated API request.
ONMO re-verifies account status and workspace membership on every authenticated API request rather than relying on a cached authorization decision. If a teammate is removed from your workspace or their account is disabled, subsequent requests no longer inherit their previous access.
Authorization is determined from the user’s verified identity and workspace membership, not from a workspace identifier supplied by the request.
Workspace isolation
Every authenticated request is scoped to the workspace contained in the user’s verified identity.
Requests cannot select another workspace simply by changing an ID or request parameter. If authorization fails, the denied request carries no workspace data forward into the application flow.
Customer data is logically isolated throughout the platform, and access controls are designed to prevent one customer from accessing another customer’s data.
Advertising credentials
AWS KMSConnection credentials for Meta, Google, TikTok and Snapchat are encrypted using a dedicated AWS Key Management Service key.
Credentials are encrypted and cryptographically bound to your workspace.
Encrypted credential fields are cryptographically bound to the workspace, advertising platform, and credential field they belong to. A credential encrypted in one context cannot simply be moved to another workspace or credential field and decrypted there.
Encryption
Data is protected both in transit and at rest.
Infrastructure and identity
ONMO is hosted on Amazon Web Services in AWS us-east-1. Authentication is managed using Amazon Cognito.
Application layer
Controls a technical reviewer will look for, in place across the product.
Engineering process
Security controls are reviewed continuously as ONMO changes.
Every commit and CI run is subject to automated secret scanning. Production builds install dependencies from a committed lockfile, and deployment pipelines do not depend on long-lived cloud access keys.
Dependency security updates are documented and reviewed. ONMO also conducts independent senior engineering security reviews, with findings documented and tracked through remediation.
Data control
Account deletion is available in-product from Profile Settings. Customer data deletion requests, including for connected platform data, can be sent to privacy@onmo.ai. Our connected-platform data policy explains what happens to data when you disconnect a platform.
Database backups retain up to 35 days of history with point-in-time recovery.
ONMO acts within the goals, budgets, campaign scope and permissions you approve. Changes to goals, scope or limits require your approval.
Where ONMO uses third-party AI services to provide creative-generation functionality, processors may include Anthropic, Google, OpenAI, Adobe, and Runway. Use of these services depends on the feature being used and remains subject to ONMO’s contractual, privacy, and data-handling requirements. See the Privacy Policy and the Data Processing Addendum.
Enterprise security questionnaire, architecture, data-handling, or vulnerability disclosure questions can be sent to security@onmo.ai. Responsible vulnerability reports are reviewed and routed to the appropriate engineering owner for investigation.
We acknowledge security inquiries within two business days.
If your team needs additional information about ONMO’s architecture, integrations, access controls, processing practices, or enterprise security requirements, contact security@onmo.ai.
Contact Security