Share useful context without exposing a person
A privacy-first way to separate observable public facts from sensitive incident information.
- About
- Aamegh guide with named source links
- Updated
- 13 September 2026
- Reading time
- 4 minute guide
Read-aloud is not supported in this browser. You can use your device’s reading or screen-reader tools.
Reading choices reset when you leave. Read-aloud uses your browser’s speech service; some voices use an online service. Only the published guide text is read.
Describe the public condition
A useful broad-area audit describes a condition that another reviewer can check, such as whether lighting or an attended public facility was observed.
- Use a broad locality or approved grid
- Choose a structured category
- Record when the condition was observed
Leave identifying detail out
A public observation should never identify a survivor, witness or private individual, and should not reveal an exact incident location.
- No names or contact details
- No faces, vehicle numbers or private addresses
- No personal incident narrative in a public field
Expect moderation before publication
A submission is not a public fact. Source, consent, privacy and relevance checks must happen first, and a report about harm must never earn a token.
- Public submissions are not open yet
- Allow correction and revocation
- Publish only broad, non-identifying summaries
Keep this useful next step.
Keep predefined Aamegh tasks for up to 30 days. No account, place, search, report, points or public ranking is created.
No task was stored. Every public feature remains usable.