Transparency at Seldeo
Seldeo publishes a semi-annual Transparency Report with aggregate statistics on how governments, rightsholders, and our own moderation systems interact with the Seldeo mobile app and this website. This is the landing page for that program.
When the first report is due
The first Seldeo Transparency Report is scheduled for publication no later than 31 March 2027 and will cover the period 15 July 2026 through 31 December 2026.
Thereafter, each report will be published within 90 days of the end of the reporting period:
| Reporting period | Publication deadline |
|---|---|
| H2 2026 (Jul 15 – Dec 31 2026) | 31 March 2027 — first report |
| H1 2027 (Jan 1 – Jun 30 2027) | 30 September 2027 |
| H2 2027 (Jul 1 – Dec 31 2027) | 31 March 2028 |
| … each half thereafter | +90 days after period end |
When a report is live, it will appear at www.seldeo.com/transparency/<year>-h1/ or .../<year>-h2/.
What each report will contain
Consistent with the Transparency Report Policy that governs the program, each report will publish, at minimum, aggregate statistics on:
- Content moderation — how many items were actioned, by category (child safety, violence, hate, harassment, spam, IP, other), by detection source (user report, hash match, classifier, government legal order, trusted flagger), and by action type. Aligned with EU DSA Article 15.
- Notice-and-action (DSA Article 16) — number of legal-notice reports received, SLA hit rates, and median time-to-action.
- Government requests for user data — subpoenas, court orders, search warrants, wiretap orders, emergency disclosures, and preservation requests, broken down by jurisdiction. National-security process is reported in the USA FREEDOM Act permitted bands.
- Government requests for content removal — number of orders, accounts affected, and the outcome (complied fully, geo-restricted, refused).
- Copyright / DMCA takedowns — notices received, counter-notices, and repeat-infringer terminations.
- Child safety — CyberTipline reports filed with NCMEC, accounts banned for CSAM or grooming, and imminent-harm SLA performance.
- Account security — 2FA adoption, confirmed account-takeovers, and incidents disclosed to regulators under GDPR Article 33 or analogous laws.
- AI-system reliability — material AI-system malfunctions and safety-tooling availability.
Every metric will be published with a written methodology explaining exactly how it was measured, so the numbers can be compared apples-to-apples between periods.
What we will not publish
Individual case detail — no user identifier, IP address, message content, or specific enforcement decision — will ever appear in a report. Neither will information covered by an active non-disclosure obligation, nor anything that would compromise a live safety investigation.
Interim disclosures
Between the semi-annual reports, we publish:
- Ad-hoc bulletins in the news feed for material events (novel legal orders that raise policy questions, large-scale takedown operations, or breach disclosures required by law).
- Incident post-mortems on our engineering blog for material Service outages that affected safety tooling for more than 4 hours.
How to reach us about transparency
- Methodology questions and research collaboration: legal@seldeo.com, subject line "Transparency methodology".
- Journalists writing about a Seldeo transparency report: legal@seldeo.com, subject line "Press – transparency report".
- Verified civil-society researchers requesting aggregate data outside the standard cadence: safety@seldeo.com.
- Postal: Seldeo, Inc., Attn: Legal — Transparency, 1007 Red Wing Dr, Durham, NC 27703, United States.
Related policies
- Privacy Policy — how Seldeo collects, uses, and protects user data.
- Community Guidelines — the rules content on the Service must follow.
- Safety at Seldeo — the user-facing safety toolkit and how to report content.
- DMCA / Copyright Policy — the copyright takedown process.
Changes to this page
The publication cadence, metric list, and methodology may evolve as Seldeo grows. When they do, the version number and effective date at the top of this page are updated and the change is announced in the news feed.