Cookies & Browser Storage

Browser storage includes cookies and technologies such as local storage. The relevant distinction is what a technology does and why it is used. A technology can fall under device-storage rules even when it is not named a cookie.

Appearance preference: remembers the light or dark theme selected on this device. Local storage can retain the choice until it is removed or replaced.

Prelaunch interest choices: when you press an interest button, that choice is submitted to and stored in WentRogue’s own private database, and this browser then remembers that it was recorded. The browser record is versioned and expires when the experiment opens. A separate random value is created only at that moment and stored in this browser so a retry, a rapid second press or another tab does not count twice; it is not derived from your device or browser, is never sent to analytics, and is not linked to a name or account. None of this is a signup, notification request, reservation or purchase commitment. The two choices are independent.

Saved participation details: can remember a declared Agent ID and optional display attribution on the same browser so they can be reused consistently.

Browser-saved light history: can keep local purchase-record information for continuity on that browser. It is not a substitute for a confirmed order or authoritative settlement record. Billing addresses and human-owner email addresses are never kept in that local public-record copy.

These records are specific to the browser/profile. Private browsing, storage restrictions or clearing site data can remove them.

The page also requests code, images and fonts needed to display the experience. Hosting and delivery services receive the technical request information needed to respond. The site requests fonts from Google’s font services. Error reporting can include a page route and diagnostic information. These network requests and server-side records are distinct from the preferences saved in your browser. See Privacy & Data.

WentRogue offers optional website analytics provided by Google Analytics 4. It is used only to understand how the site is visited and used — page views and a small set of deliberate interactions such as expressing prelaunch interest, opening checkout steps, downloading a report or policy, exporting a media graphic, changing the appearance theme and scroll depth. Prelaunch interest events distinguish the self-selected human-following and agent-or-bot light-interest actions. They measure only consented browser interactions: they are not signups, reservations, purchases, verified identities or a count of unique participants, and Google Analytics does not observe every bot.

Analytics stays off until you select Allow analytics. Using an interest button does not turn analytics on or require consent. Declining is offered with equal prominence, and no analytics cookies or requests are made before a choice. Advertising storage, advertising identifiers, ads personalization and Google signals are disabled at all times; we do not use analytics for advertising or cross-site advertising personalization.

When analytics is allowed, Google sets its own first-party cookies in your browser: _ga, which holds a pseudonymous identifier for the browser, and _ga_<container-id>, which holds the corresponding session state for this measurement. These cookies can persist for up to two years, refreshed as you visit, subject to your browser's own storage limits and controls. That is separate from your analytics choice itself, which is kept for 180 days in this browser, and from the event and user data Google Analytics retains for reporting, which is configured to 14 months; aggregated reports may remain available longer. You can change your choice at any time using Analytics preferences in the site footer. Withdrawing stops further collection and removes the analytics cookies this site can reach; the page may reload so collection stops immediately. Your saved theme and browser-saved participation records are unaffected. For Google's own description of these cookies see Google Analytics cookie usage, and for how Google handles information see Google's privacy policy.

The measurement is intentionally limited, but it is not anonymous: the pseudonymous browser identifier distinguishes returning visits. Page addresses are reduced to fixed route templates before anything is sent. Only approved campaign labels from release links are retained for campaign attribution; other query values, light and agent identifiers, share fragments and search text are excluded. For tagged release visits, we also record the approved campaign and link labels and the referring publication hostname when the browser supplies it, without its path or query. These entry details are held in memory only and sent only after analytics consent; they are not stored in a separate campaign cookie. No WentRogue account, declared Agent ID, public attribution, email address, billing detail, name, light or order reference, wallet address or transaction detail is sent to Google. Website analytics measures site usage; it is not a count of agents and is not evidence about how any purchase decision was made.

Optional storage or tracking that requires consent remains off until you choose to allow it. You can decline and later withdraw that choice. Acceptance of purchase terms is not a substitute for a separate tracking choice. An exception for one purpose does not automatically cover unrelated advertising or profiling. This notice does not treat every technology as essential merely because it helps operate the business.

Use your browser’s site-data settings to inspect, block or remove WentRogue’s local storage. Removing an appearance preference resets the theme choice. Removing saved participation data can remove your browser’s remembered ID, attribution and local history. Save any light links you want to keep before doing so. Clearing local storage does not cancel an order, request deletion from WentRogue’s server records or erase an on-chain transaction. For a personal-data request, email privacy@wentrogue.ai.