Cookie Policy

0. Operator and contact details

[PredictDuel Legal Entity Name] operates the current PredictDuel service. The registered address placeholder for notices related to this Cookie Policy is [Registered Business Address, City, State/Region, Postal Code, Country].

Questions about cookies, consent choices, and related privacy issues may be sent through the platform support flow, to [privacy@predictduel.com], or for general support to [support@predictduel.com].

1. Scope

This Cookie Policy explains how PredictDuel uses cookies, local storage, session identifiers, SDK identifiers, pixels, tags, and similar technologies across the website, account flows, market pages, and related services.

This policy should be read together with the Privacy Policy and Terms of Service. Where local law requires consent or additional notice, this policy is intended to supplement those requirements rather than replace them.

2. What technologies we use

We use first-party and service-provider technologies that store or read data on your browser, device, or session context. These may be session-based or persistent depending on purpose.

For simplicity, this policy refers to these technologies collectively as cookies, even where the implementation uses local storage, session storage, device identifiers, SDK state, or similar methods.

3. Why we use them

To keep accounts signed in, protect requests, maintain session continuity, remember preferences, preserve market and onboarding state, measure performance, detect abuse, and support lawful platform operations.

Some technologies are required for core security and functionality. Others help us improve the service or remember convenience settings. Optional technologies are used only as permitted by applicable law and your consent choices.

4. Cookie categories

Strictly necessary cookies support authentication, request integrity, anti-fraud controls, session continuity, routing stability, and core site operation.

Functional cookies remember user preferences such as locale, display density, dismissed notices, onboarding state, and market filter preferences.

Analytics cookies help us understand reliability, route performance, feature adoption, navigation flow, and release regressions in aggregated or pseudonymous form.

Security and compliance technologies help detect bots, rate-limit abuse, correlate suspicious sessions, and enforce regional or policy restrictions where needed.

5. Consent and regional treatment

Where applicable law requires opt-in consent, non-essential technologies remain off until you grant consent through the available controls.

Strictly necessary and certain security-related technologies may remain active because they are required to provide the service safely, prevent fraud, or comply with legal obligations.

If local law grants additional rights relating to advertising, analytics, or cross-context disclosures, those rights may be exercised through the controls we make available.

6. Managing preferences

You can manage available choices through browser settings, device-level controls, and any cookie or privacy controls provided in the service, including account settings where available.

Clearing browser storage, using private browsing, or changing devices may reset saved preferences. Some choices may need a refresh, sign-in renewal, or a new session before taking full effect.

7. If you block cookies

Blocking all cookies or storage technologies may prevent sign-in, session continuity, account protection, market interactions, and other important features from working properly.

PredictDuel is not responsible for degraded performance caused by browser, extension, enterprise policy, or device-level blocking of technologies required for secure service operation.

8. Information collected through cookies

Depending on the technology and purpose, cookie-related data may include technical identifiers, session state, browser and device metadata, timestamps, page interactions, latency or error signals, approximate region indicators, and abuse-detection signals.

We use minimization, retention, and access controls appropriate to the purpose of the data and as described more broadly in the Privacy Policy.

9. Third-party providers

We may use approved service providers to support hosting, analytics, monitoring, authentication, communications, fraud prevention, and other operational needs.

Where third-party technologies are used, providers are expected to be bound by contractual restrictions covering confidentiality, security, purpose limitation, and legal compliance.

Provider choices may change over time as infrastructure, product needs, and compliance expectations evolve.

10. Retention and expiry

Some cookies expire when your session ends. Others persist for a defined period to preserve preferences, maintain security continuity, or support fraud-prevention controls.

Retention periods may change as legal, technical, or operational needs evolve. We periodically review whether persistence periods remain necessary and proportionate.

11. Security-specific clarifications

Certain cookies and related technologies are intentionally short-lived, rotating, or not fully described in public technical detail because full disclosure could weaken anti-abuse controls.

These technologies may be used to detect session hijacking, credential attacks, repeated policy evasion, automation abuse, and other integrity risks.

12. International use and data protection rights

Cookie-related data may be processed in jurisdictions where PredictDuel or its providers operate. Where required, we apply transfer safeguards and related privacy controls appropriate to the processing context.

If cookie-derived data qualifies as personal data under applicable law, you may exercise relevant privacy rights using the channels described in the Privacy Policy or by contacting [privacy@predictduel.com].

13. Policy changes

We may update this Cookie Policy to reflect changes in technology, providers, legal requirements, product architecture, or consent practices. The latest version will be published on the site with an updated effective date.

14. Representative examples by category

14.1 Strictly necessary

• Session authentication and secure session continuity
• CSRF protection and request integrity markers
• Rate-limiting, anti-replay, and anti-abuse correlation state
• Routing continuity for sensitive account and market actions

14.2 Functional

• Display settings, density choices, and locale preferences
• Dismissed notices and onboarding progress memory
• Saved market filters and convenience preferences

14.3 Analytics

• Route performance and latency measurement
• Error-frequency and release-regression monitoring
• Feature adoption and navigation-path analysis