Security & Trust

A per-change audit trail

Every action that changes data — a sale, an expense, a cost update, a role change, a workspace setting — writes an immutable audit record capturing who did it, what changed, and when.

When a Mezbano administrator works inside your workspace on your behalf, that access is recorded as impersonation and the audit record attributes the change to the administrator, not to you. Support access never hides behind your identity.

Financial month locks

When you finalize a month, that month’s sales, expenses, labour, and purchases are locked against edits so your closed books stay closed. The lock is enforced at the database, not just in the interface.

Owners and admins can finalize a month; reopening a finalized month is restricted to the workspace owner, because it reverses a financial-control decision.

Optimistic concurrency on edits

On editors where saving replaces a whole record and its children — recipes, checklists, daily sales — Mezbano checks that no one else changed the record since you opened it. If they did, your save is rejected with a clear conflict message instead of silently overwriting their work.

Two-factor authentication and workspace security policy

Any user can turn on time-based two-factor authentication (an authenticator app) for their account. A workspace can go further and require two-factor authentication for its owners and admins, so privileged access always carries a second factor.

Each workspace controls its own sign-in policy, so a stricter operator is never held back by a more relaxed one.

Brand-scoped tenant isolation

Your recipes, ingredients, costs, SOPs, and checklists are brand-scoped: another brand on Mezbano cannot see or reach them. Store, brand, and platform roles are separated, and access is checked on every request against the workspace you are acting in — not trusted from the browser.

The one deliberate exception is the standard chart of expense and revenue categories, which is shared so that reporting stays consistent and comparable across the platform. That standard chart is a feature, not a leak of your operating data.

Encryption in transit and at rest

All traffic runs over HTTPS with HTTP Strict Transport Security, so data moving between you and Mezbano is encrypted end to end. Data at rest is encrypted by the underlying Cloudflare platform that hosts the application, database, and file storage.

Automated backups and disaster recovery

The database is backed up automatically every night to object storage. The backup path also carries an off-provider replication seam that can copy each backup to a second location, off the primary provider, once it is enabled for an environment — so that a backup can survive even the loss of the primary account. Continuous point-in-time recovery covers the most recent 30 days.

Our published objectives are a Recovery Point Objective of 24 hours or less (how much data a worst-case incident could cost you) and a Recovery Time Objective measured in hours, with the restore procedure documented in an internal runbook.

Safe, reviewed database changes

Schema changes never touch production directly. Each one is first replayed against a fresh clone of the production database and compared for drift; only a clean replay is allowed to apply. Changes are strictly additive by policy — we do not run destructive operations against your live data to ship a feature.

Deploys gated by an automated test floor

Every release is gated by an automated test floor: a deploy cannot proceed unless a dedicated suite of security and authorization tests passes first — the release command runs them and stops on the first failure. Isolation, permission, and abuse-resistance behaviours are pinned by those tests so a regression fails the build instead of reaching you.

Reporting a security concern

Found something that looks wrong, or have a question about how your data is handled? Email support@mezbano.com and we will route it to the right person. See our subprocessors for the third parties that help us run the service, and the privacy policy for how we handle personal data.