Privacy policy
Protecting the identity of reporters is the foundation of this platform. This page explains exactly what we collect, what we do with it, and what we never do.
Last updated: 5 Oct 2026
What we collect
- The report itself: section, place, governorate, description, date, and the photos or video you upload.
- A contact detail if you choose to give one (a Telegram username). It is fully optional.
- An encrypted fingerprint of your internet address (IP). We never store the real address, only a one-way code used to prevent abuse and duplicates.
- If you choose to follow your report on Telegram: only the chat id, so we can send you updates on that report. Send /stop to the bot and it is removed.
What we do not collect
- We do not ask for your name, ID number, an account or a password.
- No trackers, no ads, no third-party analytics.
- No cookies for visitors. The only cookie on the site is for the admin team’s login.
Photos and video
Every photo is re-processed on our server and stripped of hidden data, including GPS location and device model. Video metadata is removed too. Files are never published automatically: our team picks what is shown and leaves out anything with faces or personal details.
What is published
The name and location of the place, the reviewed description of the problem, the evidence our team approved, and the report’s timeline. Nothing that identifies the reporter, and no contact details, is ever published.
Control over your report
- When you submit, you get a private link to follow the report and confirm when it is solved.
- While the report is under review, you can withdraw it from that link and it is deleted permanently, files included.
- After publication, you can request removal from the same link and our team reviews the request.
Technical notes
Fonts on this site load from Google Fonts, which means your browser connects to Google to fetch them. We keep a nightly backup of the database on the same server so reports are not lost.