Playing Wanted Dead Or a Wild Slot game means providing personal data wanteddeadorwild.uk. This document lays out exactly how long we retain it, the reasons, and what technical protections underpin each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We manage identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its unique retention clock. Identity records are kept for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation is applied. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors check our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log records every edit, and we give you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Safe Gambling and Self-Exclusion Registers
Deposit limits, time checks, and timeout settings are stored for your account’s whole period and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register maintained without time limit under UKGC licence requirements. The register is encrypted separately, checked only at login or registration, and never used for analytics. Entry is confined to educated compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no banking or gameplay records. We review it annually to fix errors and remove deceased individuals. Otherwise, it is kept permanent. This retention is obligatory and exempt from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check clocks use transient session counters that clear every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and automatically reactivates when you come back, even after a long break. Changing the interval mid-session introduces the new value right away for the next reminder. These settings are purged only upon verified account deletion. Session timer data resides in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are checkable through the same three-year access log standard. We do not profile or market based on these settings.
Data Subject Access Request and Deletion Workflows
When a subject access request arrives, we compile a organized JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We create a confirmation report outlining erased versus retained categories and their justifications. This report is maintained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Policy Evaluation and Data Breach Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are minuted with DPO, CISO, and legal counsel. A public summary is published in our privacy centre, minus confidential details. Material changes are emailed 30 days ahead. Minor edits are silently recorded. If a breach occurs affecting data under this policy, we inform affected individuals within 72 hours if high risk, report with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We hold a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Update Log
We preserve a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log specifies exactly which sections changed and why. Previous versions remain accessible for comparison, so you can see precisely what was added or removed. Material modifications affecting your rights are conveyed via email at least thirty days in advance. Minor typographical fixes are deployed silently but still recorded. Each entry is cryptographically signed to prove integrity, and annual independent audits confirm the log’s accuracy. The log is a living document reflecting our evolving data practices. You can view the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.
Session Gameplay and Analytics of Behavior Data
Each spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then compress them into an anonymous statistical digest utilized for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—persist for the same 24-month window and are then deleted. Feature trigger heatmaps stay for 12 months before merging into a global model. RNG seed audit trails get 36 months. Error diagnostics receive 90 days. No individual gameplay data goes into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then anonymised aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then cycled out
Registration Account and Identity Verification Data
Main identity data—scans of government IDs, residence proof, biometric selfie verifications—are held for 5 years after your last session or account termination, whichever comes later. This encompasses contractual limitation periods and anti-money laundering responsibilities. We obtain only the key information: ID number, validity, nationality. The full-resolution image gets destroyed right after extraction. Once five years pass, all original data is purged, but a cryptographic hash of the verification result remains for two more years inside an logging system. Identity data sits stored encrypted with AES-256-GCM, isolated from analytics, and every access is tracked for 3 years. Unnecessary fields like birthplace are deleted at the time of verification to reduce the data volume. Yearly reviews confirm accuracy and actively purge expired entries.
File Upload and Biometric Handling
Upload an ID through our protected portal and automatic verification completes within ninety seconds. We pull the document number, expiry, country of citizenship, and a reliability score, then delete the full-resolution image instantly—it is never stored on disk. The initial file stays in an memory buffer and disappears after analysis. A compressed, watermarked preview is generated for compliance purposes and stored only for the identity lifecycle. That small image lives in a immutable vault with rigorous controls and is never exposed to customer support. Collected information are encoded and saved for the 5-year-plus-2-year hash period. All processing runs on ISO 27001 certified UK servers, and every thumbnail access is stored unchangeably.
Biometric Data Specifics
Liveness verifications collect a brief video feed completely in memory. Frames are analyzed and removed within milliseconds of time. Only a mathematical vector of facial points remains. This numerical representation lacks any image data and cannot be reverse-engineered into a picture. It stays for the duration of identity verification and is irreversibly removed upon account closure or after a five-year period. The vector sits in a specialized HSM with automatic expiration and is never exported. Login verifications happen inside the HSM’s secure enclave without revealing the original vector. The vector is bound to a pseudonymous identifier separated from marketing profiles, which makes re-identification very hard. Even system administrators are unable to view or recreate face characteristics from the kept numerical representation.
Marketing Consent and Communication Logs
We store your consent record—timestamped, with IP address, and method-captured—for the life of our partnership plus six years after withdrawal, to satisfy PECR requirements. Send logs for emails, push messages, and SMS are kept for only thirteen months. Withdrawing consent right away halts communications while preserving historical proof. A segmented database ensures suppression without delay, and consent logs are held in a distinct compliance archive. Send logs contain metadata only—subject, time, status—not full message content. The six-year post-withdrawal period mirrors the statute of limitations for regulatory inquiries. Quarterly audits check no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Monetary Transaction and Billing Records
Deposit, withdrawal, and wager histories are retained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised identifier. Chargeback disputes suspend the contested record until final outcome, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references remain valid only while your account is live and are deleted within thirty days of closure. Summarised, anonymised totals persist for financial reporting without any personal identifiers. All financial data is secured and isolated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and erase our own mapping. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever exist on our systems. We check token revocation daily and trigger incidents if deletion fails. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are recorded and verifiable. Aggregate reports never reveal individual transaction hashes.
Technical Infrastructure and Data Residency
All data sits in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone syncs every six hours. Backups are encrypted client-side and adhere to identical retention rules. We implement least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication integrates a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor confirms automated purge schedules. Any deviation generates a Severity 1 incident, reported to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, following the same deletion policies.
Management of Encryption Keys
Master keys are renewed every 90 days automatically inside an HSM. New keys are kept internal in plaintext. Rotated keys are stored for the data’s retention period plus 12 months for lawful forensic access. When a data category is purged, its key is destroyed inside the HSM, making any backups unrecoverable. We link each key to a single data partition, avoid reuse, and conduct quarterly witnessed key ceremonies logged immutably for five years. The offline archive of old keys requires dual control and is stored on write-once media in a fireproof safe. Annual recovery drills confirm forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.
Essential Definitions and Range of Personal Data
We take a broad view on what constitutes personal data. Direct identifiers—name, email, billing address, masked payment details—coexist with indirect signals like hashed IP addresses, device fingerprints, browser agents, and advertising tokens. Behavioural data includes session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can link back to a person when stitched together, so we handle them as personal. Our lawful bases are contractual necessity, legitimate interest for fraud prevention, and explicit consent for game-related marketing. Full card numbers get tokenised before storage. We never collect special category data. Encryption and access controls apply uniformly, and retention rules extend across live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.