SOURCES AND LIMITSEvery result shows where it came from and what it cannot tell you.Data & method
Back to resourcesPrivacy and participation

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
Check reporting availability
Share or print this source-linked guide without sending personal information.
Share this guide on WhatsApp ↗Opens WhatsApp with the public title and link. Choose the recipient and send it there.
Text size
Listen to this 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.

1

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
2

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
3

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
MY AAMEGH / THIS BROWSER ONLY

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.

Browser storage is unavailable.

No task was stored. Every public feature remains usable.

Private progress, not a trust score.Completion stays on this device and never affects jobs, support, contribution review or public visibility.

Understand this page

Separate public facts from private circumstances.

A useful public observation describes a checkable condition within a broad area. It should not ask readers to identify a person or infer what happened in a private incident.

Keep the wording factual

Describe the condition and what is unknown. For example, a source may show a transport stop without establishing current service frequency. Do not turn missing information into a claim that a facility does not exist.

Use current channels for a personal need

Aamegh reporting is closed. If you need support or an official complaint route, choose that pathway directly rather than writing a narrative in a place search.

Questions about this page

Can I upload a photograph or incident description here?

This guide does not accept evidence or create a report. Keep identifying or private material out of public fields.