Mobile / App
This page covers how dobeltoto handles your account data, the scope of our policy obligations, and the steps available to you when something needs to be reviewed or corrected. Access to our platform depends on local law and is available only where eligible under applicable regional regulations.
dobeltoto operates under a policy framework designed to be transparent about what we collect, how we use it, and what choices you have. When you open an account and move through the deposit flow — whether through OVO, Bank Transfer, or QRIS — each transaction is logged against your account record. That log is visible to you from your account dashboard after login. We hold account data only as long as it is needed for the purposes it was collected: processing transactions, verifying account identity, and responding to support requests. Once a retention period lapses or you request deletion where that right applies, data is removed from active records. Availability of this platform and the rights described here depend on local law in Indonesia and apply only in eligible regions. We do not make legal certainty claims about jurisdictions outside our configured service area. If there is a conflict between this policy and a local legal requirement, the local requirement takes precedence. Any material change to this policy will be communicated through your account notification channel before it takes effect.
Understanding the boundaries of this policy helps you know where to direct a question. The four areas below separate what we control directly from what sits with third-party services or your own device.
Login credentials, session management, and account verification steps are covered fully. We control the account layer; the rules here apply end-to-end from the moment you open the login page to the moment your session closes.
Deposits and withdrawals processed through OVO, Bank Transfer, and QRIS fall within our policy for the portion we handle. Once funds move to or from a payment provider's own network, that provider's terms govern the remainder of the journey.
Game content supplied by studios such as Microgaming, PlayStar, JDB, Bigtime Gaming, and Joker is governed by those providers' licensing terms alongside ours. We surface their titles in our lobby but do not override their game-level rules.
External links, partner sites, and services you reach from our pages operate under their own privacy and legal terms. We are not responsible for data handling that occurs outside the dobeltoto domain.
You have concrete actions available to you at each stage of the account lifecycle. To review what personal data we hold, log in and open the account settings section — your profile details, transaction history including OVO and Bank Transfer records, and communication preferences are all displayed there without needing to contact support first. If any detail is incorrect — a name spelling, a registered email address, or a linked payment method — the correction path starts in account settings. Fields that cannot be edited directly are flagged with a contact prompt; use that prompt to raise a correction request and we will process it within the timeframe shown on the confirmation screen. For questions about data retention, policy scope, or how a specific transaction was recorded, the support channel handles those inquiries. Every request receives a reference number so you can track its status.
Account settings shows your full transaction history, profile data, and linked payment methods including OVO and QRIS entries. No support request is needed to read your own records — it is all accessible after login.
Edit eligible fields directly in account settings. For locked fields, the inline contact prompt routes your correction request to the right team with the relevant account context already attached.
Use the support channel for questions about what data we hold, how long we keep it, or how a specific transaction was recorded. Submitting through the account dashboard includes your account reference automatically.
For anything that cannot be resolved through self-service, our support team handles policy inquiries. The response path and expected timeframe are shown in the support section after your request is submitted.
Three contact paths are available for policy-related inquiries. Choose the one that matches how quickly you need a response and whether the issue relates to your account record directly.
Open the chat widget from your account dashboard for account-specific policy questions. This path connects directly to the team that handles data and rights inquiries for Indonesia-region accounts.
Send a written policy request to our support address listed in the account help section. Include your account reference number so the team can locate your record without a separate verification step.
The current state of any active inquiry is shown in your account dashboard after login. Check there first before opening a new request — an existing ticket may already be in progress.
Our approach to data and account security is built around giving you visibility and control at each step. The points below cover the four areas visitors ask about most when reviewing a platform's policy practices.
We collect only what is needed to run your account and process transactions through OVO, Bank Transfer, and QRIS. Cookies used on the site are categorised as essential or functional; the cookie consent layer on first visit lets you review and adjust functional cookie use.
Your account is protected through the verification steps shown during login. If you notice activity you do not recognise, the account security section in settings provides the path to flag it and initiate a review — that is the fastest route to locking the account while the inquiry runs.
Transaction records and account data are held for the period required to fulfil the purpose they were collected for. Where a deletion right applies under local law, the request path is in account settings under data preferences. We confirm receipt and action within the timeframe displayed there.
Material policy changes are communicated through your account notification channel before they take effect. For direct policy correspondence, the contact details are in the account help section — include your account reference so queries are routed to the right team without delay.
Common questions from visitors reviewing the legal and data policy for dobeltoto accounts in Indonesia.
We collect the details you provide during registration — name, email, and contact information — along with transaction data generated when you deposit or withdraw through OVO, Bank Transfer, or QRIS. Device and session data is also collected to run account security checks.
Log in and open account settings. Your profile details, transaction history, and linked payment method records are displayed there. You do not need to contact support to read your own records — the dashboard shows the current state of your account data after login.
Editable fields can be updated directly in account settings. If a field is locked, an inline contact prompt appears — use that to send a correction request with your account context already attached. The team processes corrections within the timeframe shown on the confirmation screen.
Our policy covers the portion of each transaction we handle directly. Once a payment moves through OVO, Bank Transfer, or QRIS into the provider's own network, that provider's terms apply. Your transaction log in the account dashboard shows the point at which each transfer left our system.
Data is held for the period needed to fulfil the purpose it was collected for — account operation, transaction processing, and support. Where a deletion right applies under Indonesia law, the request path is in account settings under data preferences, and we confirm action within the timeframe shown there.
Use the live chat from your account dashboard for account-specific questions, or send a written request to the support email address in the account help section. Include your account reference number so the team can locate your record and respond without a separate verification step.