Information Retention Policy for Wanted Dead Or a Wild Slot Game in UK

Playing wanted dead or a wild no deposit bonus Slot means handing over personal data. This document sets forth exactly how long we retain it, the rationale, and what technical protections support 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 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 is applied. Full card numbers never touch our systems—only tokenised aliases—and every byte is protected. Independent auditors verify 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 become effective. Subject access and deletion requests are handled within statutory deadlines.

Core Definitions and Scope of Personal Data

We cast a wide net 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 includes 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 starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.

User Account and Identity Verification Data

Core identity profiles—official ID scans, residence proof, selfie biometric matches—are retained for five years after your last activity or account closure, whichever comes later. This includes contractual limitation periods and AML obligations. We retrieve only the key information: document ID, expiration date, citizenship. The high-resolution image gets deleted right after extraction. Once 5 years pass, all raw data is erased, but a cryptographic hash of the verification outcome remains for two more years inside an logging system. Identity data sits encrypted in storage with AES-256-GCM, isolated from analytics, and every data access is tracked for three years. Optional fields like birth location are discarded at verification time to shrink the data volume. Yearly audits verify correctness and automatically remove outdated records.

Uploading Documents and Biometric Processing

Submit an ID through our safe portal and automated validation finishes within 90 seconds. We extract the ID number, expiration date, nationality, and a trust score, then destroy the original image right away—it never reaches storage. The initial file stays in ibisworld.com an memory buffer and vanishes after processing. A reduced, stamped thumbnail is produced for auditing purposes and stored only for the ID lifecycle. That preview lives in a write-once storage with tight controls and is never shown to support staff. Extracted fields are encoded and kept for the five-year plus two-year hash timeframe. All handling runs on servers in the UK with ISO 27001, and every small image access is stored unchangeably.

Biometric Information Details

Liveness checks record a brief video feed completely in memory. Images are processed and deleted within a few milliseconds. Only a data vector of face features survives. This data set contains no image data and cannot be turned back into a face. It is kept for the time of identity verification and is purged irrevocably upon closure of account or after 5 years. The data set sits in a dedicated HSM with auto-expiry and is never exported. Login comparisons happen inside the HSM’s safe environment without disclosing the unprocessed data. The data set is associated with a pseudonymous identifier separated from advertising profiles, which makes reidentification very hard. Even system admins cannot see or recreate face characteristics from the stored vector.

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 reference. 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 checked by auditors. Tokenised card references stay valid only while your account is open and are wiped within thirty days of termination. Aggregated, anonymised totals persist for financial reporting without any personal information. All financial data is secured and quarantined from marketing systems.

Tokenised Payment Instruments and Processor References

Payment gateways produce vaulted tokens that map your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and erase our own reference. The only evidence left behind is an anonymised transaction hash used in aggregate statements, themselves removed after seven years. No usable credentials ever exist on our systems. We monitor token revocation daily and trigger incidents if deletion fails. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and checked. Aggregate reports never expose individual transaction hashes.

Responsible Gambling and Self-Exclusion Registers

Stake limits, session reminders, and timeout settings are kept for your account’s whole period and never removed while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a dedicated exclusion register kept permanently under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never employed for analytics. Access is restricted to educated compliance staff, and all lookups are recorded for three years. The register contains only identity blocks—no banking or gameplay records. We examine it annually to rectify errors and remove deceased individuals. Otherwise, it is kept everlasting. This retention is mandatory and excluded from deletion requests.

Session Awareness and Gaming Duration Enforcement

Reality check counters use temporary session counters that reset every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and automatically reactivates when you come back, even after a long break. Altering the interval mid-session sets the new value instantly for the next reminder. These settings are purged only upon verified 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 accuracy. All timer configurations are verifiable through the same three-year access log standard. We do not profile or advertise based on these settings.

Gameplay Session and Behavioural 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 persist for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics get 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 comply with technical standards
• Feature trigger heatmaps: 12 months, then merged into global model
• Error and crash diagnostic logs: 90 days, then cycled out

Marketing Consent and Message Logs

We keep your consent log—time-stamped, IP-marked, and method-recorded—for the entirety of our partnership plus six years after withdrawal, to satisfy PECR requirements. Dispatch records for e-mails, push alerts, and SMS are kept for only thirteen months. Revoking consent immediately halts communications while retaining historical proof. A partitioned database ensures suppression without latency, and consent logs are stored in a dedicated compliance archive. Delivery logs include metadata only—heading, time stamp, state—not full message content. The six-year post-withdrawal period matches the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.

Access Request and Erasure Workflows

Upon receiving an SAR, we produce a structured 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 batched erasure of all personal data not subject to legal hold. We produce a https://data-api.marketindex.com.au/api/v1/announcements/XASX:SGR:2A1478883/pdf/inline/notice-of-annual-general-meeting 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 recorded immutably for five years.

Technology Framework 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 follow 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 uses 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, reported to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, subject to the same deletion policies.

Key Lifecycle Administration

Master keys rotate every 90 days automatically inside an HSM. New keys are not extracted 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 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 confirm forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.

Policy Review and Breach Notification 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 published 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, submit with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We hold a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.

Document Versioning and Revision History

We preserve 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 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.