Platform security
This page describes how we protect the platform that runs Cirrux, what we do today, and what is not in place yet.
Last reviewed: 14 November 2026.
Access to your data#
Production access is locked down
Production systems can only be reached over a VPN, and signing in to them requires a physical security key. Every admin action is audited and logged.
The database and internal services are not reachable from the internet.
Development stays away from production
Building and testing Cirrux needs no production credentials and no production data. Production secrets live in a separate secrets manager, and the AI coding tools we use while building Cirrux are blocked from production systems altogether. Test data is made up, never copied from real mailboxes.
The data center
Cirrux runs on Exoscale, a European cloud provider that has held ISO/IEC 27001 certification since 2018. Our servers are in its Frankfurt zone, in a facility operated by Equinix. Physical security (entry control, surveillance, power, cooling and fire protection) is theirs. Data center staff look after the building and the hardware, and have no login to our systems.
European law only
Cirrux is run by Werk Slim B.V., a Dutch company without a US parent or US investors. That matters: US law such as the CLOUD Act lets US authorities demand data from US companies wherever it is stored, and it has no hold on us. Your mail, files and documents are not stored with US companies. We only hand over data when the law requires it, and we check every request before we do, as set out in our terms. The outside services we use, and what each one receives, are listed in our data processing agreement.
Mail and the web apps#
Mail in transit
All connections to Cirrux are encrypted, including IMAP, SMTP, CalDAV and CardDAV. For mail between servers we publish MTA-STS in enforce mode and DANE records on DNSSEC-signed DNS, so other servers refuse to deliver to us over a connection that is not encrypted or not ours.
Incoming mail is checked by rspamd for spam and phishing and every attachment is scanned by ClamAV, both running on our own servers. Outgoing mail is signed with your own domain’s DKIM key. More on deliverability.
Web apps
The apps are only served over HTTPS, enforced with HSTS. A strict Content Security Policy only allows code we ship ourselves plus our error reporting, which runs in the EU. The apps load no trackers or ads.
We watch for copies of our website on lookalike domains. When one appears, we find out quickly and get it taken down. If you ever see a site that looks like Cirrux on another address, tell us.
Encryption at rest
Every message, attachment and file is encrypted with keys specific to your workspace. The encryption page covers exactly what that protects against and what it does not.
How Cirrux is built#
Code and dependencies
Cirrux is our own code, not a repackaged open source suite. Every dependency is pinned to an exact version, and a new release is only picked up after it has been public for seven days, so a hijacked package is usually caught before it reaches us. Build tooling is pinned the same way, and our infrastructure is defined as code.
Monthly security reviews
Every month we review the code that changed against a written checklist based on the OWASP Application Security Verification Standard, the OAuth security best practices and the Kubernetes security checklist. Each review is written down with its findings, and the next one starts by checking that every open finding was fixed.
Deleted means deleted
Mail, files, documents and events you delete are permanently removed seven days after they leave the trash. When a workspace is deleted, its encryption keys go with it. Our own operational logs are removed automatically after three to 30 days, depending on their level.
If something goes wrong#
We tell you within 48 hours
If we find that your data has been accessed, changed or lost by someone who should not have it, we email your workspace admins within 48 hours of finding out. That first message says what happened, what data is involved as far as we know, and what we are doing about it. We follow up as we learn more, and we notify the Dutch data protection authority where the law requires it.
Certifications#
Cirrux is not certified yet. We are preparing for ISO/IEC 27001 and SOC 2, and keep a register of every requirement in both, plus the Dutch government baseline (BIO2), with where we stand on each. No independent audit or penetration test has taken place so far. The one external assessment is Google’s security assessment (CASA) of Cirrux, which every app with access to Gmail data has to pass.
We would rather tell you this plainly than imply more. If your organisation needs something specific for its own compliance, ask us and we will tell you honestly what we can provide. How we handle your data as a processor is in our data processing agreement, and availability and backups are on reliability and backups.
Reporting a vulnerability#
If you think you have found a security problem in Cirrux, we want to hear about it. This is our coordinated vulnerability disclosure policy.
How to report
Email help@cirrux.co with “Security report” in the subject. Tell us what you found, where, and the steps to reproduce it, and what you think someone could do with it. Screenshots or a short proof of concept help. You can write in English or Dutch.
What we do
- A person reads every report. We reply within two working days to confirm we have it.
- We tell you whether we can reproduce it and how serious we think it is, and keep you posted.
- We fix it as fast as its severity calls for, and tell you when it is fixed.
- If you like, we credit you by name once it is fixed.
We don’t have a bounty program in place, but we look at each case individually and will consider a reward for your efforts, depending on the severity of the find.
Testing within these rules
- Only test against accounts and workspaces that are yours, or that you have permission to use.
- Do not look at, change or delete other people’s data. If you reach any by accident, stop, do not keep a copy, and tell us in your report.
- Do not run denial-of-service attacks, send spam or bulk mail, or try social engineering or phishing on our staff or customers.
- Do no more than you need to show the problem.
- Keep the details to yourself until it is fixed. We aim to fix within 90 days, and we agree on a disclosure date with you.
If you stay within these rules and act in good faith, we will not take legal action against you or report you to the police for your research.
In scope
Everything we run: cirrux.co and cirrux.me, the Cirrux apps and API, IMAP, SMTP, CalDAV and CardDAV, the command-line tool and the desktop app. Not in scope: copies of our site on domains that are not ours (tell us about those anyway), reports from automated scanners without a demonstrated problem, and missing hardening that has no real impact.