Transparency Report
Period: Q3 2026 (published 2026-09-14, before this report had anything to hide)
We're publishing this now, at zero, so a later report has a real baseline to be compared against — not so we can start counting only once something happens.
Legal and government requests
- Government or legal requests for customer data received: 0
- Customer accounts affected: 0
- Requests we contested or narrowed: 0
See our law enforcement request policy on the Security page for how we'd handle one.
Security incidents
A "material security incident" here means unauthorized access to, or disclosure of, customer or recipient data — the same bar that triggers our 72-hour breach notification commitment (DPA, Security page).
- Material security incidents this period: 0
Subprocessor changes
- Subprocessors added, removed, or replaced this period: 0
See the current subprocessor list at /subprocessors.
Verification accuracy
We don't yet have enough independently-labeled outcomes to publish defensible per-provider accuracy figures — and we'd rather say that plainly than publish a number that looks precise but isn't backed by real sample size. Ground-truth collection (delivery/bounce outcomes independent of our own verdicts) started this quarter.
- Independent labels collected across all evidence classes: 0
- First accuracy figures ship once sample size supports a real confidence interval, with the sample size published alongside every number, never hidden below it.
We will never publish an accuracy statistic without the sample size next to it. A number from 50 labels and a number from 50,000 will never be presented as equivalent.
Contact
Questions about this report: privacy@skink.dev.