Playing Wanted Dead Or a Wild Slot game means handing over personal data wanteddeadorwild.uk. This document lays out exactly how long we keep it, the reasons, and what technical protections support each category—all based on 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 own retention clock. Identity records are retained for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors check our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log documents every edit, and we give you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.
Core Definitions and Extent of Personal Data
We adopt a comprehensive approach on what qualifies as personal data. Direct identifiers—name, email, billing address, masked payment details—are accompanied by 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 cover live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.
Consent for Marketing and Message Logs
We keep your consent document—with time stamp, IP-stamped, and method-recorded—for the life of our association plus six years after cancellation, to comply with PECR obligations. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Cancelling consent instantly blocks communications while keeping historical proof. A partitioned database ensures suppression without latency, and consent logs are stored in a separate compliance archive. Delivery logs include metadata only—subject, timestamp, condition—not full message content. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents initiate mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Registration Account and Identity Verification Data
Core identity profiles—official ID scans, proof of address, biometric selfie verifications—are retained for 5 years after your final session or closure of account, whichever occurs later. This covers contractual limitation periods and AML obligations. We obtain only the essentials: document number, validity, citizenship. The high-resolution image gets shredded right after extraction. Once 5 years pass, all original data is purged, but a cryptographic hash of the verification result persists for another two years inside an logging system. Personal identity information sits stored encrypted with AES-256-GCM, isolated from analytics, and every data access is logged for three years. Optional fields like birthplace are discarded at verification stage to reduce the data footprint. Yearly reviews verify correctness and actively purge expired entries.
File Upload and Biometric Data Processing
Submit an ID through our secure portal and automated checking finishes within ninety seconds. We pull the document number, expiration date, citizenship, and a confidence score, then destroy the original image right away—it never reaches storage. The initial file stays in an in-memory buffer and is removed after processing. A compacted, stamped small image is created for auditing purposes and kept only for the identity lifecycle. That preview lives in a write-once vault with strict controls and is never exposed to customer support. Retrieved data are encoded and saved for the 5-year-plus-2-year hash period. All processing runs on UK-based ISO 27001 servers, and every preview retrieval is logged permanently.
Specifics of Biometric Data
Liveness checks record a short video stream completely in memory. Images are processed and discarded within a few milliseconds. Only a mathematical vector of facial points persists. This vector has no image data and cannot be turned back into a facial image. It is kept for the entire identity verification process and is permanently deleted upon closure of account or after 5 years. The vector sits in a hardware security module with self-expiry and is never sent out. Login verifications happen inside the HSM’s secure enclave without exposing the raw vector. The vector is associated with a pseudonym disconnected from advertising profiles, which makes re-identifying extremely difficult. Even system administrators are unable to view or recreate facial features from the stored vector.
Data Subject Access Request and Deletion Workflows
Upon receiving an SAR, we generate a organized JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, sent via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We create a confirmation report specifying erased versus retained categories and their justifications. This report is kept as auditable proof for as long as the longest surviving data category. All requests are logged immutably for five years.
Controlled Gambling and Self-Exclusion Registers
Betting limits, session reminders, and timeout settings are kept for your account’s whole period and never purged while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specialized exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never used for analytics. Access is confined to educated compliance staff, and all queries are recorded for three years. The register stores only identity blocks—no banking or gameplay records. We examine it annually to correct errors and remove deceased individuals. Otherwise, it remains permanent. This retention is required and exempt from deletion requests.
Time Check and Session Limit Enforcement
Reality check counters use short-lived session counters that clear every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and instantly reactivates when you visit again, even after a long break. Modifying the interval mid-session sets the new value immediately for the next reminder. These settings are removed only upon validated account deletion. Session timer data lies in a specific, 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 never categorize or market based on these settings.
Gameplay Session and Behavioural Analytics Data
All spins on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then condense them into an anonymous statistical digest used 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 remain for 12 months before merging into a global model. RNG seed audit trails have 36 months. Error diagnostics get 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 anonymized aggregation
- Session behavioural profiles: 24 months from last session, then removed
- 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
Monetary Transaction and Payment 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 collect only the BIN, last four digits, and a tokenised alias. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is open and are erased within thirty days of closing. Combined, anonymised totals remain for financial reporting without any personal identifiers. All financial data is coded and isolated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that map your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace window, then transmit deletion commands to the processor and wipe our own link. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever sit on our systems. We track token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and checked. Aggregate reports never expose individual transaction hashes.
Infrastructure Setup 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 synchronizes every six hours. Backups are encrypted client-side and adhere to identical retention rules. We apply least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication combines a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor validates automated purge schedules. Any deviation generates a Severity 1 incident, reported to our DPO within four hours. We also operate an air-gapped backup rotated weekly, subject to the same deletion policies.
Encryption Key Lifecycle Management
Master keys change every 90 days automatically inside an HSM. New keys are kept internal in plaintext. Rotated keys are retained for the data’s retention period plus 12 months for lawful forensic access. When a data category is purged, its key is removed inside the HSM, making any backups unrecoverable. We bind each key to a single data partition, do not 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.
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 displayed in our privacy centre, minus confidential details. Material changes are sent 30 days ahead. Minor edits are silently recorded. If a breach occurs affecting data under this policy, we alert affected individuals within 72 hours if high risk, report with the ICO, and post a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Policy Versioning and Update Log
We keep a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log details 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 transmitted 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 check 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 shows our commitment to accountable data governance.