Trust center
Security practices
Last updated July 15, 2026
Access and workspace isolation
Cenerio scopes application data to an organization workspace. Membership, organization roles, and budget-level permissions determine what an authenticated user can view or change. Database row-level controls provide an additional enforcement layer for organization-owned records.
Authentication and invitations
Private-beta access is invitation-only. Cenerio uses passwordless authentication and validates organization invitations before granting workspace access. Administrators can manage members and roles from the application.
Salesforce connections
An organization administrator authorizes Salesforce through OAuth and chooses the Campaign fields used for synchronization. Connection credentials are handled on the server and are not exposed to the browser. Administrators can disconnect the integration.
Monitoring, change history, and recovery
Cenerio records operational events needed to investigate failures. Recovery and incident-response procedures are still being developed and validated during the private beta; ask for the current posture before relying on a specific recovery commitment.
Beta data guidelines
Do not submit payment-card data, government identifiers, health information, passwords, or other regulated or highly sensitive information during the beta unless Cenerio has explicitly approved that use in writing.
Report a concern
Send suspected security or privacy issues to hello@cenerio.com with enough detail for us to investigate. Do not include credentials, access tokens, or sensitive customer data in the initial message.