---
sidebar_position: 3
tags: [security, privacy]
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lium.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cookies, Analytics and Your Consent

lium.io sets a strictly necessary cookie that keeps you signed in and Stripe's fraud-prevention cookies when its payment script loads; the Provider Portal keeps your sign-in in browser storage and sets one preference cookie (`show-cluster-status`). Both sites set Google Analytics 4 measurement cookies, which also feed Google Ads conversion reporting. This page says what is stored, when, and how to change your choice. The binding text is the [Privacy Policy](https://lium.io/privacy), section 5.

## What the consent bar does

If you visit from the European Economic Area, the United Kingdom or Switzerland, a panel appears at the bottom of the page before any analytics or advertising cookie is set — nothing is dimmed, nothing blocks the page. It says that necessary cookies (sign-in, Stripe's fraud prevention) run the service regardless, that analytics and advertising cookies are set only with your permission, and links the [Privacy Policy](https://lium.io/privacy) as **Details**. The analytics and advertising switches are visible immediately, followed by three actions:

| choice | effect |
|---|---|
| **Accept optional** | Google Analytics and Google Ads measurement cookies are allowed. Google is told it may store them and use the click data to attribute a sign-up to an advertisement (`ad_storage`, `ad_user_data`). It is not told it may personalize ads: we do not use personalized advertising, and `ad_personalization` stays denied whatever you choose. |
| **Reject optional** | No analytics or advertising cookie is set. Google receives only cookieless pings that carry no identifier stored on your device. Necessary cookies are unaffected. |
| **Save choices** | Applies the *Analytics* and *Advertising* switches. They start from your current state: both off when the panel appears on its own in the regions above, otherwise your stored or default choice. Analytics covers Google Analytics cookies for site usage; Advertising covers Google Ads measurement cookies and click data sent to Google, without personalized ads. |

Your choice is remembered for up to 180 days in a first-party cookie named `lium_consent`, so you are not asked again — a Reject is remembered as much as an Accept. Safari caps cookies set by page scripts at seven days, so Safari asks again after a week. Outside those regions no panel is shown and the analytics cookies are set unless you opt out.

Where you are is decided from the country our edge network reports for your connection; when that is not available, from your browser's time zone (only the zones of those countries count), and when the time zone says nothing (UTC), from your browser's language region. When none of these places you in the EEA, the UK or Switzerland, no panel is shown.

## Changing or withdrawing your choice

- Click **Cookie settings** in the footer of any page, next to the Terms of Service and Privacy Policy links — on lium.io in the sidebar's footer; on the Provider Portal in the sidebar's footer, under the sign-in forms and in the landing page's footer — or open [lium.io/#cookie-settings](https://lium.io/#cookie-settings). The panel opens with your current choice; this works everywhere, including where the panel is not shown automatically. Withdrawing stops new analytics and advertising cookies; a `_ga` cookie already on your device stays until it expires or you delete it.
- Block or delete cookies in your browser, or install the [Google Analytics opt-out add-on](https://tools.google.com/dlpage/gaoptout).

Declining analytics or advertising cookies does not change anything about renting pods, connecting nodes or your account.

## For the technically curious

The pages implement [Google Consent Mode v2](https://support.google.com/google-ads/answer/10000067): an inline script in the page head sets the four consent signals (`ad_storage`, `analytics_storage`, `ad_user_data`, `ad_personalization`) before the Google tag loads. When your browser's time zone or language region places you in the EEA, the UK or Switzerland, the script sets them to *denied* outright; otherwise it sets them to *denied* for those regions as Google resolves them from your IP address and to *granted* elsewhere. So a visitor on a VPN or travelling is denied when either the IP or the browser says one of those regions. Your choice in the panel updates three of those signals: *Analytics* sets `analytics_storage`, *Advertising* sets `ad_storage` and `ad_user_data`; `ad_personalization` is denied in every case, because we describe and use the advertising cookies for measurement only. Whether the panel is shown is decided from the `CloudFront-Viewer-Country` header first, then the same time zone and locale signals, as described above. Google states that [Google Analytics does not log or store IP addresses from EU, Swiss or UK users](https://support.google.com/analytics/answer/12017362).