Cookie Policy

Cookies and similar browser storage

A cookie is a small text value a website or service can store in your browser. Websites also use related technologies such as local storage, pixels, and scripts that read or write device information. These tools can remember a preference, keep a session secure, count visits, support a conversation, or deliver advertising.

This policy separates storage required for a feature you request from storage used by optional analytics, advertising, or support providers. A listed optional provider is only active when it has been configured on the live site.

Necessary and preference storage

The guide can use limited first-party storage for site operation:

• Language preference — a value such as PARAGLIDE_LOCALE can remember the language selected in the interface.
• Authentication session — a secure session cookie can keep a user signed in if they deliberately enter a protected account or administration area. Public guide reading does not require this session.
• Interface state — local storage or a cookie can remember a preference inside a protected dashboard, such as whether a navigation panel is open.
• Security controls — request and session signals may be used to limit abuse, validate a session, and protect the service.

These items are not used to build an advertising profile. Their duration depends on the feature and can end when the browser session closes, when you sign out, when the value expires, or when you clear it.

Analytics storage

Analytics helps identify high-value guides, broken pages, and general traffic patterns. The live site can enable one of the following tools:

• Google Analytics 4 — the standard tag can use _ga to distinguish users and _ga_<container-id> to maintain session state. Google's GA4 cookie reference documents a default lifetime of up to two years for these cookies, subject to configuration and browser limits.
• Plausible Analytics — the standard hosted service is designed for aggregate measurement without cookies. See Plausible's data policy. A custom script source or later configuration should be checked separately.

When local law requires a choice before non-essential analytics storage is used, the live site should wait for the relevant consent. You can also block analytics scripts or clear their stored values through your browser.

Advertising storage

If Google AdSense is enabled, Google and advertising partners may use cookies, web beacons, IP addresses, or similar identifiers to deliver ads, control how often an ad appears, measure performance, prevent invalid activity, and—where permitted and selected—personalize advertising. Google provides a current explanation of how AdSense uses cookies.

Advertising storage is not necessary to read the guide. AdSense configuration, regional privacy messages, and consent controls must be reviewed before ads are activated for visitors in locations that require prior consent. Google's advertising settings and your browser controls provide additional ways to limit personalization or clear stored identifiers.

Support-widget storage

The site software can optionally load Crisp or Tawk.to. A support widget may use cookies or local storage to keep a conversation connected, remember a chat session, reduce abuse, and operate the widget across page changes.

If no support widget appears, its script is not enabled through the site's configuration. If you choose to use an enabled widget, avoid sharing game-account passwords, recovery codes, payment information, or other sensitive credentials.

External websites and media

Links to Steam, official game news, YouTube, community posts, and other references do not by themselves give this site control over those services. When you click a link, the destination may set its own cookies and process information under its own policy.

If an external video, ad, or widget is embedded directly in a page, its provider may receive a request when that element loads. The guide should identify or defer non-essential embeds when local rules require a visitor choice.

How to manage browser storage

Most browsers let you view, delete, or block cookies and site storage for one website or all websites. You can usually find these controls under Privacy, Security, Cookies, or Site Data. Private browsing and content-blocking extensions can provide additional limits, although their behavior varies.

Deleting storage can reset a language choice, sign you out of a protected feature, remove a support conversation identifier, or change analytics and advertising recognition. Blocking all storage should not prevent you from reading ordinary public guide text, but it can break optional or account-based features.

If the live site presents a cookie-preference control, use that control to change optional choices. A browser-level block can still take priority over a site preference.

Changes and contact

This inventory should be reviewed whenever an analytics, advertising, support, authentication, or localization feature changes. The date at the top identifies the current revision.

For a question about a cookie or script observed on the production site, use the contact method published there and include the page URL, cookie or storage name, and approximate observation time. Do not include a game-account password or payment credential.