Playing Wanted Dead Or a Wild Slot means submitting personal data. This document sets forth exactly how long we store it, the reasons, and what technical protections sit behind 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 unique retention clock. Identity records are retained 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 reach our systems—only tokenised aliases—and every byte is protected. Independent auditors review our automated deletion routines, and any schedule slip initiates 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 managed within statutory deadlines.
Core Definitions and Extent of Personal Data
We cast a wide net on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—sit alongside 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 re-identify 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 span 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 keep pace with regulatory guidance.
Responsible Gambling and Self-Exclusion Registers
Betting limits, session reminders, and timeout settings are kept for your account’s entire duration and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are placed into a specific exclusion register held indefinitely under UKGC licence requirements. The register is coded separately, accessed only at login wanted dead or a wild slot no deposit registration, and never utilized for analytics. Entry is limited to trained compliance staff, and all queries are tracked for three years. The register contains only identity blocks—no financial or gameplay records. We examine it annually to fix errors and remove deceased individuals. If not, it remains indefinite. This retention is mandatory and exempt from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check clocks use transient session counters that reset every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and automatically reactivates when you visit again, even after a long break. Altering the interval mid-session introduces the new value instantly 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 precision. All timer configurations are verifiable through the same three-year access log standard. We never profile or promote based on these settings.
User Account and Verification of Identity Data
Core identity profiles—official ID scans, residence proof, biometric selfie verifications—are kept for five years after your last session or closure of account, whichever occurs later. This includes statutory limitation periods and AML obligations. We obtain only the essentials: ID number, validity, citizenship. The high-resolution image gets destroyed right after extraction. Once 5 years pass, all source data is purged, but a encrypted hash of the verification outcome lives on for another two years inside an audit log. Personal identity information sits encrypted at rest with AES-256-GCM, kept separate from analytics, and every data access is logged for 3 years. Non-essential fields like birth location are removed at verification stage to shrink the data volume. Yearly reviews confirm correctness and proactively delete expired entries.
Document Upload and Biometric Handling
Upload an ID through our safe portal and automated validation finishes within 90 seconds. We extract the document number, expiration date, country of citizenship, and a trust score, then delete the original image right away—it is never stored on disk. The initial file stays in an memory buffer and is removed after processing. A compressed, watermarked small image is produced for compliance purposes and stored only for the ID lifecycle. That preview lives in a immutable vault with strict controls and is never shared to client support. Retrieved data are encoded and kept for the five-year plus two-year hash timeframe. All operations runs on servers in the UK with ISO 27001, and every small image access is recorded immutably.
Specifics of Biometric Data
Liveness checks record a quick video completely in memory. Video frames are analysed and removed within a few milliseconds. Only a data vector of facial points persists. This numerical representation contains no image data and cannot be reverse-engineered into a facial image. It is kept for the time of identity verification and is purged irrevocably upon account termination or after 5 years. The numerical representation sits in a dedicated HSM with auto-expiry and is never transferred. Login verifications happen inside the HSM’s safe environment without exposing the original vector. The data set is associated with a pseudonym separated from advertising profiles, which makes reidentification very hard. Even IT admins cannot view or rebuild facial attributes from the kept numerical representation.
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, sent 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 generate 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 documented immutably for five years.
Gaming Session and Behavioral Analytics Data
Each spin 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—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 feeds 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 combined into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Financial Transaction and Settlement Records
Deposit, withdrawal, and wager histories are maintained 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 reference. Chargeback disputes suspend the contested record until final outcome, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is open and are deleted within thirty days of termination. Summarised, anonymised totals remain for financial reporting without any personal identifiers. All financial data is encrypted and isolated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and clear our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever reside on our systems. We check token revocation daily and raise incidents if deletion is unsuccessful. Tokens are tied to our merchant code and cannot be used in other contexts. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are documented and verifiable. Aggregate reports never expose individual transaction hashes.
Consent for Marketing and Correspondence Records
We keep your consent document—timestamped, IP-stamped, and method-captured—for the life of our association plus six years after cancellation, to meet PECR rules. Dispatch records for emails, push notifications, and SMS are held for only thirteen months. Withdrawing consent right away suppresses communications while retaining historical proof. A segmented database provides suppression without delay, and consent logs are kept in a separate compliance archive. Send logs contain metadata only—heading, timestamp, 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 initiate mailings. We never personalise offers with gameplay or financial data beyond explicit consents.
Technical Infrastructure and Data Location
All data sits 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 adhere to 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 occur 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 operate an air-gapped backup rotated weekly, under the same deletion policies.
Encryption Key Lifecycle Management
Master keys change 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 ensure forensic decryption works when needed. No plaintext key material ever leaves the HSM boundary.
Policy Assessment and Incident Reporting Protocols
We review this policy every six months or upon material change to the game or regulation. Reviews are minuted with tracxn.com DPO, CISO, and legal counsel. A public summary is posted 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, submit with the ICO, and post a transparency notice. Third-party processor breaches must follow the same protocol. We keep 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 Version Control and Change Log
We keep 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 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.