Cookies & local storage
The short version
- wanova.io sets no cookies at all. Not first-party, not third-party, not "essential ones we'd rather not mention".
- No analytics, no advertising pixels, no trackers. There is nothing here to consent to, which is why there is no banner.
- We use a handful of localStorage entries so the site remembers your theme and keeps you signed in. They stay in your browser. The complete list is below.
1. Cookies we set
None. The site is static HTML, CSS and a little vanilla JavaScript; there is no session cookie, because sign-in uses a token held in localStorage and sent in an Authorization header instead.
2. What we do store in your browser
All of it is localStorage on wanova.io — readable only by this site, never sent anywhere except where noted.
| Key | What it's for | Sent to us? | Lifetime |
|---|---|---|---|
wanova.theme | Remembers whether you chose light or dark, so the page doesn't flash the wrong one | No | Until you clear it |
wanova.web.session | Your sign-in token. Sent with API calls to prove who you are — this is what keeps you signed in | Yes, to api.wanova.io | Expires after 30 days; removed when you sign out |
wanova.lang | Remembers which language you chose, so you land on it next time instead of being re-guessed from your browser | No | Until you clear it |
wanova.checkout_intent | Remembers which plan you clicked before signing up, so checkout resumes afterwards | No | Cleared once checkout resumes |
wanova.api_base, wanova.google_client_id | Developer overrides for local testing. Only exist if you set them yourself | No | Until you clear them |
Under the ePrivacy rules these are strictly necessary or explicitly requested by you — a sign-in token for a service you asked to sign in to, and a preference you set yourself. That is the exemption in Art. 5(3), and it is the honest reason there is no banner: not a loophole, just an absence of tracking.
3. Third parties, and only when you invoke them
| Who | When | What they may store |
|---|---|---|
| Google Identity Services | Only on the sign-in and register pages, and only if you use "Sign in with Google". The library isn't even loaded unless that feature is configured. | Google's own cookies on Google's domains, under Google's policies. If you'd rather not, sign in with a password or with an emailed code instead — neither loads anything from Google. |
| Our payment provider | Only when you go to checkout or the billing portal — those pages are on their domain, not ours. | Whatever their own cookie policy says; card data never touches our site. See sub-processors. |
There are no embedded videos, no web fonts loaded from a CDN, no chat widgets and no social buttons on this site — the usual sources of third-party cookies simply aren't here.
4. The extension
The Wanova extension stores its data in your browser too — templates, customer notes, schedules, caches and settings. That isn't cookies and none of it is sent to us; it's described in Privacy §6.
It lives in two places, and they are cleared by two different actions — worth knowing if you want all of it gone:
- The extension's own storage — your settings, notes, templates, schedules and rules. Only removing the extension clears this. Clearing site data in your browser does not touch it.
- A local database on
web.whatsapp.com— attachment files and the translation cache, which are too large for the first. This one goes when you clear site data forweb.whatsapp.com, and it survives removing the extension.
5. Clearing it
Sign out to drop the session token, or clear site data for wanova.io in your browser's settings to remove everything in the table above. Nothing breaks — you'll just be signed out and back on the system theme.
6. If this ever changes
If we ever add anything that isn't strictly necessary — analytics of any kind included — we will ask for your consent first, with a real reject option, and this page will say so before it happens.
Questions: privacy@wanova.io.