A plain-language explanation of what data Clean Nagaland collects, what it does not collect, where that data lives, who can see it, and how long it stays. For the full legal version, see the Privacy Policy. This page is the human-readable companion.
The short version
Clean Nagaland was designed so that reporters can speak up without being identifiable. We collect the minimum information needed to make the platform work. We delete media automatically. We never sell data. We never share data with third parties outside vetted partner organizations, and then only for drug reports where you specifically consented.
What we collect when you submit an alcohol report
- Your GPS coordinates captured live at submission time. We immediately snap these to a 50-meter grid so the stored pin does not reflect your exact standing location.
- A live photo from your camera. This is used only for moderator verification. It is never published publicly and is automatically deleted within 30 days.
- The district, category, and time pattern you selected. These are the fields that actually appear on the map after approval.
- A short description you typed. Used by moderators to evaluate the report. Not published with the pin.
- A device fingerprint. A hashed identifier derived from your browser and screen properties. Used to detect repeat abuse from the same device. It cannot be reversed to identify you.
- A timestamp. When you submitted.
We do not collect your name, address, email, or phone number on the alcohol form. There is no field for any of those.
What we collect when you submit a drug report
- Your district selection from the dropdown.
- A free-text description of the area. No GPS coordinates are ever captured on the drug form.
- The category and pattern you selected.
- Your optional description of what you saw.
- Optional uploaded media (photos or short videos). Automatically deleted within 90 days.
- Your phone number, only if you chose the phone-consent mode and typed one in. Encrypted before storage.
- A device fingerprint and timestamp, as above.
We never capture your GPS on a drug report. We never map drug reports publicly.
What we collect on every page visit
- Standard server logs. IP address, browser user agent, time of visit, page requested. Standard for any web server. These rotate out within a short window and are never cross-referenced against reports.
- Essential cookies to keep the platform working. See the Cookie Policy.
We do not run Google Analytics, Facebook Pixel, or any third-party tracking on submission forms. We do not show ads on Clean Nagaland.
What we never collect
- Your real name.
- Your home address.
- Your email address (except on the Contact page, which is separate from reporting).
- Your government ID, Aadhaar, PAN, or any other identity document.
- Your social media accounts or handles.
- Your friends, family, or contacts.
- Your browsing history outside helpnagaland.com.
- Your exact GPS on drug reports.
- Biometrics of any kind.
Where data lives
Clean Nagaland runs on servers operated by Hostinger in India. Submitted data is stored in a MySQL database on those servers. Photos and videos are stored in a protected uploads directory not accessible from the public web. Encrypted phone numbers live in a separate vault table.
Backups are taken on a regular schedule. Backups are encrypted and retained for a limited window, after which they rotate out. The same deletion schedules that apply to live data apply to backup data within one full backup cycle.
We do not move data outside India. We do not use third-party cloud analytics pipelines. We do not have a CDN that caches submitted reports.
Who can see your data
Moderators
Moderators can see all fields of a report during triage. They see the full description, the photo, the GPS coordinates on an alcohol report, the phone vault reference on a drug report. Moderator access is logged to an internal audit trail. Every moderator decision includes a timestamp and the moderator’s user ID.
Partners
Partners can see only drug reports that have been specifically forwarded to them. They see the description, the area text, the category, the pattern, any media, and the reporter’s phone only if the reporter consented and a moderator separately unlocked the vault. Partners never see alcohol reports. Partners never see other partners’ queues.
Aloto Naga
As the operational lead at Nagaland Me, Aloto Naga has access to the full moderation system including the audit log. He does not routinely read individual reports. He reviews aggregate numbers, handles appeals, and spot-checks moderator decisions. He personally visits a small number of reported locations to verify pins as “operator-verified.”
Nobody else
No outside vendors, no analytics providers, no marketing platforms, no government agencies. We do not feed data into any external system.
How phone encryption works, in plain language
When you type a phone number on the drug form and consent to contact, the number is encrypted on the server the moment it arrives. The encryption uses a passphrase set by a moderator, not a key stored in a file. This means that even someone with full access to the server’s database cannot read any phone number without that moderator’s passphrase.
To access a stored phone, a moderator must first unlock the vault with the passphrase (which expires after a short idle period), and then confirm a second consent statement that they are revealing a specific number for a specific case. Each reveal is logged.
Partners do not see decrypted phone numbers directly. They see a “phone available” indicator and must request contact through the moderator workflow.
How long data is kept
| Data type | Retention |
|---|---|
| Alcohol report photos | Deleted within 30 days of submission |
| Drug report photos and videos | Deleted within 90 days of submission |
| Rejected reports | Purged within 24 hours of rejection |
| Approved report metadata (district, category, timestamp) | Retained indefinitely for transparency and analysis |
| Individual GPS coordinates (alcohol) | Snapped to 50m grid at save; exact coordinates not retained |
| Encrypted phone numbers | Retained while case is open; deleted when case is closed or after 24 months, whichever comes first |
| Audit log entries | Retained for 24 months for accountability |
| Device fingerprints | Rotated with a daily salt; cannot be traced across days |
| Server access logs | Short rotation; standard hosting practice |
Your rights
Because we do not collect identifying information, many traditional data rights do not apply in the usual way. You cannot request “all data we have about you” because we do not know who you are. But there are things you can do:
- Withdraw a pending report. If you just submitted a report and regret it, contact us within 24 hours through the Contact page with your tracking code. Pending reports can be withdrawn before a moderator decision.
- Request takedown of a pin. If an approved pin is wrong, outdated, or putting someone at risk, use the Takedown and Appeal page.
- Request deletion of a phone number you shared. Contact us through the Contact page with your tracking code and we will delete the encrypted phone within 48 hours.
- See aggregate numbers. The Monthly Transparency page shows what we publish publicly. You can ask for clarification on any figure.
Government and legal requests
Nagaland Me may receive formal legal requests for data from courts or government agencies. When this happens:
- We evaluate whether the request is legally valid and properly scoped.
- We provide only what we actually have. We cannot provide what we do not collect.
- Where legally permitted, we inform the affected reporter before compliance.
- We do not voluntarily share data outside formal legal process.
The Source Protection Policy covers this in more detail.
What if a breach happens
If Clean Nagaland ever experiences a data breach that could affect reporters, we commit to:
- Publishing a public notice on helpnagaland.com within 72 hours of confirmation.
- Describing what was accessed and what was not.
- Describing the steps we have taken to contain and remediate.
- Describing what, if anything, affected users should do.
We would rather be transparent about a breach than let rumors fill the silence.