Privacy Policy and Data Processing Architecture

The integration of user data within the digital casino ecosystem is governed by strict systemic protocols and cryptographic standards. The platform operates a zero-tolerance policy for unauthorized data extraction, utilizing automated systems to manage the ingestion, processing, and localized storage of all user-generated metrics. This documentation outlines the exact technical parameters and operational constraints governing the privacy architecture of the service.

1. Algorithmic Data Ingestion Parameters

Upon initialization of a session on the platform, the server infrastructure executes automated data collection protocols. This ingestion is divided into active inputs (data provided during the KYC onboarding phase) and passive inputs (telemetry data harvested during navigation and interaction with the RNG modules).

The system architecture parses incoming data into distinct, encrypted databases to ensure compartmentalization. The parameters for data collection include the following technical specifications:

Data Classification	Collection Methodology	Primary Purpose	Systemic Necessity
Demographic Indicators	Active Input (Registration API)	Age verification (18+ constraint)	Mandatory for compliance
Financial Ledger Data	Active Input (Cashier API)	Processing of fiat/crypto transactions	Mandatory for real money sessions
Hardware Telemetry	Passive Collection (Browser Header)	Anti-fraud algorithm calibration	Mandatory for security execution
Session Latency Logs	Passive Collection (Ping Requests)	Server load balancing	Operational optimization
Geolocation Coordinates	Passive Collection (IP Routing)	Jurisdictional restriction enforcement	Mandatory for compliance

2. Cryptographic Security Standards

The platform enforces multi-layered cryptographic barriers to secure the transit and storage of all parsed data. The primary defense mechanism relies on Transport Layer Security (TLS) 1.3, which establishes a secure tunnel between the client-side browser environment and the centralized hosting servers.

The specific security algorithms deployed across the network infrastructure include:

Transit Encryption: 256-bit Advanced Encryption Standard (AES) for all active data streams.
Password Hashing: SHA-256 cryptographic hashing algorithms with randomized localized salting.
Database Encryption: RSA-4096 asymmetric encryption for stored demographic and financial ledgers.
DDoS Mitigation: Automated traffic filtering capable of absorbing volumetric attacks up to 500 Gbps.

3. Data Retention and Purge Protocols

The digital infrastructure operates under strict retention timelines dictated by the regulatory frameworks of the Curaçao eGaming authority (License No. 1668/JAZ) and international Anti-Money Laundering (AML) directives. Data is not retained indefinitely; rather, it is subjected to automated purge protocols once the operational necessity expires.

Data Category	Retention Duration	Trigger for Deletion	Purge Execution Latency
Unverified Accounts	30 Days	Failure to complete KYC phase	< 24 Hours
Verified Financial Logs	60 Months (5 Years)	Account closure or inactivity	Automated at 60th month
Session Telemetry	90 Days	Storage optimization	Weekly batch processing
Customer Support API Logs	12 Months	Resolution of ticket	Automated at 12th month
Marketing Pixel Data	180 Days	Expiration of cookie identifier	Instant upon expiration

4. Third-Party API Integration and Data Sharing

The operational framework of the platform requires the integration of external APIs to execute specialized functions, such as financial processing and RNG auditing. Data shared with these third-party nodes is strictly limited to the absolute minimum required to execute the requested function.

The system enforces automated data masking. For example, when executing a transaction via a credit gateway, the platform does not transmit the user’s localized session history; it only transmits the encrypted payment token and the requested fiat value.

Payment Gateways: Receive encrypted transaction tokens and requested numerical values.
RNG Auditors (e.g., iTech Labs): Receive anonymized spin logs devoid of demographic identifiers.
SMS Verification APIs: Receive isolated telephonic numerical strings exclusively for OTP transmission.

5. Cookie Framework and Local Storage Executions

The platform utilizes localized storage matrices (cookies) installed within the user’s browser environment to sustain session continuity and optimize load latencies. These executable files are categorized by their systemic priority and lifespan.

Cookie Classification	Storage Execution Phase	Lifespan Parameter	User Opt-Out Capability
Authentication Token	Upon successful login query	24 Hours	Restricted (Mandatory)
Load Balancer Identifier	Upon initial server ping	Session duration	Restricted (Mandatory)
Language Preference	Upon UI selection	365 Days	Available via browser settings
Affiliate Tracker	Upon landing via external node	30 Days	Available via localized cache purge
Analytics Pixel	Post-registration phase	90 Days	Available via consent dashboard

By interfacing with the platform, the user environment automatically processes these data requests. Modifying browser parameters to block mandatory authentication tokens will result in a localized system loop, preventing access to the real money session architecture.