dpltoto Privacy Policy: How We Handle Your Account Data
This policy explains exactly what data dpltoto collects when you access our platform, how we store it, and the choices available to you. Where access or eligibility is discussed, availability depends on local law and eligible regions in Indonesia.
Account data protection
OVO & Bank Transfer context
Your rights, clearly stated
Indonesia-focused coverage
POLICY FOUNDATION
What Data We Collect and Why
When you create an account on dpltoto, we collect the information you enter directly: your name, contact details, and the credentials used to log in. When you make a deposit or withdrawal using OVO or Bank Transfer, we record the transaction reference and amount — not your full wallet credentials, which stay with your payment provider. We also collect device and session data automatically: browser type, screen size, session timestamps and the pages you navigate through. This helps us keep your account session continuous across a match scroll or a lobby switch without requiring a new login. We do not sell your personal data to third parties. Data shared with payment processors such as OVO or Bank Transfer partners is limited to what those processors need to complete your transaction. Cookies and similar tracking tools are used to remember your login state and your last-visited section of the lobby. You can review which cookies are active and adjust your browser settings to limit them — though doing so may affect how your account session behaves on return visits. Retention periods vary by data type; transaction records are kept as long as required by applicable financial and regulatory obligations in supported regions.
OVO
OVO payment references are handled by the OVO processor. We store only the transaction ID and status needed to reconcile your account wallet balance.
Bank Transfer
Bank Transfer records include the reference number and confirmation timestamp. Full bank account details are not stored on our servers.
Session Cookies
Login-state cookies keep your account active across the lobby, game pages and your transaction history without a forced re-authentication on each tap.
Device Data
We log device type and session identifiers to support account continuity on mobile. This data is not linked to advertising profiles or shared with ad networks.
SCOPE AND LIMITS
Where This Policy Applies
This policy covers data processed directly by dpltoto across our platform. It does not extend to third-party services that operate under their own terms. Knowing what falls inside and outside this policy helps you understand where to direct any data question.
Account Access
Login credentials, session tokens and account-preference data are all covered here. We control how this data is stored, how long it is kept and who within our operation can access it.
Transactions
Deposits and withdrawals processed through OVO or Bank Transfer generate records that fall under this policy on our side. The payment provider's own privacy terms govern data held on their end.
Site Content
Game-launch events, page-view sequences and lobby-navigation paths are captured as usage data under this policy. We use this to maintain session continuity, not to build advertising profiles.
Third-Party Services
Links to external sites, payment processors and game studio delivery networks operate under their own privacy frameworks. This policy does not cover what those third parties collect independently.
YOUR ACCOUNT RIGHTS
Practical Steps Available Under This Policy
You have concrete actions available to you regarding the personal data we hold. Reviewing your account records is the first step — log in and open your account dashboard to see the transaction history, session log and stored contact details associated with your profile. If any detail is incorrect, the account settings page includes fields to update your contact information; follow the verification steps shown there to confirm the change. For data held outside the self-service screens — such as archived transaction references or historical session records — you can submit a written request through our support channel. We aim to respond within the timeframe required by applicable obligations for supported Indonesia regions. If you have a question about how a specific data type is handled, raise it before submitting a formal request; many questions can be resolved faster through a direct support conversation. Deletion requests are evaluated case by case: some records must be retained for the period required by financial or regulatory obligations, and we will tell you which records fall into that category when you make the request.
Review Your Records
Open the account dashboard after login to see stored contact details, transaction references and session history. The current state of your data is shown there without needing to contact support.
Correct Account Details
Account settings let you update contact information directly. Follow the verification fields shown on that page to confirm any change before it is saved to your profile.
Submit a Data Request
For records not accessible through self-service screens, contact our support team with a written request. Include your account identifier so we can locate the relevant records efficiently.
Request Clarification
If you are unsure how a data type is processed, ask through support before filing a formal request. Direct questions often resolve faster than a formal review process.
CONTACT FOR PRIVACY
How to Reach Us About This Policy
Any question about this privacy policy — whether it is about data access, correction, retention or cookies — can be directed to our support team. Use the contact path that works for you; we aim to acknowledge data-related queries and direct them to the right handler without delay.
Live Chat
Open the chat widget from any page on dpltoto to ask a privacy question directly. State that your query relates to account data so it is routed correctly.
Email Support
Send a written privacy request to our support email address listed in the contact section of your account dashboard. Include your account ID and the specific data concern.
Account Dashboard
Your dashboard shows stored data fields, transaction references and session history after login. Many data questions can be answered there without needing to open a support ticket.
HOW WE PROTECT DATA
Data Handling, Cookies and Account Security
Our approach to data handling is shaped around account continuity and minimal exposure. We do not store payment credentials on our own servers; OVO and Bank Transfer transactions are processed by the respective payment provider, and we retain only the reference and status data needed to reconcile your wallet. Session data is encrypted in transit. Cookies used for login state and lobby navigation are session-scoped where possible, meaning they expire when you close the browser. We review data retention schedules periodically and remove records that no longer serve an operational or regulatory purpose. If this policy changes in a material way, we will notify you through the account dashboard or by the contact method on file.
Data in Transit
All data moving between your device and our servers is encrypted. This covers login, account updates and the session tokens that keep your lobby position and open tabs continuous across page navigation.
Cookie Management
Login-state and session cookies are used to maintain account continuity. You can adjust cookie permissions in your browser settings; note that disabling session cookies may log you out between page views.
Retention Policy
We keep transaction records for the period required by applicable financial obligations in supported regions. Account data not tied to a regulatory requirement is removed when it no longer serves an operational purpose.
Policy Updates
When this policy is updated materially, the revised version is published at dpltoto/privacy-policy/ and you are notified through your account dashboard. Continued use after notification constitutes acceptance of the revised terms.
POLICY FAQ
Common Questions About This Privacy Policy
These questions cover the data and account-privacy topics we hear most often. If your question is not answered here, contact support through live chat or the email address in your account dashboard.
What personal data does dpltoto collect when I open an account?
We collect the name, contact details and login credentials you enter during account creation. We also capture session and device data automatically — browser type, screen size and navigation timestamps — to maintain account continuity across your session.
Does dpltoto store my OVO or Bank Transfer details?
No. OVO and Bank Transfer transactions are processed by the respective payment provider. We store only the transaction reference number and status needed to reconcile your account wallet. Your full wallet credentials or bank account number are not held on our servers.
How can I see the data dpltoto holds about my account?
Log in and open your account dashboard. Your stored contact details, transaction history and session log are displayed there. For archived records not visible in the dashboard, submit a written request through live chat or the support email listed in your account settings.
Can I update or correct my personal details?
Yes. The account settings page includes editable fields for your contact information. Follow the verification steps shown on that page to confirm the update. Changes take effect once verification is complete and are visible immediately in your dashboard.
How long does dpltoto keep my transaction records?
Transaction records are retained for the period required by applicable financial and regulatory obligations in supported Indonesia regions. Once that period ends, records that serve no ongoing operational purpose are removed. Contact support if you need clarification on a specific record type.
Who can I contact if I have a privacy concern not covered here?
Reach our support team through the live chat widget on dpltoto or by email via the address shown in your account dashboard. State that your query is privacy-related so it is directed to the correct handler. We aim to acknowledge data queries promptly.