Cookie Notice
Last updated: 2026-08-28.
Navigation
| Part | Clauses | Purpose |
|---|---|---|
| A. Technology inventory | 1–4 | define covered technologies and disclose essential, local, and analytics uses |
| B. User choice and lifecycle | 5–7 | explain consent, controls, notice versioning, and change handling |
Part A — Technology inventory
1. Scope
This Cookie Notice explains how Loglune uses cookies, local storage, and similar technologies that store or access information on a browser or device. It should be read with the Privacy Notice. “First party” means set or controlled through a Loglune domain. “Third party” means set or controlled by another provider. Classification does not determine whether consent is required; purpose and applicable law control.
2. Strictly necessary technologies
| Technology | Party / provider | Purpose and data accessed | Status | Duration |
|---|---|---|---|---|
Cloudflare Access session cookie (CF_Authorization) used by the production project |
first party; Cloudflare and Loglune | maintain and verify the signed-in console session at the edge; signed Access identity token and authentication state | strictly necessary | the session duration configured by the production Cloudflare Access application |
| LOGLUNE_LOCALE | first party; Loglune | remember the selected language; locale preference | strictly necessary preference | one year |
| Cloudflare Access sign-in flow state, if the deployment creates it | first party; Cloudflare | carry the authentication redirect and step-up state during sign-in through the identity provider; short-lived authentication-flow state | requested sign-in feature | the sign-in flow duration configured by the production Cloudflare Access application |
| Stripe technologies identified by the hosted checkout | third party; Stripe | checkout, payment security, fraud prevention, and transaction management; device, session, and transaction signals | requested checkout and security | durations stated in the Stripe cookie notice |
These technologies are necessary to provide a feature you request, secure the Service, or complete checkout. Disabling them may prevent sign-in, language selection, or payment. Loglune relies on an exemption from prior consent only where a technology is strictly necessary to transmit a communication, provide a service or feature expressly requested by the user, authenticate or secure the session, prevent fraud, remember a choice needed for that request, or satisfy another applicable statutory exception. Convenience to Loglune, analytics, general improvement, or advertising is not by itself treated as strictly necessary. The table must be verified against production behavior before release and after material deployment changes. A provider’s general cookie list does not replace identification of the technologies actually used on Loglune.
3. Local storage
Loglune may store the following on your device:
- theme preference;
- language preference;
- cookie-consent choice;
- onboarding or welcome-screen state.
Loglune does not store your flag definitions, configuration, targeting rules, or their contents in browser local storage; the flag and configuration data you create and manage in Loglune is held server-side as private objects and is not persisted in the browser. Clearing browser data can permanently remove preferences, consent records, and onboarding state held on the device. Loglune uses local storage and equivalent browser storage only for the interface preferences and consent state described in this Notice and the Privacy Notice. Access tokens, flag or configuration contents, and credentials must not be placed in persistent browser storage.
4. Analytics
Loglune uses Google Analytics 4 through Cloudflare Zaraz to measure product and website use. Zaraz is the sole analytics-tag delivery runtime on Loglune; Loglune does not load Google Analytics through a direct Google tag, Google Tag Manager, Partytown, or Plausible. Zaraz assigns Google Analytics to the optional Analytics purpose and withholds it until analytics consent. Its data processing is described in the Privacy Notice.
Zaraz stores the Analytics-purpose choice in the first-party zaraz-consent cookie until that cookie expires or is cleared. After consent, Google Analytics may set first-party _ga and _ga_<measurement-id> cookies for up to two years to distinguish pseudonymous users and sessions, and may receive page URL and title, referral and campaign data, page and feature events, web-vital and long-task measurements, coarse location, and basic browser or device data. Google Analytics user-level and event-level data is configured for two-month retention without resetting the user-data expiry on new activity.
Loglune does not send flag or configuration data, account email, User-ID, or user-provided data to Google Analytics. Google Signals, ads personalization, advertising cookies or tags, pixels, fingerprinting, cross-site tracking, and measurement of third-party advertising campaigns are disabled or not used. Introducing advertising or cross-service tracking requires updates to the Privacy Notice, this Cookie Notice, consent controls, provider list, and any applicable opt-out mechanisms before deployment.
Part B — User choice and lifecycle
5. Consent
Where EU, EEA, UK, or other law requires consent, Loglune will:
- withhold non-essential technologies until consent;
- provide equally accessible accept and reject choices;
- avoid pre-selected consent;
- record the choice; and
- allow withdrawal as easily as consent.
Strictly necessary technologies remain available without optional consent. If Loglune introduces a new non-essential technology or materially changes a consented purpose, Loglune obtains fresh consent before using it for that new technology or purpose. Consent and rejection records are retained only for the period needed to demonstrate and respect the current choice. Consent must be specific by purpose, informed, freely given, and indicated by an unambiguous affirmative action. Continuing to browse, silence, inactivity, a preselected control, or accepting general Terms is not treated as consent where affirmative consent is required. Loglune does not make the core Service conditional on consenting to an unnecessary technology. Declining a genuinely optional feature may prevent only that feature or the associated optional measurement from operating. The consent interface identifies relevant purposes and third parties, provides access to this Notice before selection, and records the policy version, timestamp, region or rule set, selected purposes, and proof needed to respect the choice. The record is not used for advertising. Withdrawal applies prospectively and does not make earlier consent-based processing unlawful. When a user withdraws, Loglune stops or disables the affected non-essential technology as soon as technically practicable and communicates the withdrawal to a third party relying on Loglune’s consent where required.
6. Managing technologies
You can change optional choices at any time through /cookies#cookie-settings and can clear cookies or local storage in your browser. Rejecting optional technologies is as accessible as accepting them. Clearing authentication cookies signs you out. Clearing local storage may reset theme, consent, onboarding, or display preferences. It does not delete account data or the flag definitions and version history stored in your Loglune account. Stripe provides separate controls for technologies on its checkout and account-management pages. Browser or device controls may block, delete, partition, or expire technologies, but browser settings are not treated as consent unless applicable law and the configuration make them a valid, informed signal. Private-browsing mode does not guarantee that a provider receives no network or device information. Loglune’s response to Global Privacy Control and Do Not Track is described in the Privacy Notice. Because Loglune does not sell personal data or use cross-site behavioral advertising, these signals do not disable a practice that Loglune does not perform. A legally binding signal will be honored if relevant practices change. Technologies used on Stripe, Google, or another separately controlled page are governed by that provider’s controls and notice. Loglune identifies the provider and purpose but cannot directly delete a technology controlled solely on the provider’s domain.
7. Notice versioning and change controls
We update this Notice when technologies or providers change. Loglune reviews the production inventory at launch, when a provider or SDK changes, when a new purpose is introduced, and periodically thereafter. The review verifies names, parties, purposes, data, legal status, duration, default state, consent behavior, links, and deletion controls. If a change adds a non-essential technology or materially expands a consented purpose, the technology remains disabled until the required updated notice and fresh consent are in place. Historical versions of this Notice are retained. Report a cookie or storage concern to support@loglune.com. Questions about personal data collected through a technology are handled under the Privacy Notice.