Security
Table of contents
01Overview
Sparked Mail is built with a security-first design. The service handles DKIM private keys, recipient addresses, and authentication tokens, and every layer of the stack is hardened to protect those assets.
We take security seriously and respond to every report. If you find a gap, please let us know - see section 2. We treat security reports as the highest priority and credit reporters in our Hall of Fame (with permission).
- HTTPS-only traffic, with HSTS enforced on production deployments.
- Bearer-token API authentication with per-IP rate limiting on sensitive endpoints.
- DKIM private keys encrypted at rest on production deployments.
- Signed webhooks (HMAC-SHA256) so you can verify authenticity of every event.
- No third-party analytics or advertising pixels on the dashboard.
- Email bodies are never stored - they are processed in memory and discarded.
Sparked Mail is operated from the United States on infrastructure provided by Sparked Host. We do not publish a physical address - all contact is through our contact form.
02Vulnerability Disclosure
If you believe you have found a security vulnerability in Sparked Mail, please report it responsibly through our contact form with the Security category selected.
We also publish an RFC 9116 security.txt file at the well-known location:
GET /.well-known/security.txt
Our commitments to reporters:
- 48-hour response. We acknowledge every report within 48 hours with a preliminary severity assessment.
- Target remediation timelines based on severity: critical (7 days), high (30 days), medium (90 days), low (best-effort).
- No legal action against reporters who follow responsible disclosure - i.e. who do not exfiltrate data, do not disrupt service availability, and give us reasonable time to remediate before publishing.
- Credit in our Hall of Fame below, with permission.
Out of scope:
- Findings in third-party software we operate but do not maintain (e.g. MariaDB, Cloudflare). Report those to the upstream vendor.
- Reports from automated scanners without a verified proof of concept.
- Best-practice suggestions, missing headers we already set, or theoretical issues without a demonstrated attack path.
Hall of Fame
Researchers who reported valid vulnerabilities and agreed to be credited. Thank you.
- The list is empty so far. Be the first.
03Compliance
Sparked Mail is designed for transactional email and operated with privacy in mind.
- CAN-SPAM Act (US). The service is designed for transactional email. Senders are required to honor unsubscribe requests within 10 business days (see Terms, section 3). Bounces are auto-suppressed.
- GDPR (EU and UK). We are a data controller for account data and metadata. Legal bases for processing are documented in Privacy Policy, section 5. Standard Contractual Clauses are in place with subprocessors for international transfers.
- CCPA / CPRA (California). California residents have the rights to know, delete, and opt out of sale of personal data. We do not sell personal data. See Privacy Policy, section 9 for how to exercise these rights.
- CASL (Canada). Senders must have consent before sending commercial email to Canadian recipients. The Acceptable Use Policy enforces this.
For questions about compliance or to exercise data-subject rights, use our contact form with the appropriate category. We respond within the SLA listed on the contact page.
Back to top