1. A cookie and localStorage are not the same thing
A cookie is a small file your browser sends back to a server with every single request, which is what makes it useful for tracking. localStorage is a note your browser keeps to itself: it stays on your device, it is never attached to a request, and no server ever receives it unless a script reads it and deliberately sends it somewhere, which nothing here does.
So why does the banner say "cookie"? Because that is the word everyone knows, and because the law that matters here does not care about the difference: the EU ePrivacy rules, and Germany's TDDDG, cover any storage of or access to information on your device, cookie or not. The same consent is required either way, and it is asked for either way. This page uses the accurate word for each thing so you can check the claim yourself in your browser's developer tools.
2. What these sites store on your device
This is the complete inventory across all seven sites. Every entry is localStorage, not a cookie. None of it contains personal data: a consent record is a choice and a timestamp, and a theme key is a display preference.
| Site | Key | Type | What it holds | How long |
|---|---|---|---|---|
| vikataylor.com, steamquest.vikataylor.com | vt_consent |
localStorage | Your banner choice and when you made it: {choice:'granted'|'denied', ts:<epoch ms>} |
180 days, then you are asked again |
| claude-design-vs-lovable-vs-v0.vikataylor.com | vt_consent |
localStorage | Same: choice plus timestamp | 180 days |
| claude-design-vs-lovable-vs-v0.vikataylor.com | vt-theme |
localStorage | 'light' or 'dark': which theme you picked with the toggle |
Until you clear it |
| mood-palette-generator.vikataylor.com, moodpalette-prompts.vikataylor.com | mp_consent |
localStorage | Same: choice plus timestamp | 180 days |
| fable-vs-opus.vikataylor.com | fvo_consent |
localStorage | Same: choice plus timestamp | 180 days |
| 3d-scroll-prompts.vikataylor.com | p3d_consent |
localStorage | Same: choice plus timestamp | 180 days |
That is the entire list. There is no advertising storage, no retargeting pixel, no affiliate tracking, no A/B testing, no session recording, no heatmap, no chat widget and no CAPTCHA on any of these sites. If JavaScript is switched off in your browser, the banner never appears, nothing is stored and no analytics can load.
One thing that is not device storage but should be said anyway: these pages are served through Cloudflare, which receives your IP address and request metadata and keeps them in server logs. That happens before and regardless of consent, because it is how the connection is made at all. It is a server-side log, not something written to your device. The Privacy Policy covers it.
3. What can be set once you agree
Two third parties can place storage in your browser, and only after a deliberate act by you. We describe them by purpose rather than listing exact names and lifetimes, because they are set by Google, not by us: we cannot read them, and we will not publish names and expiry dates we cannot verify and that Google can change at any time.
| Set by | Only after | Purpose | What we can honestly say |
|---|---|---|---|
| Google Analytics 4 (Google LLC) | You press Accept on the banner | Counting visits: telling one browser apart from another and one session from another, so page views and traffic sources can be measured without counting the same visit repeatedly | These are Google's own cookies, written by Google's script. Before you press Accept the
script is not on the page and no request reaches googletagmanager.com or
google-analytics.com. Our measurement ID is G-VFPV5MZNL2, IP anonymisation is
on, and Google Consent Mode v2 starts with every storage type denied. Names and lifetimes
are Google's to set and change:
Google's privacy policy. |
| YouTube (Google LLC) | You press play on an embedded video | Playing the video, remembering playback settings, and measuring viewing on Google's side | Three sites embed a video: the Claude Design comparison, Fable vs Opus and 3D Scroll Prompts. Until you press play there is no player on the page, only a local thumbnail, and nothing is requested from any Google host. The player then loads from youtube-nocookie.com, which limits storage until playback begins, but once it begins YouTube receives your IP address and may store data in your browser under its own rules. Every one of those pages also offers a plain link to youtube.com instead, which keeps the embed off the page entirely. |
Note the asymmetry, because it is deliberate: pressing Accept does not load the video, and pressing play does not turn on analytics. They are two separate decisions and you can make them differently.
4. Giving, refusing and withdrawing consent
A banner appears shortly after the page has loaded, on your first visit to each site. It has two buttons and neither is pre-selected:
- Accept loads Google Analytics and lets it set its storage.
- Decline loads nothing. The Google script is never fetched at all, so there is nothing to switch off afterwards.
Ignoring the banner has the same practical effect as declining: nothing loads until you press Accept. Your answer is written to localStorage under the key listed in section 2 so you are not asked on every page, and it is re-asked after 180 days.
Changing your mind is as easy as the first choice. Every page on every one of these sites has a Cookie settings button in its footer, including this one. It reopens the same banner with the same two buttons, and the choice you make replaces the stored one. Withdrawing is exactly as easy as giving consent, which is what the GDPR requires and not merely what it recommends.
One honest limit: switching from Accept to Decline stops anything further from loading, but it does not reach into your browser and delete cookies Google has already set. Those are Google's, in your browser, and only you can clear them. Section 6 says how.
5. Your choice is stored per site, not across the network
Browsers keep localStorage separately for every origin, and these seven sites are seven origins. So the record of your choice lives on the subdomain where you made it, and it is not shared with the others. In practice: if you decline on vikataylor.com and then open 3d-scroll-prompts.vikataylor.com, the banner asks you again there.
We could have worked around that with a shared cookie on the parent domain. We did not, because that would mean setting a real cookie across all seven sites in order to record that you did not want tracking, and reading a per-visit choice on domains you may never open. Being asked twice is the price of not doing that. It is a per-site choice and always was, so this page says so rather than implying one click covers everything.
6. Clearing it yourself in the browser
Everything described here can be removed by you at any time, without asking us, and nothing here can stop you.
- For one site: open the padlock or the icon next to the address bar while you are on the page, and use the option to clear cookies and site data for that site. This is the quickest way, and it removes both our localStorage entry and any Google cookies for that site.
- For everything: in your browser's settings, under privacy, there is a section for cookies and site data with a clear-all option and per-site controls. The exact wording differs between Chrome, Safari, Firefox and Edge, and it moves between versions, so use the search box in settings for "cookies" rather than trusting a menu path printed here.
- Block it in advance: browsers can refuse third-party cookies outright, and a private or incognito window discards all of it when you close the window.
What clearing does on the next visit: the consent record is gone, so the banner will ask you again. On the Claude Design comparison, the theme you picked goes with it and the page returns to its default. Nothing else is lost, because nothing else is stored.
7. What you give up by declining: nothing
Declining costs you no functionality whatsoever. Every page reads the same, every prompt is fully visible and copyable, Moodpalette generates palettes exactly as before, because its colour engine is rule-based and runs entirely in your browser with no server call. No content is behind the banner, no feature is degraded, and there is no second banner nagging you later in the session.
The one difference is that visits are not counted in analytics, which affects only what we can see about traffic, not what you can do. Videos still work too: press play, or use the plain YouTube link if you would rather not load an embed at all.
8. Changes, and who to ask
If a site starts using something that stores data on your device, this page and the tables above are updated before it ships, and the date at the top changes. There is no mailing list to announce it, so this page is the record.
Questions about anything on this page, including a request to see exactly what a site writes to your browser: vika.taylor.one@gmail.com. That address is the only channel that exists. The wider picture, including legal bases, transfers outside the EEA and your rights, is in the Privacy Policy; the terms on which all this is published are in the Terms of Use.