Privacy Policy

What Raven Hubs handles directly

Raven Hubs handles the website shell, catalog metadata, public page copy, categories, guide content, policy pages, support routing, and technical delivery of Raven Hubs pages. Game pages use library metadata such as titles, descriptions, categories, tags, controls, thumbnails, permission notes, quality flags, source notes, and editorial review fields. Browsing does not require a visitor account, profile, payment detail, or login session.

• Catalog and policy content is used to power discovery pages, search metadata, sitemaps, guides, and related-game recommendations.
• Support, correction, and rights-review requests use support@ravenhubs.com.
• Privacy, data access, and deletion requests use privacy@ravenhubs.com.
• Security reports use security@ravenhubs.com.
• Raven Hubs can correct public page copy, remove or noindex catalog pages, change play mode, and update internal metadata when review evidence changes.

Current service inventory

The following list reflects the active site configuration used to render this page. If the live deployment enables or disables analytics, ads, consent, or verification services, this page is generated from the same site configuration rather than a separate template.

• Analytics: 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 Tag Manager: disabled; container ID is not configured.
• Google AdSense: 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.
• Cookie consent: 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.
• Search Console verification: not configured in this environment.
• Visitor accounts: not used; Raven Hubs does not require account registration, login, profile storage, or payment details for browsing.
• Server, CDN, and security logs: operational delivery may record IP address, user agent, request path, referrer, timestamp, response status, and security events for reliability, abuse prevention, debugging, and legal review.

Local storage and cookies

Raven Hubs uses only the storage categories needed by the active site configuration. The Cookie Policy lists the same actual cookie and storage categories, including browser privacy controls for clearing or blocking them.

• 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.

Logs, IP, device, and browser data

Server, CDN, and security logs may record IP address, user agent, request path, referrer, timestamp, response status, and security events. Raven Hubs uses this operational data for reliability, abuse prevention, security review, debugging, legal review, and aggregate site health checks. The public site code does not create user accounts or store payment profiles.

Third-party game frames

Some games may be loaded through third-party game frames or opened on a third-party source page. Those providers may use their own privacy practices, cookies, storage, analytics, advertising identifiers, save data, or device/browser signals after a visitor chooses to load or open the game. Raven Hubs cannot represent third-party game frames as Raven Hubs data handling, and visitors should review the external provider's own policy when available.

Google services and advertising data

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. 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 Google Analytics, Google Tag Manager, Google AdSense, or related Google services are enabled, Google may receive cookies, device identifiers, IP address, page activity, and browser information for measurement, ad delivery, fraud prevention, and service protection. Google explains partner-site data use at https://policies.google.com/privacy/partners.

Visitor choices and requests

Visitors can clear local preferences, consent storage, and third-party storage through browser privacy controls. Privacy or data-access questions can be sent to privacy@ravenhubs.com; game corrections and rights-review reports can be sent to support@ravenhubs.com. If a consent control is shown in the active region, use it to manage optional analytics or ads choices. If real AdSense is enabled for EEA, UK, or Switzerland traffic, Raven Hubs still needs the owner-selected Google-certified CMP documented and wired before the site should be treated as AdSense-ready.