Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we store it, the rationale, and what technical protections support each category—all based on UK GDPR, the Data Protection Act 2018, and PCI DSS. We handle identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its unique retention clock. Identity records stick around for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors review our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log documents every edit, and we provide you 30 days’ notice before material changes are implemented. Subject access and deletion requests are processed within statutory deadlines.
Marketing Approval and Message Logs
We maintain your consent log—timestamped, IP-marked, and with capture method—for the life of our association plus six years after revocation, to meet PECR requirements. Send logs for electronic messages, push notifications, and SMS are held for only thirteen months. Cancelling consent immediately halts communications while preserving historical proof. A divided database ensures suppression without latency, and consent logs are kept in a separate compliance archive. Delivery logs hold metadata only—heading, time, status—not full message text. The six-year post-withdrawal window mirrors the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Policy Assessment and Breach Notification Protocols
We review 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 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 issue a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Versioning and Revision History
We maintain 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 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.
Financial Transaction and Settlement Records
Deposit, withdrawal, and wager logs are retained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes freeze the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is open and are erased within thirty days of termination. Aggregated, anonymised totals remain for financial reporting without any personal details. All financial data is encrypted and separated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that map your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and erase our own link. The only remnant left behind is an anonymised transaction hash used in aggregate statements, themselves deleted after seven years. No usable credentials ever sit on our systems. We track token revocation daily and raise incidents if deletion fails. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and checked. Aggregate reports never reveal individual transaction hashes.
SAR and Deletion Processes
Upon receiving an SAR, we compile a structured JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, sent via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We create a confirmation report detailing 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.
Technology Framework and Data Residency
All data sits in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and maintain identical retention rules. We apply 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 triggers a Severity 1 incident, notified 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 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 assign 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 demands dual control and is stored on write-once media in a fireproof safe. Annual recovery drills ensure forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.
Account Registration and Verification of Identity Data
Core identity profiles—official ID scans, residence proof, biometric selfie matches—are kept for five years after your last activity or closure of account, whichever is later. This includes statutory limitation periods and anti-money laundering duties. We extract only the key information: document ID, validity, nationality. The full-resolution image gets deleted upon extraction. Once 5 years pass, all original data is erased, but a encrypted hash of the verification outcome lives on for an additional two years inside an logging system. Identity data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every access is recorded for a three-year period. Unnecessary fields like birth location are discarded at the time of verification to shrink the data size. Yearly audits ensure precision and proactively delete outdated records.
File Upload and Biometric Processing
Submit an ID through our safe portal and automated validation completes within ninety seconds. We extract the ID number, validity, nationality, and a trust score, then destroy the high-resolution image right away—it never reaches storage. The initial file stays in an in-memory buffer and disappears after processing. A compacted, watermarked small image is produced for compliance purposes and retained only for the ID lifecycle. That preview lives in a write-once vault with strict controls and is never shown to client support. Extracted fields are encoded and kept for the 5-year-plus-2-year hash period. All operations runs on servers in the UK with ISO 27001, and every thumbnail access is logged permanently.
Biometric Information Details
Liveness checks collect a quick video solely in memory. Images are analyzed and removed within milliseconds. Only a data vector of face features persists. This vector has no image data and cannot be reconstructed into a facial image. It is kept for the duration of identity verification and is irreversibly removed upon account closure or after 5 years. The numerical representation sits in a dedicated HSM with self-expiry and is never exported. Authentication checks happen inside the HSM’s safe environment without exposing the original vector. The data set is associated with a pseudonymous identifier separated from marketing data, which makes re-identification extremely difficult. Even IT admins are unable to view or rebuild facial features from the stored vector.
Core Definitions and Range of Personal Data
We adopt a comprehensive approach 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 encompasses session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again 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 span live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to remain compliant with regulatory guidance.
Gaming Session and Behavioral Analytics Data
Every spin on Wanted Dead Or a Wild logs 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 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then erased
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then combined into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Responsible Gambling and Self-Exclusion Registers
Stake limits, time checks, and timeout settings are saved for your account’s entire duration and never purged while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register kept without time limit under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never employed for analytics. Permission is confined to trained compliance staff, and all queries are tracked for three years. The register holds only identity blocks—no monetary or gameplay records. We review it annually to rectify errors and remove deceased individuals. Otherwise, it is kept permanent. This retention is obligatory and excluded from deletion requests.
Time Check and Session Limit Enforcement
Reality check timers use temporary session counters that reset every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and automatically reactivates when you return, even after a long break. Altering the interval mid-session sets the new value right away 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 profile or promote based on these settings.
