Enterprise & Security
Enterprise Security & Dedicated Infrastructure
By default every company shares one operations database with logical isolation. A dedicated operations environment is available only by separate agreement — not as a self-serve plan.
Security & Governance
Data ownership
Operational records of your company remain your company’s property. We process them to run the product. We do not sell customer lists.
Tenant isolation (RLS)
Company boundary is the default, enforced with Row Level Security (RLS) and application filters. Another organisation cannot read your operational rows in the shared environment. Cross-company access exists only where you enable an explicit fleet-share relationship.
Access control & MFA
Staff permissions follow company membership and roles (RBAC). Multi-factor authentication (MFA) and session controls are available for staff accounts. A URL does not grant access.
TLS & AES-256 encryption
Web and API traffic use TLS. Databases and file storage use AES-256 encryption at rest at the infrastructure layer. HTTPS terminates with managed TLS certificates.
Export & backups
Key registries can be exported from the workspace. Company files use managed object storage in the same operations boundary. Infrastructure-level backups run continuously; recovery objectives are shared in diligence.
Dedicated operations environments
For operators that need physical separation of operational data, we can provision a dedicated single-tenant operations environment by separate agreement. Same product; storage boundary changes. Not a published tariff and not a button in the workspace. The platform model catalogue and CARMASY marketing site remain shared.
Physical separation of operations data
A dedicated environment holds your company’s full operations dataset: vehicles, customers, bookings, agreements, billing, company users, and company files.
Capacity not shared with other customers
Compute and storage for that environment are not shared with other customers’ workloads on the shared multi-tenant database.
Same product, different storage boundary
You keep the CARMASY operational suite and ongoing platform releases. This is not a custom software fork.
Provisioning & retention
Backup and retention parameters are agreed at provisioning, together with migration onboarding for that environment.
Compliance & diligence review
We support enterprise procurement, technical security questionnaires, and formal Data Processing Agreements (DPA). Platform infrastructure maintains SOC 2 Type 2 and ISO 27001.