Mobile / App
This page sets out how miiototo collects, uses, and protects the personal data connected to your account — including information linked to your DANA, OVO, or GoPay wallet when you use those payment channels. Everything described here applies where access is permitted under local law and in eligible regions.
When you create an account with us, we collect the registration details you submit — name, contact information, and the credentials you choose. If you connect a local payment method such as DANA, OVO, or GoPay to your account wallet, the transaction reference and wallet identifier associated with that method are recorded as part of your account history. We do not store full payment credentials on our side; those remain with the payment provider. We also collect technical data produced by your device and browser session — IP address, session timestamps, and interaction logs. This data helps us maintain account security, detect unusual access patterns, and keep the platform available in supported regions. We do not sell this data to third parties for marketing purposes. Data is retained for as long as your account is active and for a further period required by applicable legal obligations in the jurisdictions where we operate. When retention is no longer necessary, records are deleted or anonymised according to our internal schedule. The current state of your stored data is accessible by submitting a request through the contact path shown in the Support section of this page.
Transaction references linked to DANA payments are stored as part of your account wallet history. Full wallet credentials stay with DANA and are not held by us.
OVO payment identifiers appear in your transaction log when you use this channel. We hold the reference only — not your OVO PIN or full account details.
GoPay transfers generate a reference entry in your account record. As with other e-wallet channels, the payment credential itself is managed on GoPay's side.
This policy covers the data we collect and process directly through miiototo. It does not extend to third-party services you reach through links on our platform, nor to the data practices of external payment providers. Understanding which parts of your experience fall inside and outside this policy helps you make informed choices about your account.
All data you submit during account creation or login — including your email address, contact number, and device session — falls inside this policy. We control how it is stored, who can view it internally, and when it is removed.
Transaction references for DANA, OVO, and GoPay payments are within scope. However, the payment provider's own handling of your wallet data is governed by their separate policy, which we do not control.
Session data generated while you browse game categories — including slot sessions, live table activity, and crash game rounds — is recorded under this policy to support account integrity and dispute resolution where applicable.
Any service you access outside our platform — including external sites linked from our pages — operates under its own data policy. We hold no responsibility for how those services collect or use your information.
You have practical options for managing the personal data we hold on your account. These are not abstract entitlements — each one has a clear path you can follow from your account dashboard or by contacting our support team directly. If you want to review the data connected to your account, submit a data access request through the support contact path. We will confirm what records we hold and provide a copy in a readable format. Where any detail is incorrect — for example, a contact number or linked wallet identifier — you can request a correction and we will update it after verifying your identity through the standard account verification step. If you want to close your account and request deletion of your data, this option is also available, subject to any retention period required by law. The current status of any submitted request is shown inside your account dashboard after you log in.
Submit a data access request via our support contact. We confirm what is held and share a readable copy of your account data.
If any stored detail is wrong, request a correction through support. We update it after completing the standard identity verification step shown in your account.
Questions about how specific data is used can be sent directly to our support team. We respond through the same channel you used to contact us.
You may request full account closure and data removal. Processing is subject to any legally required retention period; current request status appears in your account dashboard.
If this policy raises a question you cannot resolve through your account dashboard, our support team is the right place to start. Use the contact path that suits how you prefer to communicate — each route connects to the same team handling data and privacy queries.
Open the live chat window from any page on miiototo. State that your question is about your account data or this privacy policy so the team routes it correctly from the start.
Send your privacy or data request by email to the address listed in the account help section. Include your registered contact detail so we can match the request to your account securely.
Log in and navigate to the help or account section to find the data request form. This route automatically links your submission to your account record, which speeds up the review process.
Data protection at miiototo is handled through a combination of access controls, session monitoring, and storage practices designed to limit exposure at each stage. We do not grant broad internal access to personal account data — access is restricted to the functions that require it. Cookies and session identifiers are used to maintain your logged-in state and to detect unusual activity; you can manage cookie preferences through your browser settings. Payment data from DANA, OVO, or GoPay is handled at the point of transaction and only the reference is retained on our side. If our policy or practices change in a way that affects your data, we will update this page and note the change date at the top of the document.
Account data is stored for the duration your account is active, plus any legally required period after closure. Records no longer needed are deleted or anonymised on a set internal schedule.
We use session cookies to keep your account active and to detect access anomalies. Cookie preferences can be adjusted in your browser settings at any time without closing your account.
Internal access to personal data is limited by role. Only the processes that require your data — account verification, payment matching, support resolution — can read it.
When this policy is updated, the revised version is posted here with a change date. Continued use of your account after a posted update means you have seen the new version.
These questions come up often when account holders read through this policy for the first time. Each answer points to a real step or a real contact path — not a generic gesture.
We collect the registration details you submit: name, contact information, and your login credentials. If you link DANA, OVO, or GoPay to your account wallet, the transaction reference for those channels is also stored. We do not hold full payment credentials on our side.
Submit a data access request through the support contact path — live chat, email, or the form inside your account dashboard. We confirm what records we hold and provide a copy in a readable format after verifying your identity.
Yes. If a stored detail is wrong, contact support with the correction and we update it after the standard identity check. Full deletion requests are accepted and processed subject to any legally required retention period; request status is shown in your dashboard.
The transaction reference recorded when you use DANA or GoPay falls inside this policy. The data your wallet provider holds on their side — including your wallet credentials and transaction history within their app — is governed by their own policy, not ours.
Yes. Session data from slot rounds, live table activity, and crash game sessions is recorded under this policy to support account integrity. This data can be included in a data access request if you want to review it.
When we update this policy, the revised version is posted on this page with a change date at the top. We recommend checking back periodically. Continued use of your account after an update is posted means you have had the opportunity to review the new version.