Cookie Policy

Current cookie and storage inventory

This inventory describes the storage categories that Raven Hubs pages can use in the active site configuration. It avoids listing services that are not enabled by the current configuration.

• Necessary site storage: browser theme preference may be stored locally by the theme provider; no account session cookie is required for browsing.
• Consent storage: when the lightweight consent adapter is enabled and a visitor makes choices, ravenhubs:consent:v1 can be stored in localStorage with necessary, analytics, ads, marketing, and updatedAt fields.
• Analytics storage: GA4 or GTM cookies are not loaded by Raven Hubs while analytics is disabled; if analytics is enabled, Google storage depends on the active consent mode and browser settings.
• Advertising storage: AdSense cookies or similar identifiers are not loaded by Raven Hubs while AdSense is disabled; if AdSense is enabled, ads still require publisher ID, slot IDs, page-level ad eligibility, and consent where required.
• Third-party game storage: after a player starts or opens a third-party game, the external game host may set its own cookies, local storage, analytics, advertising identifiers, or save data under its own policies.

Necessary site storage

Raven Hubs does not require account session cookies for browsing. Necessary storage is limited to site preferences that keep the interface usable, such as theme preference and, when enabled, the lightweight consent preference stored as ravenhubs:consent:v1.

Analytics and advertising storage

Raven Hubs analytics is enabled through direct GA4 with Measurement ID configured. Page-view and event payloads are limited to site, environment, path, title, and gameplay context; contact details, tokens, IP fields, and similar sensitive identifiers are filtered before analytics events are sent. Google AdSense is enabled in the active site configuration with publisher ID configured and 0 ad slot IDs available. Ad slots still render only when page-level ad eligibility and consent checks pass. When Google analytics or advertising services are active, cookies or similar identifiers may be used for measurement, ad delivery, fraud prevention, personalization where allowed, and service protection. Ad slots still require publisher configuration, slot IDs, page-level ad eligibility, and consent where required.

Third-party game frames

Third-party game frames may use their own cookies, local storage, analytics, advertising identifiers, or save data after a player chooses to load or open a game. Those technologies are controlled by the external provider, not by Raven Hubs. Clearing Raven Hubs site preferences may not clear storage created by an external game host.

Consent and CMP boundary

The lightweight Raven Hubs consent adapter is enabled in the active site configuration. It can store ravenhubs:consent:v1 in localStorage and update Google consent signals, but it is not a Google-certified CMP. Before enabling real AdSense for EEA, UK, or Switzerland traffic, Raven Hubs still needs an owner-selected Google-certified CMP and a footer reopen action wired to that CMP. When enabled, this lightweight adapter can record preferences for Raven Hubs script gating, but it should not be treated as the final legal consent solution for real AdSense traffic in regions that require a Google-certified CMP.

How to manage cookies and storage

Use browser privacy controls to clear local storage, block third-party cookies, remove site data for ravenhubs.com, or clear storage created by external game hosts. If a consent control is shown in your region, use it to manage optional analytics or ads choices. Privacy and cookie questions can be sent to privacy@ravenhubs.com.