Playing wanted dead or a wild Slot means submitting personal data. This document details exactly how long we keep it, the rationale, and what technical protections support each category—all built around 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 own retention clock. Identity records stick around for five years after account closure. Financial logs remain for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation is applied. Full card numbers never touch our systems—only tokenised aliases—and every byte is protected. Independent auditors check our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are processed within statutory deadlines.
Responsible Gambling and Self-Exclusion Registers
Betting limits, session reminders, and timeout settings are stored for your account’s whole period and never deleted while it remains active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register kept indefinitely under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never employed for analytics. Access is confined to qualified compliance staff, and all searches are recorded for three years. The register holds only identity blocks—no banking or gameplay records. We check it annually to rectify errors and remove deceased individuals. If not, it remains everlasting. This retention is obligatory and exempt from deletion requests.
Reality Check and Session Limit Enforcement
Reality check timers use temporary session counters that restart every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently https://www.annualreports.com/HostedData/AnnualReportArchive/b/betsson-ab_2007.pdf and routinely reactivates when you return, even after a long break. Changing the interval mid-session sets the new value instantly for the next reminder. These settings are purged 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 accuracy. All timer configurations are checkable through the same three-year access log standard. We do not analyze or market based on these settings.
Session Gameplay and Behavioral Analytics Data
Every spin on Wanted Dead Or a Wild records 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—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 anonymised aggregation
- Session behavioural profiles: 24 months from last session, then removed
- 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 removed
Monetary Transaction and Settlement Records
Funding, withdrawal, and wager records are maintained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised identifier. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock continues. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is live and are deleted within thirty days of closing. Summarised, anonymised totals endure for financial reporting without any personal details. All financial data is secured and quarantined from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways generate vaulted tokens that link your card to a non-sensitive alias. We store them for the account lifetime plus a thirty-day grace period, then issue deletion commands to the processor and clear our own link. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves removed after seven years. No usable credentials ever exist on our systems. We track token revocation daily and trigger incidents if deletion does not work. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are documented and checked. Aggregate reports never reveal individual transaction hashes.
Technical Infrastructure and Data Storage
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 synchronizes every six hours. Backups are encrypted client-side and adhere to identical retention rules. We enforce least privilege with hardware MFA for administrators, capturing 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 triggers a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under the same deletion policies.
Management of Encryption Keys
Master keys are renewed every 90 days automatically inside an HSM. New keys are not extracted in plaintext. Rotated keys are retained 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 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 needs 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 Evaluation and Incident Reporting Protocols
We assess 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 published 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 notify affected individuals within 72 hours if high risk, submit 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 update 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 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.
Fundamental Definitions and Extent of Personal Data
We adopt a comprehensive approach on what constitutes 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 covers 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 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 remain compliant with regulatory guidance.
User Account and ID Verification Data
Core identity profiles—official ID scans, proof of address, biometric selfie matches—are kept for five years after your last session or account termination, whichever comes later. This includes statutory limitation periods and anti-money laundering duties. We extract only the necessary details: ID number, expiry, nationality. The full-resolution image gets destroyed immediately after extraction. Once five years pass, all source data is erased, but a hash of the verification outcome lives on for two more years inside an audit trail. Personal identity information sits stored encrypted with AES-256-GCM, stored away from analytics, and every retrieval is tracked for three years. Optional fields like birth location are deleted at the time of verification to minimize the data volume. Yearly reviews verify accuracy and actively purge expired entries.
Uploading Documents and Biometric Handling
Upload an ID through our secure portal and automatic verification wraps up within a minute and a half. We pull the ID number, validity, country of citizenship, and a trust score, then destroy the high-resolution image immediately—it is never stored on disk. The source file stays in an temporary memory and is removed after analysis. A reduced, marked small image is created for compliance purposes and kept only for the identity verification period. That thumbnail lives in a immutable vault with tight controls and is never shared to customer support. Retrieved data are secured and kept for the five-year plus two-year hash timeframe. All processing runs on ISO 27001 certified UK servers, and every thumbnail access is recorded immutably.
Specifics of Biometric Data
Liveness checks collect a brief video feed entirely in memory. Images are processed and deleted within a few milliseconds. Only a data vector of facial points survives. This numerical representation lacks any image data and cannot be reverse-engineered into a facial image. It stays for the time of identity verification and is purged irrevocably pitchbook.com upon account termination or after 5 years. The data set sits in a specialized HSM with self-expiry and is never transferred. Login comparisons happen inside the HSM’s secure enclave without exposing the raw vector. The data set is bound to a pseudonym unlinked from advertising profiles, which makes reidentification extremely difficult. Even system administrators are unable to view or recreate facial features from the saved data.
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, 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 proceed sequentially: 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 recorded immutably for five years.
Consent for Marketing and Communication Logs
We maintain your consent document—time-stamped, with IP address, and method-captured—for the duration of our relationship plus six years after cancellation, to meet PECR rules. Dispatch records for emails, push notifications, and SMS are retained for only thirteen months. Withdrawing consent instantly suppresses communications while retaining historical proof. A partitioned database guarantees suppression without delay, and consent logs are stored in a dedicated compliance archive. Send logs contain metadata only—topic, time stamp, state—not full message content. The six-year post-withdrawal window mirrors the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents initiate mailings. We never tailor offers with gameplay or financial data beyond explicit consents.