Security
Security at Orzeko
We build for operators who need clear boundaries between tenants, accountable access, and traceable changes. This page describes our approach — not third-party certifications we have not completed.
Tenant isolation
Every request is scoped to an organization. Data access paths enforce organization context before reads or writes.
Authentication model
Users authenticate through the Orzeko account hub (accounts.orzeko.com) using Orzeko ID. Sessions are validated server-side on each protected route, and organization roles flow into DealerOS permission checks.
Authorization (RBAC)
Permissions are evaluated on the server, not only in the client. Role definitions map to concrete DealerOS capabilities for consistent enforcement.
Audit logging
Security-relevant events and meaningful state changes are recorded with actor, target, and timestamp. Operators can review activity for troubleshooting and access review.
Data storage
Application state is stored in PostgreSQL. Schema changes are managed through migrations. Backups and retention policies follow our operational runbooks.
Encryption in transit
Traffic between clients and Orzeko services is served over HTTPS (TLS). Internal service communication uses encrypted channels within our deployment environment.
Questions about security practices? Contact us. We do not list SOC 2, HIPAA, ISO, or similar certifications here until they are formally completed and verified.