Privacy on this PlayOJO informational host
Privacy expectations differ between browsing an editorial guide and maintaining a funded account on a licensed casino. This page covers the first scenario on the PlayOJO informational host you are reading now. The second scenario—KYC vaults, staking histories, reward ledgers—is documented by PlayOJO where regulation requires granular transparency. We draw a bright line so you do not assume we can export spin logs or payment tokens; we cannot. What we might hold includes technical server logs, optional pseudonymous analytics identifiers, and email threads you initiate. That collection still deserves clear rules, retention discipline, and exercisable rights under UK law.
Who decides processing purposes
Our configured publisher acts as controller for data tied to this informational property. Vendors assist under processor terms. If another company claims overlap with branding, distinguish trademark use from database control—only actual stewards answer subject access requests for a given dataset.
Network-layer data
IPs and TLS metadata help deliver pages securely and block malicious automation. They are imperfect fingerprints—mobile networks recycle addresses, VPNs obscure origin. We do not treat a log entry as a permanent portrait of a household.
Consent experiences
Non-essential cookies or SDKs, if any, should wait for valid consent where UK rules require it. Rejecting optional categories must remain feasible without locking informational reading behind unrelated paywalls. Essentials proceed under legal necessity arguments.
Email ecosystems
SMTP metadata is visible to multiple hops. Assume standard encryption in transit, not end-to-end secrecy, unless both parties configure otherwise. Sensitive gambling account trivia should not be used to prove a wording disagreement to us.
Aggregated insight
Popular-page metrics and scroll distributions may guide editorial prioritisation. Aggregates lack names. Vendors operating tools publish their own modelling and retention policies separately.
GDPR requests
Specify the right—access, erasure, etc.—and the channel you used. Verification prevents impersonation. Some rights conflict with legal retention or expression balances; we explain constraints rather than ignoring mail.
Incidents
Breaches undergo UK law assessment for notification duties. Patch cadence and monitoring reduce risk without guaranteeing zero events. Users should harden operator accounts with MFA and unique passwords.
Experiments
Layout tests may log variant IDs per session. Data supports design, not resale. Tests conclude; logs expire on rotation.
Retention posture
We avoid indefinite personal mail hoarding. Legal holds pause deletion when disputes exist. De-identified statistics may persist forever without conflicting with erasure of named rows.
Privacy contact
Email the footer address with “privacy request” and the right named. Allow verification time. Operator-held exports belong to PlayOJO support, not to this inbox.
Relationship to marketing email
If you receive promotional mail from PlayOJO or partners after visiting outbound links, unsubscribe or adjust preferences through the sender’s own mechanisms. This informational host does not control operator mailing lists and cannot remove you from them. If you never want marketing, decline consent banners carefully on each domain you visit and use inbox filters proportionately. Our own mail relationship begins only when you email us first or explicitly subscribe to a list we actually operate—currently we do not run a newsletter from this template.