Untitled
أغسطس 27, 2026
Playing Wanted Dead Or a Wild Slot means providing personal data https://wanteddeadorwild.uk/. This document details exactly how long we keep 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 own retention clock. Identity records are kept for five years after account closure. Financial logs remain for seven, matching 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 protected. Independent auditors review our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are managed within statutory deadlines.
We adopt a comprehensive approach on what qualifies 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 identify again 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 begins counting from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.
Main identity data—scans of government IDs, proof of address, biometric selfie matches—are held for 5 years after your final session or account closure, whichever occurs later. This includes contractual limitation periods and anti-money laundering responsibilities. We extract only the necessary details: document ID, validity, country of citizenship. The full-resolution image gets destroyed right after extraction. Once five years pass, all raw data is erased, but a cryptographic hash of the verification data remains 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 logged for three years. Non-essential fields like birth location are deleted at verification time to reduce the data footprint. Yearly audits verify precision and proactively delete expired data.
Provide an ID through our secure portal and automated checking wraps up within ninety seconds. We extract the document ID, expiry, citizenship, and a trust score, then shred the original image immediately—it is never stored on disk. The source file stays in an memory buffer and disappears after analysis. A reduced, watermarked thumbnail is produced for audit purposes and stored only for the ID lifecycle. That small image lives in a immutable vault with strict controls and is never shared to client support. Collected information are secured and stored for the 5-year-plus-2-year hash period. All handling runs on servers in the UK with ISO 27001, and every preview retrieval is recorded immutably.
Liveness checks collect a short video stream solely in memory. Images are processed and removed within milliseconds of time. Only a numerical vector of face features remains. This numerical representation has no image data and cannot be turned back into a facial image. It remains for the entire identity verification process and is permanently deleted upon account closure or after a five-year period. The numerical representation sits in a dedicated HSM with self-expiry and is never sent out. Login comparisons happen inside the HSM’s secure enclave without disclosing the original vector. The vector is bound to a pseudonym separated from marketing profiles, which makes re-identification very hard. Even system administrators cannot see or reconstruct facial attributes from the kept numerical representation.
Each spin 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 compact them into an anonymous statistical digest utilized 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 persist for 12 months before merging into a global model. RNG seed audit trails have 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.
Deposit, withdrawal, and wager records are retained 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 identifier. Chargeback disputes halt the contested record until final outcome, after which the seven-year clock continues. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is open and are wiped within thirty days of closure. Combined, anonymised totals endure for financial reporting without any personal identifiers. All financial data is encrypted and separated from marketing systems.
Payment gateways produce vaulted tokens that associate your card to a non-sensitive identifier. We hold them for the account lifetime plus a thirty-day grace period, 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 deleted after seven years. No usable credentials ever reside on our systems. We track token revocation daily and initiate incidents if deletion fails. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation confirms authenticity, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and auditable. Aggregate reports never disclose individual transaction hashes.
When a subject access request arrives, we produce 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, provided via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We create 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.
We maintain your consent record—timestamped, with IP address, and method-recorded—for the entirety of our association plus six years after revocation, to satisfy PECR requirements. Send logs for e-mails, push notifications, and SMS are retained for only thirteen months. Revoking consent right away blocks communications while retaining historical proof. A segmented database guarantees suppression without delay, and consent logs are kept in a distinct compliance archive. Dispatch records hold metadata only—subject, time, status—not full message text. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit consents.
Stake limits, reality checks, and timeout settings are stored for your account’s entire duration and never purged while it stays active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a specific exclusion register held without time limit under UKGC licence requirements. The register is encrypted separately, checked only at login or registration, and never used for analytics. Permission is restricted to trained compliance staff, and all lookups are logged for three years. The register holds only identity blocks—no banking or gameplay records. We check it annually to correct errors and remove deceased individuals. Apart from that, it remains permanent. This retention is required and excluded from deletion requests.
Reality check counters 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 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 removed only upon validated account deletion. Session timer data lies in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are checkable through the same three-year access log standard. We at no time analyze or advertise based on these settings.
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 updates every six hours. Backups are encrypted client-side and follow 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 integrates a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor confirms automated purge schedules. Any deviation raises a Severity 1 incident, alerted to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, under the same deletion policies.
Master keys are renewed every 90 days automatically inside an HSM. New keys are kept internal 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 deleted inside the HSM, making any backups unrecoverable. We assign each key to a single data partition, do not 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 exits the HSM boundary.
We assess 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 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 inform 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 adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
We maintain 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 check 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 reflects our commitment to accountable data governance.
متاح جميع الاوقات
خدمة دعم لجميع المحافظات
