Playing Wanted Dead Or a Wild Slot means submitting personal data. This document lays out exactly how long we retain it, why, and what technical protections sit behind each category—all aligned with 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. Full card numbers never enter 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 documents every edit, and we provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.
Fundamental Definitions and Scope of Personal Data
We adopt a comprehensive approach on what constitutes 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 link back to 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 extend across live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We review definitions every six months to stay aligned with regulatory guidance.
Gameplay Session and Behavioural Analytics Data
All spins on Slot Wanted Dead Or A Wild Bonuses records 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 used 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 remain for 12 months before merging into a global model. RNG seed audit trails receive 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then erased
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Monetary Transaction and Payment Records
Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised identifier. Chargeback disputes suspend the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is active and are erased within thirty days of termination. Summarised, anonymised totals endure for financial reporting without any personal information. All financial data is coded and separated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways produce vaulted tokens that associate your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace window, then transmit deletion commands to the processor and erase 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 exist on our systems. We check token revocation daily and initiate incidents if deletion does not work. Tokens are tied to our merchant code and cannot be used elsewhere. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and auditable. Aggregate reports never reveal individual transaction hashes.
Access Request and Erasure Workflows
When an SAR lands, 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, provided via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then batched 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.
Controlled Gambling and Player Ban Registers
Betting limits, session reminders, and timeout settings are kept for your account’s whole period and never removed while it stays active. If you choose to ban yourself, your hashed identity and device fingerprints are placed into a specialized exclusion register maintained without time limit under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never employed for analytics. Access is limited to trained compliance staff, and all searches are recorded for three years. The register stores only identity blocks—no financial or gameplay records. We review it annually to fix errors and remove deceased individuals. Apart from that, it stays permanent. This retention is obligatory and excluded from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check timers use temporary session counters that https://tracxn.com/d/companies/maria-casino/__zz9WjSfqr80iOJ6ZXxCgvQUXPASPcb-mnyIzH4LBKd4 clear every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is stored persistently 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 deleted only upon verified account deletion. Session timer data resides 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 verifiable through the same three-year access log standard. We do not analyze or promote based on these settings.
User Account and Identity Verification Data
Core identity profiles—scans of government IDs, residence proof, biometric selfie matches—are kept for five years after your final session or account termination, whichever is later. This encompasses statutory limitation periods and anti-money laundering responsibilities. We obtain only the key information: ID number, expiry, citizenship. The original image gets shredded upon extraction. Once 5 years pass, all original data is erased, but a cryptographic hash of the verification data remains for an additional two years inside an audit log. Personal identity information sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every retrieval is recorded for 3 years. Unnecessary fields like birthplace are removed at verification stage to reduce the data size. Annual reviews verify precision and automatically remove expired data.
Uploading Documents and Biometric Handling
Submit an ID through our protected portal and automated validation finishes within a minute and a half. We retrieve the document ID, validity, country of citizenship, and a trust score, then destroy the high-resolution image immediately—it never touches disk. The source file stays in an memory buffer and disappears after processing. A compacted, stamped thumbnail is generated for audit purposes and kept only for the ID lifecycle. That small image lives in a write-once storage with strict controls and is never exposed to client support. Retrieved data are secured and kept for the 5-year-plus-2-year hash period. All operations runs on ISO 27001 certified UK servers, and every preview retrieval is logged permanently.
Biometric Information Details
Liveness checks record a brief video feed solely in memory. Video frames are processed and deleted within milliseconds of time. Only a numerical vector of facial landmarks persists. This numerical representation contains no image data and cannot be turned back into a picture. It is kept for the time of identity verification and is irreversibly removed upon closure of account or after 5 years. The numerical representation sits in a hardware security module with auto-expiry and is never transferred. Login verifications happen inside the HSM’s safe environment without exposing the original vector. The numerical representation is bound to a pseudonym disconnected from marketing data, which makes re-identification very hard. Even system administrators cannot see or reconstruct face characteristics from the kept numerical representation.
Consent for Marketing and Correspondence Records
We maintain your consent log—time-stamped, with IP address, and method-captured—for the duration of our relationship plus six years after cancellation, to meet PECR requirements. Send logs for electronic messages, push alerts, and SMS are retained for only thirteen months. Revoking consent immediately halts communications while keeping historical proof. A partitioned database ensures suppression without delay, and consent logs are stored in a dedicated compliance archive. Dispatch records contain metadata only—topic, time stamp, state—not full message body. The six-year post-withdrawal window mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents initiate mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.
Infrastructure Setup and Data Storage
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 follow 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 combines a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation raises a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.
Key Lifecycle Administration
Master keys are renewed every 90 days automatically inside an HSM. New keys are never exported 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 link 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 guarantee forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Policy Review and Incident Reporting Protocols
We review this policy every six months or upon material change to the game or regulation. Reviews are recorded with DPO, CISO, and legal counsel. A public summary is published 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, file 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 model misconfigurations and ransomware to test our response.
Policy Version Control and Update Log
We keep pitchbook.com a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log outlines 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 verify 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.
