Casino / Mobile
Your account data, transaction records, and device activity on bluga99 are handled under this policy — written plainly so you know exactly what we collect, why we collect it, and what choices you have. This policy applies to all access where local law and eligible regions permit.
When you access bluga99 — whether to browse the live casino lobby, check a slot session, or review a past DANA deposit — certain data is generated. This policy explains what that data is and how we handle it. We collect account registration details (your username, contact information and login credentials), session data tied to device type and browser behaviour, and transaction references connected to payment methods you use, including DANA and OVO. We do not sell your personal data to third parties. Data is stored only for as long as it is needed to operate your account, resolve disputes, or meet obligations under applicable law. When you make a deposit or withdrawal through a local e-wallet, the transaction reference is retained in your account history — you can review that record at any time after login. Where third-party payment processors handle a transaction, their own privacy terms apply to that processing leg. We apply access controls to limit who inside our team can view account-level data, and those controls are reviewed periodically. Availability and applicable obligations depend on local law and the region from which you access the platform.
Transaction references from DANA deposits and withdrawals are stored in your account history. You can view these records directly after login — no separate request needed.
OVO transfer references are retained as part of your transaction log. If a record looks incorrect, you can raise it through the account support path described in this policy.
Login timestamps and device session data are collected to protect your account from unauthorised access. This data is not shared with advertising networks.
When a payment is routed through an external processor, that processor's own privacy terms govern their portion of the data. We link to relevant terms where available in the account payment section.
Not every data touchpoint on bluga99 falls under this single policy. Understanding the boundaries helps you know where to look when a specific question comes up. Account access, in-lobby session data, and payment records connected to DANA or OVO are fully within scope. Content served by third-party studios — such as game logic from Pragmatic Play or CQ9 — is governed by those studios' own data practices for game-side telemetry. The four categories below map out what is and is not covered.
Login activity, session duration, and account settings changes are within scope. We log these to protect your account and to help you recover access if something goes wrong.
Transaction references and wallet identifiers for DANA and OVO payments are within scope. The processing leg handled by an external payment gateway is outside our direct policy coverage.
Editorial content, game lobby pages, and promotional displays on bluga99 do not carry personal identifiers. Aggregate analytics used to improve page layout are anonymised before we review them.
Game engines from studios like Pragmatic Play, CQ9, or Microgaming run inside iframes with their own data scopes. We do not control telemetry collected at the game-engine level — check the studio's own policy for those specifics.
This policy is not passive — you have real actions available to you, and we have set up clear paths for each one. Want to see what account data we hold? Log in and go to Account Settings, where your profile details, linked payment methods and session history are visible without needing to contact support. If any detail is wrong — a contact address, a preferred payment method, or a display name — you can edit it directly from that screen. For data that is not editable through the account interface, raise a correction request through the support channel listed in the Contact section of this policy. If you want to understand why a specific piece of data was collected, you can ask; we will respond through the same channel. Requests tied to account closure or data deletion are handled case by case and subject to any retention obligations under local law where your access is based. Every response path is outlined below.
After login, open Account Settings to see stored profile data, your linked e-wallet details and the transaction history connected to DANA or OVO payments.
Editable fields — name, contact info, payment method — can be updated directly in the account screen. Non-editable data corrections go through the support channel.
Send your question to the privacy contact listed in the Support section. We aim to acknowledge every request and respond with the relevant data handling explanation.
If you want a summary of what personal data we hold for your account, submit a written request via the support email. Processing time depends on the scope of the request and applicable local requirements.
If you have a question specifically about this privacy policy — a data correction, a records request, or a concern about how account data was used — the three contact paths below are the right channels. General account help and payment queries follow the same routes. Response handling depends on the nature of the request and current queue; data-specific requests may take longer than general account queries.
Send data requests and policy questions to our support email. Include your account username and a clear description of the data concern so we can route it correctly.
For quicker acknowledgement of a privacy concern, open the live chat window from the account dashboard. The agent will log your request and escalate data-handling questions to the right team.
The support section inside your account lists current contact options and their availability. Check there after login for the most current response channel and any status updates on your request.
Account security and data retention are operational commitments, not just policy text. When you log in from your mobile device, your session is authenticated before any account data or transaction history — including DANA and OVO records — is rendered on screen. We apply role-based access controls internally, meaning only team members with a specific operational need can view account-level data. Cookies are used to maintain your session state and remember lobby preferences; you can manage cookie behaviour through your browser settings. Retention periods are set by account status and applicable legal obligations — active account data is retained while the account is open, and a defined retention window applies after account closure. The current state of your stored data is shown in your account dashboard after login.
Every login triggers an authentication check before account data is shown. Session tokens expire after inactivity, and a new login is required to access your records or transaction history again.
We use session cookies and preference cookies. Session cookies expire when you close the browser. Preference cookies remember lobby settings. Manage or clear both through your browser's cookie settings at any time.
Account data is retained while your account is active. After closure, a retention period applies as required by local law. You can ask for a summary of what is retained through the privacy email contact.
Access to personal account data inside our team is restricted by role. Payment records linked to DANA or OVO transactions are accessible only to the team members who handle payment disputes and compliance queries.
The questions below cover what real account holders ask when they want to understand their data rights on bluga99. If your question is not here, use the privacy email or live chat contact path listed in the Support section.
We collect your registration details — username, contact information and login credentials. When you make a deposit using DANA or OVO, a transaction reference is also stored in your account history. Session and device data is collected to protect your login.
Yes. After login, open Account Settings to view your profile data, linked payment methods and transaction history. For a full data summary beyond what is visible in the dashboard, submit a written request through the privacy email contact.
We do not sell your personal data. Payment processors handling DANA or OVO transactions process the payment-leg data under their own privacy terms. Game studios like Pragmatic Play and CQ9 operate game engines with their own telemetry scope — we do not control that layer.
Editable fields — contact information, display name, linked payment method — can be updated directly in Account Settings after login. For data that cannot be changed through the account interface, raise a correction request through the privacy email or live chat support path.
Active account data is retained while your account is open. After closure, a retention period applies based on applicable local law and any outstanding dispute or compliance obligation. You can request clarification on your specific retention window through the support email.
Yes. Session cookies maintain your login state and expire when you close the browser. Preference cookies remember your lobby settings across visits. You can manage or remove both types through your browser's built-in cookie settings — no account action is needed to do this.