Legal & Trust
Last updated: June 2026
This page describes the controls that are live today and the ones we are actively working toward. We have kept it honest: where something is in progress, we say so, rather than implying a certification we do not yet hold.
Every organization’s data is isolated at the database layer using row-level security. Access is scoped to the caller’s organization on every query, so one customer cannot read or write another customer’s data. This is enforced in the database, not only in application code.
Data is encrypted in transit using TLS and at rest by our infrastructure providers. OAuth tokens for third-party integrations are additionally encrypted at the application layer with AES-256-GCM, and encryption keys are never written to logs.
Role-based access control (admin, member, viewer) governs what each user can do, enforced on the server. Production access is restricted to authorized personnel and is logged. Multi-factor authentication and enterprise single sign-on are on the near-term roadmap (see status below).
Security-relevant actions are recorded to an append-only audit log with the actor, timestamp, and source IP address. Administrators can review account activity, and audit export is available to enterprise customers.
Standing controls in the application include:
Errors and anomalies are captured through our monitoring provider. We maintain a health endpoint for uptime monitoring and are building out alerting and a public status page.
We will update this section as controls move from in-progress to live. If you have a security questionnaire, send it to security@benchside.ai and we will complete it accurately.
We welcome responsible disclosure. Email security@benchside.ai with details and steps to reproduce. Please do not test against production data belonging to other customers.
Questions about this page? Email privacy@benchside.ai. For security disclosures, email security@benchside.ai.