Privacy Policy
How dmarcproof handles data. We minimize by design: we characterize the servers that send DMARC reports, and we never read the reports themselves.
What we collect
For each connection that delivers a report, we record transport metadata about the sending server: source IP, ASN, network prefix, reverse-DNS/FCrDNS result, HELO/EHLO, TLS handshake details and a fingerprint, the verifying DKIM d= domain, the envelope SPF result, the per-tenant recipient address, and timestamps. For an account, we store your Google sign-in identity (email, name, provider subject) and an encrypted OAuth refresh token.
What we never collect
We never read, parse, or store the DMARC report XML payload — it is discarded unread. We do not collect message content, and we do not accept forensic (RUF) reports.
Why we process it (legal basis)
We process connection metadata under legitimate interest — building a public defense against forged DMARC reports — balanced against the limited, non-content nature of the data and a documented assessment.
How long we keep it
- Raw per-connection records (incl. the client IP) — a rolling window (currently 90 days during development, set to tighten), after folding into a minimal per-identity aggregate.
- Aggregates — decay and purge after 365 days with no re-observation.
- Audit logs — 2 years. Acceptable-use acceptance, disputes, and permission changes — 7 years.
Your rights
You can access your account data, and you can delete your account from Settings — this deprovisions your domains, revokes our access to your Google account, and erases your personal information (your acceptance record is retained, anonymized, as required). For data published about sending infrastructure, we provide a dispute/takedown process.
Cookies
Essential cookies only (your session). No advertising or cross-site tracking cookies.
Contact & governing law
Privacy questions and data requests: [email protected]. This policy is governed by the laws of the State of Florida, USA.