Nerja Tag (website)
Privacy & consent
Exactly what the Nerja Tag reads, what it never reads, and how consent levels change that.
Consent levels#
| none | identity | full | |
|---|---|---|---|
| Page views, clicks, cart and checkout events | |||
| Field type and length | |||
| Email, phone, first and last name values | |||
| Address values | |||
| Passwords, card, CVV, SSN, bank, PIN, one-time codes |
identity is the default. The last row is never collected at any level.
| Level | Form values sent | Use when |
|---|---|---|
none | Only the field type and length — values are redacted | Visitor has declined tracking beyond basics |
identity (default) | Email, phone, first and last name. Address and everything else redacted | Normal operation: leads and identity merge work |
full | All non-sensitive values, including address fields | After an explicit opt-in on your consent banner |
Never collected#
- Password, hidden and one-time-code fields
- Card number, expiry, CVV/CVC, cardholder name
- SSN / tax id, bank account, routing, PIN, 2FA codes
This is enforced in the tag itself, before any data leaves the page, regardless of consent level.
What is stored in the browser#
| Item | Where | Purpose |
|---|---|---|
_cid | First-party cookie | Browser identity |
anon_id | localStorage | Anonymous id backup |
nerja.* keys | localStorage | Cart model, funnel stage, outbox of unsent events |
Your responsibilities#
- Show a consent banner where the law requires it and call
setConsentwith the visitor's choice. - Honour deletion requests — Nerja provides a data-deletion flow for end customers.
- Keep your privacy policy aligned with the data above.
Privacy
Contact details are never sent to AI models — only aggregate audience summaries and product context.
Prefer to talk it through? Book a 30-minute call with the Nerja team.
Something unclear or missing? Email support@nerja.ai and we will improve this page.