Cookie Policy
TriNetra sets no cookies. Here is exactly what it stores in your browser instead, and why.
No cookies
The TriNetra console does not set, read or rely on HTTP cookies. Signing in does not create a cookie, and nothing on this site or in the console tracks you across other sites.
What the console stores instead
A signed-in console session is held entirely in your browser's local storage, scoped to this site only. Local storage never leaves your device unless the console reads it to attach it to a request you make. The keys used are:
trinetra_token— the session's authentication token, sent with each request to prove you are signed in.trinetra_role— the enforced role for the session (patrol, investigator, analyst, auditor or super_admin).trinetra_username— the signed-in username, shown in the console and recorded in the audit ledger.trinetra_purpose— the stated purpose attached to the session's queries, required by the accountability controls described in the privacy policy.trinetra_case_id— the case identifier attached to the session's queries, for the same reason.
All five are cleared when you sign out, or by clearing this site's data in your browser. None of them is set on the public pages you're reading now — only on the console itself, after sign-in.
Third-party requests
The console (not this page) loads two typefaces from Google Fonts on sign-in, which involves a request to Google's font servers. The static pages you're reading now — including this one — make no third-party requests at all; every font they use is served from this site.
How to clear stored data
Sign out of the console, or use your browser's "clear site data" option for trinetraa.live to remove everything listed above.