What gets stored on your device when you read this site, by whom, and how to stop it.
Last updated
The short version, as of the date at the top of this page: this site sets no advertising cookies and no analytics cookies, because it runs neither service. The only thing stored in your browser is your light/dark theme preference. The sections below describe what would be set if those services were enabled, and this page will be updated on the day that changes.
A cookie is a small text file a website asks your browser to store and hand back on later requests. It lets a site recognise a returning browser — to remember a setting, to keep a session alive, or to count you as the same visitor across pages. Related technologies do similar jobs by different means: localStorage and sessionStorage keep values in the browser without ever sending them to a server, and tracking pixels and SDK identifiers can identify a device without a cookie at all. This page covers all of them, not just cookies strictly defined.
Finvorais itself sets no cookies. There are no accounts, no sessions and no consent-state cookie, so there is nothing this site’s own code needs to store on a server round-trip.
The one thing the site does store is your light/dark theme preference, and it uses localStorage for it — a key named theme, holding light, dark or system. That is worth stating plainly because most cookie policies would list it as a “preferences cookie” and be wrong: a localStorage value is never attached to a request, so it is never transmitted to us or to anyone else. It exists only in your browser, on that device, and clearing site data removes it.
Everything else below comes from third parties, and only if the site operator has enabled that service.
| Category | Purpose | Examples | Duration |
|---|---|---|---|
| Strictly necessary | Delivering pages, load balancing, and blocking abuse. Cannot be switched off without breaking the site. | Hosting or CDN routing and security cookies set by the platform serving this site. This site’s own code sets none. | Session to a few hours, depending on the platform |
| Preferences | Remembering the light/dark theme you chose. | theme — localStorage, not a cookie. Never sent to a server. | Until you clear site data |
| Analytics | Counting visits and understanding which articles get read. Only if the operator has enabled analytics, and only in production. | Google Analytics (_ga, _ga_*), Microsoft Clarity (_clck, _clsk), or a cookieless alternative such as Plausible or Umami | Session up to 2 years, set by the provider |
| Advertising | Selecting ads, capping how often you see the same one, and measuring clicks. Only if the operator has enabled advertising. | Google AdSense and its partners (__gads, __gpi, IDE on doubleclick.net) | Typically 13 months to 2 years |
Cookie names and lifetimes are set by the third parties, not by us, and they change them without telling us. Treat the examples as indicative rather than exhaustive.
Each applies only where the operator has switched that service on.
Google and its advertising partners use cookies and similar identifiers to serve ads, including personalised ads based on your previous visits to this and other sites. Google also uses the DoubleClick cookie for frequency capping and conversion measurement. This data goes to Google under Google’s own privacy policy; we do not receive it. Ads are not served on the legal and utility pages of this site.
Sets first-party cookies to distinguish visitors and sessions, and reports aggregate traffic. IP addresses are processed by Google as part of that.
Sets cookies to link a set of page views into one session so that scroll, click and session-replay data can be assembled. Clarity attempts to mask input fields, but treat anything you type on a page as potentially recorded.
The newsletter form posts to this site’s own server rather than to a provider’s script, so it sets no third-party cookie. Where an article embeds something external — a video, a code sandbox — that provider may set its own cookies when the embed loads.
Every major browser lets you block third-party cookies outright, delete what is already stored, or clear everything for one site. Blocking third-party cookies stops essentially all of the advertising and analytics tracking described above and will not break this site.
Clearing site data also removes the theme value described above, so the site will go back to following your operating system’s light/dark setting.
A caveat worth knowing: these industry opt-outs are themselves stored in a cookie, so clearing your cookies also clears the opt-out and you have to set it again.
Most sites ignore the DNT header because nothing obliges them to honour it. This one is built not to: the analytics configuration has a respectDoNotTrack option that is enabled by default, so when your browser sends a Do Not Track signal — or Global Privacy Control, which several US state laws do treat as binding — the analytics scripts are not loaded for you at all.
That switch controls this site’s analytics. It cannot control what a third-party ad network does once its own script is running, so use the browser controls and the ad opt-outs above for advertising.
No consent banner is shown, because there is currently nothing to consent to: the site sets no non-essential cookies. Your theme preference is stored because you chose a theme, which is what makes it strictly necessary rather than optional.
If advertising or analytics are ever enabled, that changes. Readers in the EU, UK and other regions requiring prior consent must then be asked before any such script runs, and must be able to withdraw consent afterwards. A banner and the service it governs will appear here together — not one without the other.
This page changes when what the site stores changes; the “last updated” date at the top reflects that. For how the resulting data is used, see the privacy policy. Questions about anything on this page: hello@finvorais.com, or via the contact page.