Security at Mise Team

How we protect the data restaurants trust us with.

Version 1 · Effective 30 October 2026

Mise Team holds information about your guests, your staff and your business. This page summarises the controls we use to protect it. The contractual detail is in Annex 2 of our Data Processing Agreement.

Where your data lives

Your data is stored in the United Kingdom (AWS London region) on Supabase, with application servers running in London on Vercel. Both providers hold ISO 27001 and SOC 2 Type II certifications for their infrastructure.

Backups are encrypted and held in the same region.

Encryption

All traffic between your devices and Mise Team uses TLS 1.2 or higher. Plain HTTP is redirected to HTTPS and browsers are told to use HTTPS only (HSTS).

Data at rest, including the database, uploaded files and backups, is encrypted with AES-256.

Passwords are stored as salted one-way hashes. We never see or store card numbers; payments are handled by Stripe, a PCI DSS Level 1 provider.

Keeping venues separate

Every record is tagged with the venue it belongs to. Row-level security policies in the database enforce that a user can only read or change data for venues they are a member of, and server-side functions repeat those checks.

Roles (owner, manager, staff) control which features and data each person can reach. Staff-app features are additionally gated by per-site access.

Accounts and sign-in

Email verification is required to activate an account. Passwords must meet a minimum length and are checked against known leaked-password lists. Sign-in attempts are rate limited.

Sessions use short-lived signed tokens that are refreshed securely; signing out invalidates them.

Application and operations

Security headers (content security policy, frame protection, referrer policy) are applied across the application. Sensitive endpoints are rate limited and inputs are validated.

Dependencies are monitored for known vulnerabilities and updated. Code changes are reviewed before release and deployed through an automated pipeline with preview environments.

An audit log records significant actions in the Service. Server errors are monitored and reviewed daily.

Administrative access to production systems is limited to the proprietor, protected by strong credentials, and used only for support, security and maintenance.

Incident response

If we become aware of a personal-data breach affecting your data we will notify the account owner without undue delay and within 48 hours, with what we know, what we are doing and what you may need to do.

Reporting a vulnerability

If you believe you have found a security issue, email privacy@miseteam.com with enough detail to reproduce it. Please do not access other people's data, disrupt the Service or disclose the issue publicly before we have had a chance to fix it. We will acknowledge reports within 3 working days and will not take legal action against good-faith research that respects these rules.