Cookie Policy
Version 1.3 · 2 September 2026
Which cookies and similar technologies NEMO uses, why and for how long. We only list the ones that actually exist.
On nemolink.app and app.nemolink.app
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| sb-* | User session (Supabase authentication) | Technical/necessary | Session or persistent per “remember session” |
| nemo_recuerda | Your remember-session preference on this device | Technical/preference | 400 days |
| nemo_sh | Technical session hint for routing | Technical/necessary | Session |
| nemo_lang | Chosen language (ES/EN) | Preference | Persistent |
| nemo_theme | Chosen light/dark theme | Preference | Persistent |
| nemo_demo | Dashboard demo mode | Technical | Session |
| nemo_click_id / nemo_cta_atribucion | First-party attribution of your own journey on our site | First-party measurement | Limited |
| nemo_consent | Remembers your choice in the cookie notice (1 = you accept attribution, 0 = this visit only) so we don't ask again | Strictly necessary | 180 days |
| nm_id / nm_anchor (cookie and localStorage) | Identifier of the click that brought you and of the first of your series, to attribute your signup or purchase to its origin. ONLY written if you accept in the notice; otherwise they live in the memory of that visit and nothing is stored | First-party measurement, with consent | 90 days from the first click; deleted when consent is withdrawn |
| nemo_acepta | Bridge for the legal acceptance at signup: remembers you ticked the box until the server records the acceptance when your session is created | Technical/necessary | 1 hour (deleted as soon as it is recorded) |
| nemo_legal | Mark that your account has accepted the current versions of the documents, so we don't query it on every page | Technical/necessary | Session |
On our users' websites (nemo.js script)
If a creator installs nemo.js on their website, that script handles two click identifiers on THEIR site to attribute leads and sales to their origin: nm_id (the most recent click) and nm_anchor (the first of the series, which makes it possible to tell that several visits come from the same person). Without a consent signal they are not stored: they live in the memory of that visit and are lost when it ends. Only after consent (window.nemoConsent or window.nemo.consent(true), which the creator wires to their own cookie notice) are they written as a cookie and in localStorage, expiring 90 days after the first click; after that period, or when consent is withdrawn, they are deleted and, if that person returns, a new series begins. This data is never cross-referenced between different creators' websites. In that processing NEMO acts as the creator's processor (see DPA); informing visitors and obtaining their consent is the creator's duty as controller, in accordance with the applicable rules.
Managing cookies
You can delete or block cookies from your browser; technical ones are essential for signing in. We do not use third-party advertising cookies.
Version history
- 1.3 (2026-09-02): declarada nemo_consent (la elección del aviso de cookies) y las cookies nm_id/nm_anchor en nemolink.app; los identificadores de atribución solo se guardan tras consentir — sin consentimiento viven en la memoria de la visita (nemo.js v1.4, D-081).
- 1.2 (2026-07-24): declarada nm_anchor, el ancla de la secuencia de toques, y el tope real de 90 días del almacenamiento de atribución (D-075).
- 1.1 (2026-07-22): declaradas nemo_acepta y nemo_legal, del sistema de consentimiento forense (D-LEGAL-2).
- 1.0 (2026-07-22): versión inicial, inventario real del código.