Playing Wanted Dead Or a Wild Slot means submitting personal data. This document details exactly how long we retain it, the reasons, and what technical protections underpin each category—all based on UK GDPR, the Data Protection Act 2018, and PCI DSS. We process identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its specific retention clock. Identity records are kept for five years after account closure. Financial logs remain for seven, satisfying 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 secured. Independent auditors check our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log tracks every edit, and we offer you 30 days’ notice before material changes become effective. Subject access and deletion requests are handled within statutory deadlines.
Essential Definitions and Extent of Personal Data
We take a broad view on what counts 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 regard 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 begins counting from the last activity or transaction date, spelled out below. We revisit definitions every six months to keep pace with regulatory guidance.
Registration Account and ID Verification Data
Core identity profiles—official ID scans, proof of address, biometric selfie verifications—are retained for a five-year period after your last activity or account termination, whichever occurs later. This covers statutory limitation periods and anti-money laundering duties. We retrieve only the key information: document number, validity, citizenship. The high-resolution image gets shredded upon extraction. Once 5 years pass, all original data is purged, but a encrypted hash of the verification result lives on for another two years inside an audit log. Identity data sits encrypted at rest with AES-256-GCM, isolated from analytics, and every retrieval is tracked for three years. Optional fields like place of birth are discarded at verification time to minimize the data footprint. Yearly reviews confirm precision and automatically remove expired entries.
Uploading Documents and Biometric Data Processing
Submit an ID through our protected portal and automatic verification completes within a minute and a half. We pull the ID number, validity, country of citizenship, and a reliability score, then shred the original image instantly—it never reaches storage. The source file stays in an in-memory buffer and disappears after processing. A compressed, stamped preview is created for compliance purposes and kept only for the identity lifecycle. That small image lives in a write-once vault with tight controls and is never exposed to support staff. Extracted fields are secured and stored for the 5-year-plus-2-year hash period. All processing runs on servers in the UK with ISO 27001, and every thumbnail access is stored unchangeably.
Biometric Information Details
Live detection checks capture a brief video feed solely in memory. Video frames are analysed and removed within a few milliseconds. Only a numerical vector of face features survives. This vector lacks any image data and cannot be turned back into a picture. It is kept for the entire identity verification process and is permanently deleted upon account closure or after 5 years. The data set sits in a dedicated HSM with auto-expiry and is never sent out. Login comparisons happen inside the HSM’s secure enclave without disclosing the unprocessed data. The vector is linked to a pseudonym unlinked from marketing profiles, which makes re-identifying highly challenging. Even system admins cannot view or rebuild facial attributes from the kept numerical representation.
Gaming Session and Behavioral Analytics Data
All spins on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision https://wanteddeadorwild.uk/. We store these raw logs for twenty-four months, then compact them into an anonymous statistical digest employed for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—remain 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 flows into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then aggregated aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Financial Transaction and Billing Records
Deposit, withdrawal, and wager histories are retained for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised reference. Chargeback disputes freeze the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs checked by auditors. Tokenised card references are valid only while your account is open and are wiped within thirty days of closure. Combined, anonymised totals endure for financial reporting without any personal identifiers. All financial data is secured and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that associate your card to a non-sensitive identifier. We hold them for the account lifetime plus a thirty-day grace period, then issue deletion commands to the processor and erase our own reference. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever exist on our systems. We check token revocation daily and trigger incidents if deletion fails. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are recorded and verifiable. Aggregate reports never expose individual transaction hashes.
Safe Gambling and Voluntary Exclusion Registers
Betting limits, time checks, and timeout settings are stored for your account’s entire duration and never deleted while it remains active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specific exclusion register held without time limit under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never utilized for analytics. Access is restricted to educated compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no financial or gameplay records. We check it annually to correct errors and remove deceased individuals. Apart from that, it stays everlasting. This retention is mandatory and exempt from deletion requests.
Reality Check and Session Limit Enforcement
Reality check timers use temporary session counters that clear every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is stored persistently and routinely reactivates when you come back, even after a long break. Altering the interval mid-session sets the new value right away for the next reminder. These settings are purged only upon verified account deletion. Session timer data resides in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are verifiable through the same three-year access log standard. We do not categorize or promote based on these settings.
Data Subject Access Request and Deletion Workflows
Upon receiving an SAR, we compile a structured JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, provided via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We produce a confirmation report detailing erased versus retained categories and their justifications. This report is retained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Marketing Approval and Correspondence Records
We store your consent log—timestamped, IP-marked, and method-recorded—for the duration of our relationship plus six years after cancellation, to meet PECR obligations. Dispatch records for emails, push alerts, and SMS are kept for only thirteen months. Revoking consent immediately suppresses communications while preserving historical proof. A segmented database ensures suppression without delay, and consent logs are kept in a dedicated compliance archive. Send logs include metadata only—subject, time stamp, status—not full message text. The six-year post-withdrawal window mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents initiate mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Technology Framework and Data Residency
All data resides in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK. A hot disaster recovery site in a separate UK zone updates every six hours. Backups are encrypted client-side and maintain identical retention rules. We enforce least privilege with hardware MFA for administrators, logging 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 verifies automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.
Key Lifecycle Administration
Master keys change every 90 days automatically inside an HSM. New keys are kept internal in plaintext. Rotated keys are archived 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, never 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 guarantee forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.
Policy Evaluation and Breach Notification Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are documented with DPO, CISO, and legal counsel. A public summary is posted in our privacy centre, minus confidential details. Material changes are communicated 30 days ahead. Minor edits are silently recorded. If a breach occurs affecting data under this policy, we notify affected individuals within 72 hours if high risk, submit 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 test misconfigurations and ransomware to test our response.
Policy Versioning and Update Log
We maintain a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log outlines 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 access the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.
