Cookie Policy
Nota para lectoras y lectores en español: esta Política de cookies se publica únicamente en inglés y el texto en inglés es el que rige; la Política de privacidad explica por qué. En resumen: hoy el servidor no coloca ninguna cookie, y lo único que se guarda en tu navegador es tu elección sobre cookies, el tema visual y el idioma — las tres cosas porque tú las pediste. Si algo no queda claro, escríbenos a info@empoweragile.com.
Last updated 8 August 2026. Applies to the website narrativetrace.ai.
This page lists everything narrativetrace.ai puts in your browser. It covers
cookies and localStorage alike — you care what is stored on
your device, not which browser API stores it, and listing only cookies would be a
technicality standing in for an answer.
As of the date above, the server sets no cookies at all: a request to this
site returns zero Set-Cookie headers. Everything in the table below is written
by the page itself, in your browser, as a direct result of something you did.
1. What is stored right now
| Name | Kind | Provider | Purpose | Lifetime |
|---|---|---|---|---|
nt_consent |
Cookie | This site (first-party) | Remembers the choice you made in the cookie settings dialog, so you are not asked again on every page. Without it there is no way to honour a "no". | 182 days |
theme |
localStorage |
This site (first-party) | Remembers whether you chose the light or dark appearance. Written only when you click the theme toggle. | Until you clear your browser storage |
lang |
localStorage |
This site (first-party) | Remembers whether you chose English or Spanish, so the site stops guessing from
your browser settings on later visits. Written only when you click the language
switcher, or open a ?lang= link — never merely because we
detected a language. |
Until you clear your browser storage |
All three are strictly necessary in the legal sense: each exists solely to deliver something you explicitly asked for. None is sent to us, none is readable by anyone else, and none can identify you.
The language entry deserves one clarification, because detection and storage are separate
things. On a first visit we read the language list your browser already sends with every
request, in order to decide which version to show you. That reading is momentary and
stores nothing. The lang entry is written only when you make an
actual choice — the switcher in the header, or a ?lang= link. Arriving
somewhere is not the same as choosing to be there.
2. Measurement that stores nothing
Cloudflare Web Analytics counts page views for us. It appears in no row
above because it belongs in none: it writes no cookie, no localStorage entry,
and no identifier of any kind to your device, and it does not fingerprint your browser.
That is also why it is not one of the switches in the cookie settings dialog. A switch would suggest we are asking permission to store something, and we are not storing anything. It is described instead in the Privacy Policy, section 2.2, along with your right to object to it.
3. Categories you can control
The cookie settings dialog offers three categories. Two of them are, today, empty — no tool is wired to them. They exist so that the day we introduce one, you have already been asked, and the switch you set is already being honoured.
| Category | Status today | What it would cover | Cookies it would set |
|---|---|---|---|
| Strictly necessary | Active, always on | The two rows in section 1. | nt_consent, plus the theme value in localStorage |
| Audience measurement | Empty — nothing is loaded | Aggregate statistics about which pages get read, to decide which documentation to improve. | _ga, _gid — none of which currently exist |
| Session replay | Empty — nothing is loaded | Recording how an individual visitor moves through a page: pointer, clicks, scrolling. | _clck, _clsk, CLID — none of which currently exist |
Session replay is a separate category from measurement on purpose. Watching how one person moves through a page is a materially more invasive thing than counting how many people read it, and bundling the two would mean a single "yes" bought both.
4. Whether you are asked at all depends on where you are
We apply the standard that gives you the most protection where you are:
- Outside the United States — including the EU, the EEA and the UK — the optional categories are off until you switch them on. You are asked before anything optional runs.
- In the United States — the optional categories follow the opt-out model those laws use, and the "Cookie settings" link in the footer turns them off. If your browser sends a Global Privacy Control signal we treat that as the opt-out immediately, without you having to click anything.
- If we cannot tell — because the lookup failed, timed out, or returned a country we do not recognise — you get the stricter treatment, not the looser one.
Working out which case applies uses a request to our own host for a country code. It is a first-party request and reveals nothing to anyone new. We deliberately do not use a third-party geolocation service: asking an outside company where you are, in order to decide whether we are allowed to contact outside companies, would defeat the point.
5. Changing your mind
The Cookie settings link in the footer of every page reopens the dialog. Withdrawing is one click from anywhere on the site, and the control looks exactly like the links next to it — no dark pattern, no buried switch, no "are you sure".
Turning off a category also clears the cookies it set. Turning off session replay additionally reloads the page: a replay tool told to stop will stop setting cookies but carries on recording until the page it is running in goes away, so the reload is what actually ends the recording.
You can also block or delete anything here from your browser's own settings. The site works with all of it blocked — you will simply be asked about your theme choice again on each visit.
6. The library that shows the dialog
The consent dialog is drawn by an open-source library (vanilla-cookieconsent, MIT licensed) that we serve from this site, not from a content delivery network. Loading a consent banner from a third-party CDN would disclose your IP address to that third party before you had agreed to anything — a consent gate that violates itself in the act of asking. The same applies to the documentation viewer's syntax highlighting, which is likewise served from here rather than from a CDN.