Skip to main content
Brand My Inbox
Get started

Data sovereignty

Email, marketing and CRM data that stays inside your organisation

Yes, you can run email, SMS, WhatsApp, CRM, marketing automation and AI agents without an outside party keeping your data. Installed on your servers, the platform keeps inboxes, lists, consent records, keys and audit logs in your network, and your security team runs access, retention and monitoring on its own.

Plan a sovereign deploymentWhere each deployment keeps data

The cloud is described as it is: hosted, in Europe, with keys we manage.

Where does your data live, and who holds the keys?

The same software in three places. What changes is the location of the data, the owner of the keys and who operates the servers.

Our cloud

Data
Servers in Germany, a managed European database
Encryption keys
Held by our servers
Operated by
We operate it
Fits
Most businesses; live the same day

Your private cloud

Data
Your own cloud account
Encryption keys
Secrets in your account
Operated by
Shared, by agreement
Fits
An existing cloud policy

Your data centre

Data
Your servers, your network
Encryption keys
Secrets on your servers
Operated by
Your team, with our support
Fits
Data that may not leave the network

What stays inside, and what has to leave?

Inside your network, on-premise

  • Inboxes and the Sent folder, encrypted per message
  • Contact lists and each recipient's consent record
  • CRM: contacts, deals, tickets and projects
  • AI conversation transcripts and leads
  • Encryption keys, audit logs and backups

What must travel

  • The message itself, on its way to the recipient's mail server
  • Text messages to your SMS provider, WhatsApp to Meta's official API
  • A conversation's prompt to your AI provider, only if agents are on

Each outbound connection is listed during scoping for your security team to approve.

Running information security on your own terms

Sovereignty is not only where the servers stand. It is who decides. In every deployment your owners and admins set roles, enforce two-factor authentication, choose how long received mail is kept, and decide which fields of the CRM each role may see or change. Hidden fields stay hidden in exports and API answers, and separation between workspaces is enforced in the database rather than on the screen.

Every sensitive action is written to an audit trail kept for 400 days: list imports, permission changes, campaign approvals and new connections, readable on screen, through the API, or by an AI assistant you authorise. AI agents work on your key, with the permissions you grant, and cannot approve a send; a person approves the exact version that goes out.

On-premise, all of that runs in your network and your team holds the keys. The installation is planned with your IT and security teams, described on the on-premise page, and anything your policy needs that the platform does not do yet is built by our custom development team alongside yours.

Related: email security controls · on-premise installation · EmailPro

Clear answers

Data sovereignty: questions organisations ask first

Keep your organisation's data where your policy says it belongs

A scoping call with the people who build the platform, and a written list of what stays in and what has to leave.

Book a scoping call