Security

Isolation by structure, not by promise

Every business’s data sits in its own database. Not a shared table with a tenant column — a separate database, reached over a separate connection. A query cannot cross between accounts because there is no table for it to cross into.

That is the difference between an isolation policy and an isolation guarantee. A policy is code somebody has to remember to write. This one is the shape of the system.

Access control

• Roles determine what each user can see, and the same rules apply to reports, screens and Revire Assist alike — a cashier cannot ask their way to owner-only figures
• Users scoped to a store see that store’s data, not the group’s
• Every override is written to an audit log with a name and a timestamp

Data in transit and at rest

• All traffic is served over TLS
• Databases are not exposed to the public internet
• Backups are taken regularly and restore is rehearsed, not assumed

Staff access

Revire staff reach production data only to resolve a fault or at your request. That access is logged. We do not browse customer data.

What we will not claim

We hold no security certifications at this time. When we do, they will be named here with their scope and date, and not before.

Last updated 22 August 2026. Revire, hello@revire.one.