Playing Wanted Dead Or A Wild Slot User Reviews means submitting personal data. This document lays out exactly how long we retain it, why, and what technical protections underpin 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 unique retention clock. Identity records are retained for five years after account closure. Financial logs remain for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors review our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log tracks every edit, and we provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Fundamental 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 identify again a person when stitched together, so we treat 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.
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 keep these raw logs for twenty-four months, then condense them into an anonymous statistical digest utilized for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—stay 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 anonymized aggregation
- Session behavioural profiles: 24 months from last session, then erased
- RNG seed audit trails: 36 months to meet technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Controlled Gambling and Voluntary Exclusion Registers
Stake limits, reality checks, and timeout settings are saved for your account’s lifetime and never removed while it is active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specialized exclusion register kept without time limit under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never used for analytics. Entry is restricted to educated compliance staff, and all lookups are tracked for three years. The register contains only identity blocks—no monetary or gameplay records. We examine it annually to fix errors and remove deceased individuals. Apart from that, it is kept permanent. This retention is obligatory and free from deletion requests.
Reality Check and Play Time Restriction Enforcement
Reality check counters use temporary session counters that clear every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and instantly reactivates when you return, even after a long break. Modifying the interval mid-session introduces the new value right away for the next reminder. These settings are purged only upon validated account deletion. Session timer data sits in a specific, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are auditable through the same three-year access log standard. We at no time categorize or market based on these settings.
Registration Account and ID Verification Data
Core identity profiles—scans of government IDs, address verification, biometric selfie matches—are retained for 5 years after your last session or account closure, whichever comes later. This includes contractual limitation periods and AML obligations. We retrieve only the essentials: ID number, expiration date, nationality. The high-resolution image gets shredded immediately after extraction. Once the five-year period pass, all raw data is purged, but a cryptographic hash of the verification outcome persists for two more years inside an audit trail. Identification data sits encrypted at rest with AES-256-GCM, isolated from analytics, and every data access is recorded for a three-year period. Unnecessary fields like birth location are deleted at verification stage to minimize the data size. Annual reviews ensure correctness and automatically remove expired data.
File Upload and Biometric Processing
Upload an ID through our safe portal and automated checking completes within ninety seconds. We extract the document ID, expiration date, country of citizenship, and a trust score, then shred the high-resolution image immediately—it never touches disk. The original file stays in an memory buffer and vanishes after handling. A compressed, marked thumbnail is generated for auditing purposes and retained only for the ID lifecycle. That thumbnail lives in a write-once vault with rigorous controls and is never shared to customer support. Retrieved data are encrypted and saved for the five-year-plus-two hash window. All processing runs on servers in the UK with ISO 27001, and every preview retrieval is stored unchangeably.
Specifics of Biometric Data
Liveness checks capture a quick video entirely in memory. Images are analyzed and discarded within a few milliseconds. Only a mathematical vector of face features survives. This data set contains no image data and cannot be turned back into a facial image. It is kept for the duration of identity verification and is irreversibly removed upon account termination or after 5 years. The numerical representation sits in a specialized HSM with self-expiry and is never exported. Login comparisons happen inside the HSM’s safe environment without disclosing the raw vector. The data set is associated with a pseudonym unlinked from advertising profiles, which makes reidentification highly challenging. Even system administrators cannot view or reconstruct facial attributes from the stored vector.
Data Subject Access Request and Deletion Workflows
When a subject access request arrives, we generate a organized JSON/CSV export of all non-purged data within one month, prolongable 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 cascade: immediate account suppression and token revocation, then batched 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 kept as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Infrastructure Setup and Data Location
All data is stored in UK-based ISO 27001 Tier III+ data centres, with no replication outside the UK. A hot disaster recovery site in a separate UK zone syncs every six hours. Backups are encrypted client-side and maintain identical retention rules. We enforce 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 run quarterly, and an independent auditor validates automated purge schedules. Any deviation triggers a Severity 1 incident, alerted to our DPO within four hours. We also operate an air-gapped backup rotated weekly, subject to the same deletion policies.
Management of Encryption Keys
Master keys rotate every 90 days automatically inside an HSM. New keys are never exported 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 assign 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 confirm forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Consent for Marketing and Message Logs
We keep your consent document—timestamped, IP-marked, and method-captured—for the duration of our relationship plus six years after withdrawal, to satisfy PECR requirements. Send logs for emails, push messages, and SMS are held for only thirteen months. Cancelling consent right away suppresses communications while preserving historical proof. A divided database provides suppression without lag, and consent logs are held in a distinct compliance archive. Dispatch records include metadata only—subject, time, status—not full message body. The six-year post-withdrawal period mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Financial Transaction and Payment Records
Deposit, withdrawal, and wager records are maintained 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 reference. Chargeback disputes halt the contested record until final outcome, after which the seven-year clock continues. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs checked by auditors. Tokenised card references stay valid only while your account is active and are deleted within thirty days of closure. Combined, anonymised totals persist for financial reporting without any personal identifiers. All financial data is coded and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways produce vaulted tokens that map your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and wipe our own mapping. The only evidence left behind is an anonymised transaction hash used in aggregate reports, themselves purged after seven years. No usable credentials ever reside on our systems. We track token revocation daily and raise incidents if deletion fails. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and verifiable. Aggregate reports never expose individual transaction hashes.
Policy Review and Incident Reporting 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 posted 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, 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 update controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control and Change Log
We maintain 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 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 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.
Leave a reply