Playing Wanted Dead Or a Wild Slot means providing personal data. This document sets forth exactly how long we store it, the reasons, and what technical protections support each category—all aligned with 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never touch our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log records every edit, and we give you 30 days’ notice before material changes become effective. Subject access and deletion requests are processed within statutory deadlines.
Fundamental Definitions and Scope of Personal Data
We adopt a comprehensive approach on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—coexist with 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 re-identify 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 extend across 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.
Marketing Consent and Correspondence Records
We store your consent document—with time stamp, with IP address, and method-recorded—for the life of our relationship plus six years after withdrawal, to satisfy PECR requirements. Dispatch records for electronic messages, push messages, and SMS are held for only thirteen months. Cancelling consent right away halts communications while keeping historical proof. A segmented database ensures suppression without lag, and consent logs are stored in a separate compliance archive. Send logs include metadata only—heading, time stamp, condition—not full message body. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.
SAR and Deletion Processes
When an SAR lands, we produce a formatted 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 implement a cascade: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We generate a confirmation report outlining 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 logged immutably for five years.
Gaming Session and Behavioural Analytics Data
All tracxn.com spins on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We store these raw logs for twenty-four months, then compress 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 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 removed
Safe Gambling and Voluntary Exclusion Registers
Deposit limits, time checks, and timeout settings are kept for your account’s whole period and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never employed for analytics. Permission is restricted to trained compliance staff, and all queries are recorded for three years. The register contains only identity blocks—no monetary or gameplay records. We review it annually to fix errors and remove deceased individuals. If not, it remains indefinite. This retention is obligatory and exempt from deletion requests.
Reality Check and Play Time Restriction Enforcement
Reality check clocks use temporary session counters that clear every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved 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 deleted only upon validated account deletion. Session timer data sits in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are auditable through the same three-year access log standard. We do not categorize Wanted Dead Or A Wild Review Of advertise based on these settings.
Account Registration and Identity Verification Data
Main identity data—government ID scans, address verification, selfie biometric matches—are kept for five years after your last activity or account closure, whichever is later. This includes statutory limitation periods and anti-money laundering responsibilities. We extract only the essentials: document number, expiration date, nationality. The high-resolution image gets deleted right after extraction. Once five years pass, all source data is erased, but a cryptographic hash of the verification data persists for two more years inside an logging system. Personal identity information sits encrypted in storage with AES-256-GCM, isolated from analytics, and every data access is logged for 3 years. Unnecessary fields like place of birth are discarded at verification stage to minimize the data volume. Yearly audits ensure correctness and automatically remove expired data.
Document Upload and Biometric Handling
Submit an ID through our protected portal and automated validation finishes within ninety seconds. We pull the document ID, expiry, nationality, and a trust score, then shred the full-resolution image immediately—it is never stored on disk. The initial file stays in an memory buffer and is removed after analysis. A reduced, watermarked thumbnail is created for auditing purposes and retained only for the identity verification period. That small image lives in a immutable vault with rigorous controls and is never shown to support staff. Collected information are encoded and saved for the five-year plus two-year hash timeframe. All processing runs on servers in the UK with ISO 27001, and every preview retrieval is logged permanently.
Biometric Data Specifics
Live detection checks collect a brief video feed entirely in memory. Video frames are analysed and deleted within milliseconds of time. Only a data vector of face features survives. This data set lacks any image data and cannot be reconstructed into a facial image. It stays for the entire identity verification process and is permanently deleted upon account termination or after five years. The vector sits in a hardware security module with auto-expiry and is never exported. Login comparisons happen inside the HSM’s safe environment without disclosing the original vector. The vector is linked to a anonymous identifier disconnected from marketing profiles, which makes reidentification very hard. Even system administrators cannot view or rebuild facial attributes from the saved data.
Financial Transaction and Settlement Records
Deposit, withdrawal, and wager logs are kept 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 identifier. Chargeback disputes freeze the contested record until final settlement, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs checked by auditors. Tokenised card references are valid only while your account is open and are deleted within thirty days of closing. Combined, anonymised totals remain 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 link 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 mapping. The only trace left behind is an anonymised transaction hash used in aggregate statements, themselves deleted after seven years. No usable credentials ever exist on our systems. We monitor token revocation daily and initiate incidents if deletion fails. Tokens are tied to our merchant code and cannot be used elsewhere. Weekly reconciliation validates authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and verifiable. Aggregate reports never disclose individual transaction hashes.
Infrastructure Setup and Data Location
All data resides 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 updates 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 are conducted quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, alerted to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.
Management of Encryption Keys
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 removed inside the HSM, making any backups unrecoverable. We link each key to a single data partition, avoid reuse, and conduct quarterly witnessed key ceremonies logged immutably for five years. The offline archive of old keys needs 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.
Policy Assessment and Data Breach Protocols
We review 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, file with the ICO, and issue 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 simulate 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 communicated 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 access the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.