Cookies and storage in your browser
Last updated: August 4, 2026.
What Wurz leaves stored in your browser, what each item is for, and how to delete it. The list came from reading the code, not from a template.
What’s there, key by key
Wurz stores two kinds of things in your browser. Local storage holds preferences of yours that never leave your machine: they don’t travel to any server. Cookies are the ones that do travel with every request, and here they exist only to keep your session signed in.
| Key | Type | Purpose | How long |
|---|---|---|---|
wurz-settings | Local storage | Your in-app preferences: light or dark theme, how much detail the canvas shows, and whether the chat can suggest filters. It's stored here so the screen doesn't flicker while the server responds. | Until you delete it |
wurz-theme | Local storage | The light or dark theme you chose on this public site, without signing in. | Until you delete it |
wurz-lang | Cookie | The language you chose with this site's selector, so we greet you in it next time. If you never touch it, the site is served according to your browser's language. | One year |
wurz:hideMergeWarning | Local storage | That you checked the box to stop showing the warning that appears when merging two nodes. | Until you delete it |
wurz:upload-history-cleared-at | Local storage | From what point in time you want to see your upload history. Hiding the history is a display preference: it deletes no documents. | Until you delete it |
wurz:invitation-handoff | Local storage | The invitation to a workspace, held while you create your account, so that when you finish signing up you land in the workspace you were invited to and not an empty one. | Expires on its own within minutes |
__session | Cookie | Your signed-in session, managed by our identity provider. It's what keeps you from typing your password on every screen. Without it there's no way to sign in. | While your session stays active |
__client_uat | Cookie | A timestamp that tells the application whether your session is still alive or needs revalidating. | While your session stays active |
__clerk_handshake | Cookie | A very short-lived cookie used during the sign-in handshake itself. | Seconds |
What’s not there
Wurz does not use advertising cookies, third-party analytics tools, social media pixels, or anything that follows you from one site to another. We also don’t sell or share browsing data with anyone for commercial purposes.
That’s why this site doesn’t greet you with a cookie banner. Mexico doesn’t require one: what the law asks is that you be told what is stored and be able to disable it, which is exactly what this page does. A banner over a list with no trackers would only cost you a click in exchange for nothing.
How to delete it
Everything in the table is under your control from your browser. In Chrome, Edge, Firefox, or Safari it’s in the privacy settings, under site data: you can delete this site’s data specifically or block cookies entirely.
Mind the consequence: session cookies are what keep you signed in. If you block them, Wurz will ask you to sign in over and over, or you won’t be able to get in at all. Deleting local storage, on the other hand, only resets your preferences to their defaults — you don’t lose a single document.
Deleting things from the browser deletes nothing from your account. That’s what your data rights (ARCO) are for, or write to us at privacidad@wurz.app.
Pending definition
Everything above describes what Wurz does today. What follows hasn't been decided yet, and that's why it doesn't appear above: we'd rather show you the gap than plug it with something we couldn't honor.
- If at some point a site analytics tool is added, this page and the privacy notice have to say so before it’s switched on, and it will have to be decided whether a consent mechanism is then warranted.