Column	Type	Definition & Constraints
departmentSlug	string	Canonical slug of the government department (e.g. passport, rto, police).
departmentName	string	Official name of the department in English.
citySlug	string	Canonical slug of the city (e.g. mumbai, pune, bengaluru).
cityName	string	Display name of the city.
stateSlug	string	Canonical state slug matching ISO 3166-2:IN subdivision codes.
publishable	boolean	True if the cell satisfies privacy and aggregation gates; false if suppressed.
n	integer \| null	Total countable reports contributing to this cell. Null if suppressed.

How these numbers are made

A Google account is used only to create a one-way abuse-prevention hash. The published report is not attached to your name or account.
It publishes immediately, subject only to automated checks: a bot-detection challenge, rate limits and a daily cap per authenticated account and hashed IP, a duplicate / velocity / outlier abuse score, and canonicalisation of the department, city and role. A moderator reviews it afterwards, and can retract it. Human review happens after publication, not before.
Reports that count are grouped into a box: one department, one city, over a rolling 12-month window.
Public figures are shown only when the registry's privacy safeguards allow it.
Amounts publish exactly, as reported. Dates publish as the month range the sample spans, never a day (ADR-0005).
Every figure carries the number of reports it came from. A figure without its sample size is not a figure.

What these numbers are not

Nobody checks a report against evidence before it publishes: it goes live on submission, and there is no evidence to check against. Moderators review afterwards, on an ongoing basis, and can retract what is obviously fabricated, abusive, or personally identifying. Review happens after the figure is already public, and it does not confirm that an event happened.
This is a record of what people chose to report, not a sample of what happens. Offices people are angry about are over-represented.
An unavailable box does not mean an office is clean.
Reports are grouped by the city given, not by a specific office address.

What we never publish

The text of any individual report. There is no page for one report and there never will be.
Any name, phone number, ID number, or vehicle number typed into a structured field: these are rewritten in place before storage. The two free-text fields on the form (department and role, when 'Other' is picked) are never published anywhere, in any form, at any sample size.
The name or designation of any individual official. Role only, from a fixed list.
An exact date. Every published figure coarsens the date to the month or months the sample spans: never a day.
Any figure that cannot be shared safely.
Any box that resolves to a single office, at any sample size.
Anything about the person who reported. No name, phone, email, profile, device or raw Google subject is published. A keyed account identifier plus short-lived rate-window timestamps and counts are retained for abuse prevention, alongside the existing short-lived hashed IP.

Corrections and takedowns

If a box is wrong, or you are the office it describes, write to the grievance officer. Affected records come out of the aggregates while the complaint is open, and the next export refresh reflects it.

grievance@bribe.watch