Privacy on the PokerStars digest mirror
This document applies solely to the hostname styled as the PokerStars insight cell / UK digest. Regulated PokerStars clients remain independent controllers for gambling accounts, geolocation telemetry tied to eligibility, financial instrument tokens, and game-integrity archives. If you are researching how the operator stores hand histories or verification selfies, close this tab and read their official privacy hub while logged in. Our mirror processes a narrow editorial dataset: readers learning terminology, comparing formats, and occasionally emailing corrections.
Data elements
Infrastructure captures connection metadata—IPs, TLS client hints where supported, requested paths, response codes, and time coordinates. Analytics may assign pseudonymous keys to aggregate journeys through digest sections. Email to the footer inbox stores addresses, bodies, and delivery diagnostics. Optional alerts capture subscription tokens. We do not operate a KYC vault on this stack.
Purposes
Security engineers watch logs for brute-force spikes and scraping abuse. Editors study engagement patterns to prioritise rewrites on variance explainers. Privacy staff answer access or deletion requests concerning our holdings. Marketing use is limited to explicit newsletter opt-ins; we do not buy cold lists.
Legal bases and balancing
Legitimate interests cover fraud prevention, uptime, and aggregated analytics documented with lightweight impact assessments. Consent covers optional cookies where banners demand it and covers promotional mail. Legal duties may elongate retention for specific threads.
Technologies
Strictly necessary cookies stabilise preferences. Measurement scripts may rely on first-party storage. Embedded third-party media can introduce its own trackers when activated; their policies control that layer.
Processors and confidentiality
Hosting, CDN, mail, analytics, and backup vendors process subsets under instruction. They may not monetise gambling-related correspondence for unrelated advertising. Transfers outside the UK use approved mechanisms.
Retention and minimisation
Logs expire on rolling windows tuned for forensics. Mailbox data minimises attachments automatically where possible. Newsletter contacts purge after unsubscribe unless narrow legal holds apply.
Rights and ICO escalation
Exercise GDPR-style rights by emailing the privacy contact with sufficient detail to locate you—usually email address and approximate dates. We may request proof of identity before releasing exports. Unresolved complaints may go to the Information Commissioner’s Office.
Minors
Digest readers should be adults. We delete data that appears juvenile once notified.
Policy updates
Insight mirrors change when templates or subprocessors change. We revise this text when practices diverge materially. Your browser hostname must match the policy you rely on.
Aggregated benchmarking
We sometimes compare anonymous traffic spikes across digest sections to prioritise rewrites; those benchmarks never publish individual reader identities.
Law enforcement requests
We disclose personal data to authorities only when legally compelled and narrowly scoped; where allowed, we notify affected users after the fact.
Data accuracy
You are responsible for the accuracy of information you send us voluntarily. We correct obvious typos in correspondence but may ask you to resubmit formal rights requests if identity checks fail.
Contact for privacy requests
Use the same hostname-specific footer address marked for privacy, include “privacy request” in the subject line, and allow reasonable time for verification and response during business hours.
Version notes may appear in internal change logs; the on-page text remains the controlling statement for visitors.