Aurea.gg — Cookie & Tracking Policy

Effective date: October 29, 2025
Last updated: October 29, 2025

By using aurea.gg (the “Service”), you consent to our use of cookies, SDKs, pixels, and similar tracking technologies (collectively, “Cookies”) as described below and in ourPrivacy Policy. This policy explains what these technologies are, why we use them, and the choices you have.

1) Why we use cookies

Aurea uses tracking technologies for the following purposes:

  • Strictly necessary: Vital for the Service to work (e.g., authentication, security, load balancing, fraud prevention).
  • Performance / Analytics: Help us understand how the website and apps are performing so we can improve reliability, features, and UX.
  • Functionality: Remember your preferences (e.g., language, privacy defaults, media settings) to enhance your experience.
  • Advertising / Measurement: Where enabled and lawful, help deliver/measure advertising and attribution, limit ad frequency, and make content more relevant to your interests.

We may record, in a privacy-respectful manner, what products/features you view or interact with (e.g., highlights, leaderboards) to streamline browsing and surface more useful content.

2) How this applies to Aurea’s product

Because Aurea unifies gamer identity across platforms (e.g., Steam, Riot, Battle.net, PlayStation, Xbox, Epic, Discord, Twitch), we rely on cookies/SDKs to keep you logged in, safeguard session integrity, measure feature adoption (e.g., auto-highlights, insights), and—where permitted—support campaign attribution for creators and partners.

3) Types of tracking technologies we use

  • Cookies: Small text files stored in your browser. You can configure your browser to accept/reject cookies (see Section 7).
  • Local/session storage & IndexedDB: Browser storage for preferences, caching, performance.
  • Pixels / web beacons / clear GIFs: Tiny graphics used to measure opens, visits, and interactions; they do not store data on your device.
  • Software Development Kits (SDKs) (apps/desktop): App-embedded libraries used for analytics, crash reports, messaging, and attribution.

Cookie lifespans

  • Session: Expires automatically when you close your browser or app.
  • Persistent: Remains until it reaches its set expiration or you delete it (typically 1 day to 24 months).

4) Cookie categories and examples

  • Strictly necessary: login/auth cookies; CSRF and security tokens; load-balancing / edge cache flags.
    Examples: aurea.gg session token; Cloudflare/Vercel edge/session routing.
  • Preferences: UI language, theme, privacy defaults, media/playback settings.
    Examples: locale, cookie-consent state.
  • Performance / Analytics: page views, latency, feature adoption, crash diagnostics.
    Examples: PostHog/Google Analytics app instance IDs; internal telemetry; crash logs.
  • Functionality: video playback, embedded content, notifications.
    Examples: clip playback buffering; in-app messaging identifiers (e.g., Knock).
  • Advertising / Measurement (web/app, where enabled): campaign attribution, ad frequency capping, conversion measurement.
    Examples: install/visit attribution IDs, referral/UTM parameters.

5) Partners and third-party technologies

We sometimes partner with third-party services that may use tracking technologies to provide certain features or analytics, including:

  • Attribution tracking: estimates which marketing source or partner should receive credit for a visit, signup, or purchase.
  • Remarketing: presents relevant messages to audiences who previously interacted with Aurea.
  • Cross-device tracking: recognises an audience across multiple devices/browsers to provide consistent experiences and measurement.

These technologies may recognise your browser or device each time you visit, but do not grant partners access to personally identifying information from Aurea. Third-party technologies are governed by their own privacy policies; we require lawful use and appropriate safeguards but do not control their practices.

The Service and third parties may also provide widgets (e.g., embeds/social plugins). Aurea and the widget provider may receive analytics about your interaction with the widget. Manage the widget’s privacy preferences via your account with the third party.

6) Consent, regional rules & “Do Not Sell/Share”

  • EEA/UK: We request consent for non-essential Cookies via our banner/Consent Management Platform (CMP). You can modify your choices any time via Cookie Preferences.
  • Global Privacy Control (GPC): We honour browser-level GPC opt-out signals where legally required.
  • U.S. state laws: If certain analytics/advertising uses are deemed a “sale” or “share,” you can opt out via our Do Not Sell/Share control.

7) Opting-out & managing cookies

Browser controls: Most browsers let you block/erase cookies or set preferences for certain sites. Common help pages:

Mobile settings: On iOS and Android, you can reset/limit advertising IDs (IDFA/GAID) and control app-level permissions.

In-product controls: Use our Cookie Preferences panel to adjust non-essential categories and view consent status.

Interest-based advertising: You can opt-out of certain interest-based advertising on participating platforms (e.g., “YourAdChoices,” “YourOnlineChoices”). Opt-outs are browser/device-specific and may not block all ads.

Note: blocking all cookies may prevent some core features (login, security, clip playback) from working properly.

8) Retention

Cookie/SDK identifiers persist for their designated lifespan (see Section 3). We generally use session cookies for authentication flows and persistent cookies (1 day to 24 months) for preferences, performance, and attribution—unless you delete them sooner or withdraw consent.

9) Changes to this policy

We may update this Cookie Policy from time to time. We will post updates here and modify the “Last updated” date above. Where required, we will re-prompt for consent.

10) Contact

Questions about this policy or your choices?