Cookies and Browser Storage
Last updated: 2 November 2026
1. Analytics on customer websites
The analytics server processes IP addresses and User-Agent information for request handling, geographic enrichment, and approximate weekly network/browser groups. Raw IP is not a field in the analytics event table, but operational access and security logs may retain it. These network groups are not verified people.
The current browser SDK first requests the site collection and privacy policy. If consent is required, it waits for the customer’s consent flow to grant collection; denying or withdrawing consent clears its session context and stops further tracking writes. Once collection is allowed, it uses a random per-tab session nonce, with a 30-minute inactivity window, and sessionStorage for session and campaign context. Storage restrictions or older tags can reduce continuity. Optional site-scoped customer digests can link declared customer activity across sessions; a 64-character hash is pseudonymous data and can remain personal data.
New websites default to minimal mode, which drops optional declared customer and advertising identifiers, diagnostic error details and precise city/region. Existing websites retain a labelled legacy mode until an admin reviews it; identified mode requires an explicit processing-instructions acknowledgement. Server controls strip URL queries/fragments, reduce referrers to origins, bound text and redact common sensitive patterns, but cannot detect every form of personal information. Paths, UTM values, referrers, click destinations, custom-event fields and error text can still contain customer information if your application puts it there. Keep names, emails, payment credentials, account tokens and sensitive information out of those fields. Hashing identifiers does not remove the need to control collection and access.
The current analytics tag uses sessionStorage rather than an analytics cookie. Session and campaign context are still identifiers or stored data; “cookieless” does not mean anonymous or storage-free. Browser restrictions may shorten or prevent continuity.
2. NeuTarget account and sign-in storage
| Storage | Purpose and lifetime |
|---|---|
nt_token cookie | Dashboard access token. The browser cookie is set for up to one day; token expiry, sign-out and server revocation can end access earlier. |
| SSO state and handoff cookies | The API uses HttpOnly cookies to bind sign-in to the initiating browser. Current state lifetime is ten minutes; the one-use handoff lifetime is sixty seconds. They are cleared or expire as the flow completes. |
| Session storage | Pending MFA and explicit SSO-link approval use isolated session state. The analytics SDK uses per-tab session context with a thirty-minute inactivity window. |
| Local storage | Dashboard preferences and localization can persist until cleared. A private erasure receipt can remain locally so a closed account can check progress without signing in; the user can download or remove it. |
3. Connected services
Identity, checkout, embedded security and connected-platform services can have their own cookies, storage and processing. Review the providers enabled for your deployment; this page does not promise that every integration is cookie-free.
4. Choices and notices
Customers choose the purposes, data fields, lawful basis and visitor notices for their deployment. Where consent is required, control loading of the analytics script and enabled integrations through your consent flow. Using no analytics cookies does not by itself establish an exemption for browser storage, identifiers or subsequent personal-data processing.
Applicable requirements depend on the audience, jurisdiction and configuration. The European Commission explains personal and pseudonymised data, and Your Europe describes online privacy and cookie requirements. India’s 2025 DPDP Rules notification provides phased commencement; publication does not mean every provision took effect at once. This product does not assign a lawful basis or certify a customer’s compliance.
Browser settings can remove or block cookies and storage, which can sign you out or reduce analytics continuity. Customers should load the tag and integrations only when their chosen collection conditions are satisfied. A Do Not Track setting is honored by the current tag, but that alone is not a complete consent-management system.
5. Contact and updates
Questions about configured storage or providers can be sent to the existing contact, support@neutarget.com. See the Privacy Policy for retention and erasure. Changes to tag versions or enabled integrations can change the storage record.
