Security Policy
Last updated: October 2026
This Security Policy describes the technical and organisational measures HalixonMail uses to
protect your account, your data, and our infrastructure. Please read it alongside our
Terms and Conditions and
Privacy Policy.
1. Our Commitment
1.1At HalixonMail, the security of your account and personal data is our highest priority. We employ industry-standard practices to protect your information at every layer of our platform.
2. Account Security
2.1All passwords are hashed using Argon2id with a server-side pepper and per-user salts. We never store passwords in plain text.
2.2Two-factor authentication (TOTP) is available for all accounts, compatible with Google Authenticator, Microsoft Authenticator, and similar apps. We strongly recommend enabling it.
2.3TOTP secrets are encrypted at rest using AES-256-GCM authenticated encryption.
2.4Two-factor verification is temporarily locked after repeated incorrect codes to prevent brute-force guessing.
2.5All login attempts are audited, including the outcome, timestamp, and originating IP address.
2.6Password complexity requirements enforce a minimum of 15 characters using at least 3 character categories.
2.7Email address changes and forwarding address changes require verification via a link sent to the new address before taking effect.
3. Session Management
3.1Sessions are stored server-side in a distributed database. Your browser only holds an opaque session cookie.
3.2Session cookies are configured with
HttpOnly, Secure, and SameSite=Lax attributes.3.3Anti-forgery (CSRF) tokens are required on all state-changing requests to prevent cross-site request forgery.
3.4Sessions expire after a configurable period of inactivity.
4. Payment Security
4.1All payments are processed by Stripe. We never see, store, or process your card details.
4.2Stripe webhook events are verified using cryptographic signatures before processing.
4.3All pricing is determined server-side and cannot be influenced by client-side manipulation.
5. Infrastructure
5.1The portal is served exclusively over HTTPS. All traffic between your browser and our servers is encrypted using TLS 1.2 or higher.
5.2HTTP Strict Transport Security (HSTS) is enforced with a one-year max-age (including subdomains, with preload), instructing browsers to always use HTTPS.
5.3Our infrastructure sits behind Cloudflare, providing DDoS protection, Web Application Firewall (WAF) rules, and bot mitigation.
5.4Human verification (Cloudflare Turnstile) is required for login, account creation, and password-reset requests to prevent automated attacks.
5.5Third-party scripts are self-hosted and loaded with Subresource Integrity (SRI) checks, so the browser will not execute them if their contents are altered.
5.6Responses include browser-hardening headers to prevent MIME-type sniffing, clickjacking (framing), and referrer leakage.
5.7Account registrations from known Tor exit nodes are rejected to reduce abuse.
5.8Rate limiting is applied to sensitive endpoints to prevent brute-force and enumeration attacks.
5.9TLS certificates are issued by Let's Encrypt, short-lived, and automatically renewed, limiting the exposure window of any single certificate.
5.10We follow the principle of least privilege across our infrastructure. Database accounts, service accounts, and internal APIs are granted only the minimum permissions required for their function.
6. Email Security
6.1All inbound and outbound SMTP connections require TLS encryption (TLS 1.2 or higher). SSLv2, SSLv3, TLS 1.0, and TLS 1.1 are disabled.
6.2DNSSEC is enabled on all domains, protecting against DNS spoofing and cache poisoning attacks.
6.3Outbound mail is signed with DKIM (DomainKeys Identified Mail) using RSA-SHA256, allowing recipients to verify message authenticity.
6.4SPF (Sender Policy Framework) records are published for all domains and inbound mail is checked against the sender's SPF policy.
6.5DMARC (Domain-based Message Authentication, Reporting and Conformance) is enforced. Messages failing DMARC evaluation are rejected.
6.6SRS (Sender Rewriting Scheme) is applied to forwarded mail to preserve SPF alignment at the destination.
6.7The SMTP VRFY command is disabled to prevent address enumeration.
6.8SMTP submission connections are secured with TLS using short-lived, automatically renewed Let's Encrypt certificates.
6.9SMTP authentication passwords (used for sending mail from your purchased address) are hashed using Argon2id with a server-side pepper, the same standard used for account passwords.
6.10Forwarding addresses cannot be set to domains owned by HalixonMail, preventing circular routing.
6.11Purchased email addresses are reserved in the database during checkout to prevent race conditions.
7. Data Protection
7.1We comply with UK GDPR. You can request a full export of your personal data from your profile at any time.
7.2Account deletion requests can be submitted via a support ticket and are processed by our team.
7.3We do not sell or share your personal data with third parties for marketing purposes.
7.4Sensitive information such as encryption keys, API secrets, and passwords are never logged.
8. Responsible Disclosure
8.1If you discover a security vulnerability in our platform, please report it responsibly by contacting us at security@halixonmail.com.
8.2Do not access or modify other users' data.
8.3Do not publicly disclose the vulnerability before we have had a reasonable opportunity to address it.
8.4Provide sufficient detail for us to reproduce and fix the issue.
8.5We appreciate the security research community and will acknowledge valid reports.
Our terms of service are set out separately in our Terms and Conditions, and how we handle your personal data is described in our Privacy Policy.