Takedown and reporting process
Status: Draft — counsel review required
Version: 0.1.0-draft
Last-updated: 2026-07-20
Use this process to report illegal content, privacy concerns, defamation concerns, misattribution on the map or dataset, or other breaches of TUNES rules.
1. How to report
Email: manglekuo@gmail.com
Subject line: TUNES report — [illegal | privacy | defamation | dataset | other]
Include:
- URL or contribution / comment ID (if known)
- Description of the problem
- Why you believe action is needed
- Your contact email for follow-up
- For privacy/erasure: what personal data you want removed and any account identifier
Do not send illegal images or CSAM in email. If you believe child sexual abuse material is present, report via the in-product report control if available and/or to the appropriate authorities; describe the location of the content without attaching the material.
2. What we will do
| Step | Target (volunteer-proportionate) |
|---|---|
| Acknowledge receipt | Within 5 working days |
| Initial assessment | Promptly for clear illegal content; otherwise within 15 working days where capacity allows |
| Outcome | Remove/hide content, reject report, request more info, or escalate |
Significant account penalties get a short reason and an appeal path (see moderation policy).
3. Privacy and erasure
Data subject requests (access, erasure, etc.) should go to manglekuo@gmail.com (may be the same address). See the privacy notice.
If personal data was published in an open release, we will remove it from operational systems and future versions where required, and take reasonable steps regarding online copies we control. We cannot erase third-party downloads.
4. Defamation and operator concerns
If you believe content is defamatory or wrongly implies TfL/operator endorsement or failure:
- Identify the exact words or map claim
- State what is inaccurate
- We will review under moderation and claim-language rules (ADR-011)
We may correct map honesty chrome or remove UGC without admitting liability.
5. Dataset corrections
Scientific disputes about methods should prefer GitHub issues / ADRs. Factual errors in a release (wrong section labels, corrupted files) can be reported here for a patch or next-version note.
Draft only — not lawyer-approved. Related: Ofcom illegal content duties.