Data encrypted in transit (HTTPS/TLS)
Security architecture · any brand · any dealership network
Security summary
Last updated · 1 April 2026
Data encrypted in transit (HTTPS/TLS)
Role-based access control
Immutable audit trail
Store-level data isolation with RLS enforcement
POPIA-aligned data handling
Role-based access matrix
Platform access is separated from dealership access. Support visibility is auditable. Tenant boundaries are enforced in data access and then reinforced in the product layer.
| Role | Access scope | Restriction |
|---|---|---|
| Platform Owner | All dealers, governance rules, audit logs, and implementation oversight. | No platform secrets are exposed client-side. |
| Platform Support | Dealer setup, operational diagnostics, and scoped support actions. | No billing control, no raw key visibility, all actions audited. |
| Dealer Admin | Users, local policies, reporting, and store configuration. | No cross-dealer visibility. |
| Dealer Sales | Inbox, lead actions, bookings, and assigned workflows. | No governance or billing controls. |
| Dealer Marketing | Metrics and compliance views only. | PII and message bodies can be redacted by policy. |
Governance notes
Security contact
Security reviews, access questions, and incident coordination are handled through the platform team with auditable support procedures.
security@autoraos.company