1. Scope
This disclosure explains the cookies, local browser storage, and service-worker cache used by INSINTA. It supplements the Privacy Policy.
INSINTA does not currently use advertising cookies or third-party behavioral analytics. The technologies below are used for authentication, security, access, preferences, realtime coordination, Progressive Web App behavior, and offline presentation.
2. Essential authentication and access cookies
Better Auth sets secure authentication/session cookies needed to sign in, keep a session, and protect authenticated requests. Production session cookies are host-scoped, HTTP-only where applicable, secure over HTTPS, and SameSite Lax. The configured session duration is 30 days unless the session is revoked, expires, or the user signs out earlier.
An essential pilot/access capability cookie may be used during controlled access flows. It is not advertising or analytics storage and is validated server-side. Security and anti-abuse controls may use short-lived request state that is not intended for cross-site tracking.
Blocking essential cookies may prevent sign-in, approved access, account security, or protected application use.
3. Preference cookies
INSINTA stores the selected interface locale in the thing-locale cookie and the selected theme in the thing-theme cookie. They are set for up to 365 days, use SameSite Lax, and may be refreshed when preferences change. They do not identify advertising interests.
4. Local storage
The selected theme may also be stored under thing-theme in local storage so the correct theme can be applied before the application hydrates and reduce visual flashing.
A bounded realtime logout signal may be stored under thing:realtime-logout-at so open tabs can react to sign-out. It contains a timestamp, not credentials or message content.
Optional browser push uses the browser's Push and Notifications APIs. Push subscription endpoint and key material are stored on the server when a user opts in; the browser and push provider may maintain related device state under their own policies.
5. Service worker and cache storage
The INSINTA service worker may cache the offline page, manifest, application icons, and static GET assets needed for Progressive Web App presentation. It does not intentionally cache authenticated API responses, non-GET requests, incident submissions, private evidence, or billing operations.
Cached static resources can persist until updated, evicted by the browser, or cleared by the user. Browser storage quotas and clearing behavior are controlled by the browser and device.
6. Managing storage
Users can sign out, revoke sessions through supported security controls, change locale/theme, disable push, clear site data, or use browser settings to block cookies. Clearing site data may sign the user out, reset preferences, remove offline assets, and disable push until re-enabled.
Essential storage is not used on the basis of advertising consent. If INSINTA later introduces non-essential analytics or marketing storage, it will update this disclosure and implement the notices or consent controls required by applicable law before use.
7. Contact
Privacy questions: [email protected]. Product support: [email protected]. Security reports: [email protected].