Security policy and adoption
How we approach security for Polpo Mail, and the specialist cybersecurity companies we work with to protect the service, its code and its users.
Our security policy
Polpo Mail handles business email, so we treat security as part of the product, not an add-on. These are the rules we work by:
- Secure by default. Encryption in transit, DKIM signing, SPF, DKIM and DMARC checks and two-step verification are set up for every workspace, not left as options to discover.
- Least privilege. Services run as unprivileged processes, operator access is separate from customer accounts, and access tokens are limited to the permissions they need.
- Defence in depth. We don't rely on any single control. Traffic is filtered before it reaches us, code is checked before it ships, and the running service is tested from the outside.
- Data minimisation. We don't scan mail for advertising or profiling, and we keep personal data only as long as described in our Privacy Policy. Mail is processed and stored in Germany (EU).
- Fix what we find, first. Confirmed vulnerabilities take priority over new features. Fixes are deployed as soon as they're ready, and dependencies are kept up to date.
- Log and review. Sign-ins, security changes and admin actions are recorded in the activity log, and operator actions in the system console are logged too.
- Tell people. If a security incident affects a workspace, we inform its administrators without undue delay and as the law requires.
The technical details of these controls (TLS, MTA-STS, passkeys, sandboxed HTML mail, blocked remote images and more) are on our Security page.
Security partners
A small team can't be an expert in every area of security, so we partner with specialist cybersecurity companies for the parts where dedicated tools and research make the biggest difference:
| Area | Partner | What it protects |
|---|---|---|
| Cyber threat intelligence | OneFirewall | The service and its users, by blocking traffic from known malicious sources |
| Web application protection & next-generation WAF | OneFirewall | The website, webmail, admin console and API |
| Code security | AquilaX | The Polpo Mail source code and the libraries it depends on |
| Penetration testing, AI red teaming & DAST | Vulnix0 by OneFirewall | The running website and application, tested from an attacker's point of view |
Cyber threat intelligence: OneFirewall
Polpo Mail uses cyber threat intelligence (CTI) from OneFirewall. OneFirewall gathers and validates indicators of compromise, such as IP addresses involved in attacks, scanning, brute-force sign-in attempts, spam and phishing, from a large alliance of organisations that share what they see.
We use this intelligence to recognise and block known malicious sources before they reach the service. In practice that means fewer password-guessing attempts against your account, less abuse of our mail servers, and attackers that are already known elsewhere being stopped at the door instead of being discovered from scratch.
Web application protection and next-generation WAF: OneFirewall
The Polpo Mail website, webmail, admin console and REST API sit behind web application protection and a next-generation web application firewall (WAF) from OneFirewall.
- It inspects web requests and blocks common attacks such as injection, cross-site scripting and malicious payloads before they reach our application.
- It combines rules with threat intelligence, so requests from sources with a bad reputation can be blocked or challenged.
- It limits abusive traffic, such as automated scanning and credential-stuffing bots.
The WAF is an extra layer, not a replacement for secure code. Polpo Mail also protects itself: CSRF protection on every form, strict content security policies, rate limits on sign-in, and HTML mail shown in a sandbox.
Code security: AquilaX
The Polpo Mail source code is checked with AquilaX, an application security platform that finds vulnerabilities in code before it reaches production.
- Static analysis (SAST) of our own code, to catch flaws such as injection, unsafe input handling and insecure configuration.
- Dependency scanning of the open-source libraries we use, so known vulnerabilities in third-party code are found and updated.
- Secret detection, so keys, tokens and passwords are never committed to the code.
Findings are reviewed by our developers and fixed according to their severity, as part of normal development, not as a one-off audit.
Penetration testing and AI red teaming: Vulnix0
We periodically run penetration tests against the Polpo Mail website and application with Vulnix0 by OneFirewall. Vulnix0 tests the live service from the outside, the way a real attacker would.
- AI red teaming: AI-driven attack simulations that explore the application, chain weaknesses together and try the techniques real attackers use.
- Dynamic application security testing (DAST): automated testing of the running website, webmail and API for vulnerabilities such as injection, broken authentication, access-control mistakes and misconfiguration.
Confirmed findings are fixed and then re-tested to make sure the fix works.
How the layers fit together
- Before code ships: AquilaX checks our code, its dependencies and secrets.
- At the edge: OneFirewall threat intelligence and the next-generation WAF filter traffic before it reaches the application.
- In the application: Polpo Mail's own controls (TLS, two-step verification, scoped tokens, rate limits, CSRF protection, sandboxed mail) protect every account.
- Continuously, from outside: Vulnix0 penetration tests, AI red teaming and DAST look for anything the other layers missed.
What this does and doesn't mean
Working with specialist partners makes Polpo Mail considerably harder to attack, but no service can promise to be free of vulnerabilities. We describe the limits of what we can guarantee on our Security page and in our Terms of Service. You can also help: turn on two-step verification, use a separate access token for each mail app, and only show images from senders you trust.
Reporting a vulnerability
If you believe you've found a security issue in Polpo Mail, please tell us privately through our security contact and follow our responsible disclosure policy. Please don't test against other people's accounts or data, and give us reasonable time to fix the issue before making it public.