How we handle your data.

Every row of data carries your workspace identity, and the database itself refuses cross-workspace access through row-level security. An automated suite attempts more than one hundred cross-tenant reads and writes on every code change, and the build fails unless every attempt is blocked.

Owner, admin, and coordinator tiers are enforced by the database itself, not just the interface. Members cannot promote their own role, and only owners can grant ownership.

Veztra drafts; your team decides. No buyer message, carrier communication, claim package, or record correction goes out without an operator approving it first.

Every meaningful action is logged to an append-only activity record. Entries cannot be deleted from the application, and the only permitted update is redacting a buyer's personal identifiers when honoring a privacy erasure request.

Designed to honor PIPEDA erasure requests: when a buyer asks a brand to delete their personal data, identifiers are anonymized in place and redacted across tickets, cases, and free text, while the operational records brands must retain stay intact and de-identified.

Integration credentials for your commerce and helpdesk tools are held server-side and never sent to the browser, and they are additionally encrypted at the application layer with a dedicated key. Traffic is encrypted in transit with TLS, and data is encrypted at rest on managed infrastructure (Vercel and Supabase, running PostgreSQL).