Mise

Security

At a glance

Where your data lives

The Mise app runs on Railway in the EU. Your database, files and sign-in run on Supabase in the EU, which is hosted on Amazon Web Services. Files are stored in a private storage bucket that can only be reached through Mise.

Payments are handled by Stripe, which is certified to PCI DSS Level 1. Mise never sees or stores card numbers. Supabase and Stripe are independently audited (SOC 2 Type 2).

Encryption

Who can see what

Every brand (workspace) is isolated by row-level security in the database: each request is checked against the person’s membership of that brand, so one customer’s data can’t be read through another’s account, even by a bug in the app.

Share and portal pages are hidden from search engines, and their views and downloads are recorded for the brand that shared them.

Signing in

Mise has no passwords. People sign in with Google, or with a one-time link sent to their email that works once and expires after an hour. Sign-in is handled by Supabase Auth.

Single sign-on with your identity provider (SAML: Okta, Microsoft Entra ID, Google Workspace) is on the Enterprise roadmap. Tell us if you need it.

AI and your content

Mise sends the content each feature needs, and only that, to its AI providers: Anthropic (Claude) to organise files, search and design; Google’s Gemini API for new photos and video; and Voyage AI to make files searchable by meaning. They process it under commercial terms that do not allow them to train their models on it.

Our own access

Access to production systems is limited to the people who run Mise, protected by multi-factor authentication, and used only to operate the service, fix problems or help when you ask.

We don’t look at your content unless you ask us to, or we need to in order to keep the service safe or meet a legal obligation.

Backups, retention and deletion

The database is backed up automatically every day, and each backup is kept for 7 days. Files are stored on Amazon S3 through Supabase Storage, which is designed for very high durability.

Every edit to a file keeps the previous version, so changes can be undone.

When a brand is deleted, its content is removed from the live service within 30 days and from backups within a further 90 days.

Activity log

On Enterprise, admins and owners see who added, approved, changed, deleted and shared what, plus changes to people, roles, the brand kit, product feeds and the plan, and can download it as CSV. Entries can’t be edited or removed. Activity is recorded on every plan, so it’s there from day one when a brand moves to Enterprise.

Incidents

If we become aware of a security incident that affects your data, we’ll tell the owners of the affected brands without undue delay, and within 48 hours, with what happened, what data was involved and what we’re doing about it. We’ll help you meet any obligations you have to notify others.

Software and vulnerabilities

Mise is built on maintained, widely used frameworks (Next.js, Postgres, Supabase) and its dependencies are kept up to date. Secrets are kept in our hosting provider’s encrypted settings, never in code.

Found a security problem? Email [email protected] with “Security” in the subject. We’ll reply within two working days and won’t take action against good-faith research.

Mise doesn’t hold its own SOC 2 or ISO 27001 certification yet. Our main providers do, and we’re happy to complete your security questionnaire.

Subprocessors

These providers process data for Mise, under contracts that protect it. We give customers 30 days’ notice before adding a new one (see the DPA).

Google, Dropbox and Box are only involved when you choose to import files from them or sign in with Google.

Your data, your control

Questions, security questionnaires or a signed DPA: [email protected].