PolpoMail
Security policy

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:

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:

AreaPartnerWhat it protects
Cyber threat intelligenceOneFirewallThe service and its users, by blocking traffic from known malicious sources
Web application protection & next-generation WAFOneFirewallThe website, webmail, admin console and API
Code securityAquilaXThe Polpo Mail source code and the libraries it depends on
Penetration testing, AI red teaming & DASTVulnix0 by OneFirewallThe 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.

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.

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.

Confirmed findings are fixed and then re-tested to make sure the fix works.

How the layers fit together

  1. Before code ships: AquilaX checks our code, its dependencies and secrets.
  2. At the edge: OneFirewall threat intelligence and the next-generation WAF filter traffic before it reaches the application.
  3. In the application: Polpo Mail's own controls (TLS, two-step verification, scoped tokens, rate limits, CSRF protection, sandboxed mail) protect every account.
  4. 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.