DramAuditReturn to site

DramAudit Trust Center

Operational control needs a clear trust boundary.

This page describes the current platform approach. It is not a claim of certification, legal compliance in every customer context, or a substitute for a venue’s own security and privacy program.

Security

Venue-scoped operations

Organizations, memberships, operational cells, devices and printer credentials use explicit venue identities. Server-side authorization scopes customer actions to the venue and role.

Privacy

Private records stay private

Operational content, files and integrations are intended to stay within the authorized venue boundary. Review the Privacy Policy for the applicable notice.

Reliability

Visible operating state

Health checks, device status and structured audit events support troubleshooting. Backups and restore procedures must be monitored and verified as part of production operations.

Responsible AI

Assist, do not invent

Where AI assistance is enabled, it should work from authorized venue context and be reviewed by people. It is not a replacement for accounting, legal, HR or management judgment.

Support access

Explicit, scoped, expiring

Platform health can be monitored without reading private venue content. Access to private operations should require a customer-authorized scope with an expiry and an audit trail.

Report a concern

Security contact

Report security concerns to security@dramaudit.com. Do not include passwords, payment data or private venue records in the first email.

Data and payment boundary. DramAudit should not store raw payment-card data. Payment processing must be configured through an appropriate payment provider, while DramAudit retains only the operational payment context needed for the venue record.