Home / Transparency
Transparency
Last updated: 2026-04-25
This page exists so anyone using MDSwap can see what we removed, why, and what broke. We publish a report every quarter. Between reports we publish per-incident post-mortems at /transparency/incidents/YYYY-MM-DD when something material happens.
Live engagement (last 7 days)
Numbers are pulled directly from the production database via the public read API. If a value reads —, no events have been recorded yet for that bucket.
| Metric | Last 7 days |
|---|---|
| Engagement score | — |
| MDs published | — |
| Branches created | — |
| Total MDs live | — |
| Oldest open report (days) | — |
Moderation transparency (current quarter)
First quarterly transparency report ships 2026-07-01. The counters below hydrate from the production database once the first quarter closes.
| Metric | Current quarter |
|---|---|
| Reports received | — |
| Mod actions: hide | — |
| Mod actions: remove | — |
| Mod actions: dismiss | — |
| Mod actions: warn | — |
| Mod actions: suspend | — |
| Mod actions: ban | — |
| Median resolution time (hours) | — |
What we publish
- Reports received, by category (spam, harassment, copyright, illegal, doxxing, NSFW, jailbreak, broken, off-topic, other).
- Reports acted on: hidden, removed, account warned, suspended, banned, dismissed, marked duplicate.
- DMCA notices received, valid, acted on, counter-noticed, restored.
- Government and law-enforcement requests received, by jurisdiction and type, and how we responded.
- Median time to acknowledge a report and to resolve it.
- Incidents with user-visible impact, including duration and root cause.
What we don't publish
We don't publish information that would identify a reporter, an accused user, or a victim. We don't publish content that we removed. We don't disclose specifics of pending investigations. If a request was accompanied by a non-disclosure obligation we'll either fight it or note its existence to the extent the law lets us.
Q1 2026 (placeholder)
The first quarter of public operation has not yet ended. The first full report will be published the first week of the quarter following public launch. Until then this section reads placeholder on purpose.
| Metric | Q1 2026 |
|---|---|
| Reports received | — |
| Reports resolved within 7 days | — |
| Median time to acknowledge | — |
| Median time to resolve | — |
| Content removed | — |
| Accounts suspended | — |
| Accounts banned | — |
| DMCA notices received | — |
| DMCA notices acted on | — |
| Counter-notices received | — |
| Government / LE requests | — |
| NCMEC reports filed | — |
Incidents
None yet. When one happens, a permalink will appear here at /transparency/incidents/YYYY-MM-DD with what happened, when, who was affected, root cause, and what changed afterward. We aim to publish within 7 days. We do not edit incident posts after publication; corrections go in a dated addendum.
How we measure
Numbers come from the reports, mod_actions, and incidents tables in the production database, snapshot at quarter-end. The query SQL is part of the report. If you spot an inconsistency, email us; we'll either correct it or explain why it's right.
Analytics & observability
We use three observability tools in production. None of them receive your email, your handle as a user identifier, or your raw IP. The full list lives in Privacy; here's the short version:
- Sentry — client + server error events; sensitive fields scrubbed before send.
- Google Analytics 4 — aggregate sessions, top pages, top referrers, and our existing custom event names (copy / download / share / publish, etc.). Forced
anonymize_ip; Google Signals + ad-personalization signals disabled. The forwarder honoursDNT: 1— if your browser sends Do-Not-Track, no GA event leaves the page. - Internal swap_engagement_events — the score column on a swap is computed from these; rows are deduped to one per source per minute and trimmed nightly via pg_cron.
Status
Status pages: Vercel: vercel-status.com · Supabase: status.supabase.com
Weekly newsletter
Five new MDs + one essay every Friday. No drips, no upsells, one-click unsubscribe.
Contact: muhammedeliwat@gmail.com