Privacy Policy
What TriNetra processes, why it processes it, and the controls that hold every lookup accountable.
1. Who is responsible for this data
TriNetra is operated as the data fiduciary for the personal data described below. Deployment-specific contact details for the operating entity and grievance officer are set out in Section 8.
2. What personal data TriNetra processes
- Vehicle registration marks (number plates) captured by ANPR cameras in the deployment area, together with the capture timestamp, camera identifier and location.
- Derived vehicle identity data — the visual fingerprint used to link sightings of the same vehicle across cameras, and the reconstructed trajectory between sightings.
- Operator identity data — the username, role and session details of any person signed in to the console, recorded against every action they take.
TriNetra does not process biometric data on drivers or occupants, and does not attempt facial recognition. A number plate is treated as personal data because it is capable of identifying the registered owner of a vehicle.
3. Why this data is processed
Personal data is processed only for stated law-enforcement and traffic-management purposes: locating a specific vehicle in connection with an investigation, monitoring live traffic and camera health, forecasting congestion, and simulating the effect of road closures for planning. There is no purpose in TriNetra that queries vehicle data without a stated reason attached to that specific request.
4. The purpose-binding and audit controls (Kavach)
Every request that touches vehicle data is required to carry a purpose and a case identifier. A request missing either is refused before it reaches the database — there is no anonymous lookup path in TriNetra. Each signed-in session is also bound to one of five enforced roles (patrol, investigator, analyst, auditor, super_admin), and access to each view is checked on the server on every request, not only hidden in the interface.
Every query is written to an append-only audit ledger. Each entry is chained to the one before it by a cryptographic hash of the actor, role, action, purpose, case ID and target, so that altering or deleting a past entry breaks the chain from that point forward and is detectable by anyone who verifies it. This ledger is readable only by the auditor and super_admin roles.
5. Data retention
Raw camera captures and derived trajectory data are retained for the period required by the operating agency's investigation and evidentiary needs, after which they are deleted. Audit ledger entries are retained for the full retention period regardless of the underlying data's status, since the ledger's purpose is to account for historical access even after the data it describes has been removed.
6. Who this data is shared with
Personal data processed by TriNetra is accessible only to authorised personnel of the operating law-enforcement or traffic-management agency, through the role-gated console described above. It is not sold, and it is not shared with any third party for advertising, marketing or unrelated commercial purposes.
7. Your rights as a data principal
Under the Digital Personal Data Protection Act, 2023, an individual whose vehicle registration data has been processed by TriNetra may request confirmation of what data concerning their vehicle is held, correction of inaccurate data, and erasure of data no longer required for the stated purpose, subject to the operating agency's legal obligations to retain records connected to an active investigation. Requests can be made through the grievance contact in Section 8.
8. Grievance officer and contact
Deployment contact: [Grievance Officer name] · [grievance email] · [operating agency, registered address]. This section is completed by the operating agency at deployment and is not filled in on the reference build.
9. Changes to this policy
This policy may be updated to reflect changes to TriNetra or to applicable law. The effective date at the top of this page reflects the most recent revision.