Liquidium WTF Cookie Notice
Effective date: September 14, 2026 · Version: 1.0
This Cookie Notice explains how Liquidium Inc. uses cookies and similar browser technologies on the Liquidium WTF marketing website at https://liquidium.wtf and the application at https://app.liquidium.wtf, including its Bitcoin and Robinhood Chain interfaces. It supplements the Privacy Policy.
Your choices
When no analytics choice has been saved, PostHog persistent analytics, automatic capture, heatmaps, surveys, and session recording are disabled. If you accept analytics, Liquidium may enable those PostHog features on the marketing website and in the application's Bitcoin and Robinhood Chain interfaces.
The marketing website also loads Google Analytics 4 after analytics acceptance. Google Tag Manager can load on the marketing website before an analytics choice is saved; loading that container is separate from accepting analytics cookies and may disclose network and device information to Google. Neither Google Analytics nor Google Tag Manager is used in the application at app.liquidium.wtf.
If you decline analytics, PostHog analytics cookies, persistent analytics identifiers, automatic capture, and session recording remain disabled. The marketing website may still send PostHog basic cookieless page and navigation events. The current application configuration may still send PostHog a limited set of cookieless event names concerning wallet connections, signatures, offers, and transaction outcomes. Those application events use a shared cookieless identifier and omit custom event properties, but PostHog may still receive ordinary network information such as an IP address. The feedback form may transmit information you deliberately submit after displaying a separate notice.
Browser Do Not Track and qualifying Global Privacy Control signals disable PostHog event capture regardless of a saved analytics choice.
You can accept, decline, or later change your choice using the cookie banner or cookie settings control where available. On the marketing website, use Cookie settings in the footer. Rejecting analytics does not prevent use of core lending or borrowing functionality.
Technologies currently used
| Category | Technology or provider | Purpose | Duration or operation |
|---|---|---|---|
| Necessary | analytics_consent first-party cookie | Records whether analytics was accepted or declined | 12 months after acceptance; 6 months after rejection |
| Necessary | Bitcoin jwt cookie | Maintains an authenticated Bitcoin wallet session | Until the authentication token expires or the user signs out |
| Necessary | Bitcoin walletType cookie | Remembers the connected Bitcoin wallet type | Until the authentication token expires or the user signs out |
| Necessary | Wallet-connection browser storage used by Wagmi, Reown, Coinbase Wallet, injected wallets, or similar wallet software | Remembers a selected connection and supports reconnection | Until disconnection, provider expiration, or clearing browser data, depending on the wallet/provider |
| Analytics | PostHog cookies, local storage, memory storage, and cookieless events on the marketing website and in the application | Product analytics, page and navigation events, performance, errors, heatmaps, surveys, and consented session replay | Persistent storage is enabled only after acceptance; provider-side retention is governed by Liquidium's configured retention settings |
| Analytics | Google Analytics 4, marketing website only | Page views and selected interaction events | Loaded after analytics acceptance; cookie duration depends on Google's technology and Liquidium's configuration |
| Tag management | Google Tag Manager, marketing website only | Loads and manages tags | The container can load before an analytics choice is saved and may disclose network and device information to Google |
| Support | Intercom cookies and browser storage | Loads the support messenger and maintains a support session | Intercom loads only when the user opens support; duration is controlled by Intercom and browser settings |
Analytics safeguards
When PostHog session recording is enabled after consent, it is configured to mask page text, element attributes, and input values. It does not intentionally record request headers or bodies or console logs. URL query strings and fragments are removed from captured analytics URLs.
Intercom is loaded when a user chooses to open support. Information deliberately submitted through the messenger is handled as described in the Privacy Policy.
Retention and deletion
Cookie and browser-storage duration is different from server-side retention. Deleting browser data does not automatically delete analytics, authentication, or support records already received by Liquidium or a provider. Liquidium retains those records only as long as reasonably necessary for the purposes described in the Privacy Policy, security and dispute handling, and legal obligations, and then deletes or deidentifies them where feasible.
Public blockchain records are not cookies and cannot be deleted by Liquidium.
Contact
Privacy questions or requests: help@liquidium.wtf