This page explains exactly how kebutoto collects, uses and protects the information tied to your account — from the moment you open a session to the records we keep after a transaction is complete. We keep it plain because your data choices matter, and you deserve a clear explanation, not legal filler.
Account data handled directly by kebutoto
Local payment context: DANA, OVO, GoPay
Available where local law permits
Your rights are outlined here
DATA WE COLLECT
What Information We Collect and Why
When you create an account with kebutoto, we collect the details you enter directly — your email address, chosen username and any account-verification fields we ask you to complete. When you make a deposit or withdrawal using DANA, OVO, GoPay or Bank Transfer, we record the transaction reference and the e-wallet identifier associated with it. We do not store your full e-wallet credentials or PIN on our servers; payment authentication happens on the payment provider's own channel. We also collect session data automatically: the device type you use to access the lobby, your browser or app environment, your approximate region, and the pages or game rooms you open during a session. This helps us maintain account continuity across devices — so if you start a session on your phone and switch to a browser later, your account state carries over. All collected data is used for account management, transaction verification, security monitoring and service improvement. We do not sell your personal data to third parties. Data availability and retention depend on local law and the eligible region in which your account is registered.
DANA & OVO Transactions
Transaction references tied to DANA or OVO deposits are recorded for verification only. We do not retain wallet PINs or authentication tokens.
GoPay & Bank Transfer
GoPay payment references and Bank Transfer confirmation codes are logged against your account for dispute resolution and balance accuracy.
QRIS Scan Records
QRIS scan data captures the session timestamp and transaction amount. No additional wallet credentials are stored beyond the reference string.
Session & Device Data
Device type, session region and navigation path are logged to support account continuity and detect unusual access patterns on your account.
POLICY COVERAGE SCOPE
Where This Policy Applies and What It Covers
This policy governs data collected directly through the kebutoto platform — including account registration, wallet activity, in-session behaviour and support interactions. It does not extend to third-party services you connect to through our pages, and it applies only where local law permits access to the platform. Understanding the boundary of coverage helps you know which questions to bring to us and which to direct elsewhere.
Account Access
All data collected during account creation, login and session activity falls under this policy. This includes the fields you fill in at registration and the authentication steps shown in your account.
Transaction Records
Deposit and withdrawal records processed through DANA, OVO, GoPay, Bank Transfer or QRIS are covered here. We hold these records for account verification and balance accuracy.
Site Content Interaction
Navigation data — which lobby sections or game rooms you open, how long a session runs — is collected by us and falls within this policy. No content provider receives your personal identifiers.
Third-Party Services
Payment providers like DANA, OVO and GoPay operate their own privacy policies for the authentication step that occurs on their channel. Their data handling is outside kebutoto's direct control.
YOUR DATA RIGHTS
Practical Actions You Can Take Under This Policy
You have concrete choices about the data kebutoto holds on your account. You can review the personal details attached to your account at any time through the account settings page after login — the fields shown there reflect what we currently hold. If any detail is inaccurate, you can edit it directly in account settings or raise a correction request through our support channel. If you want to understand what transaction data we hold, the transaction history inside your account dashboard is the first place to check. For records outside the visible dashboard window, contact our support team with your account identifier and we will confirm what is retained. You also have the option to request account closure, which triggers a review of which records are kept for legal or regulatory reasons and which are removed. The outcome depends on the jurisdiction in which your account is registered.
Review Your Records
Log in and open account settings. The data fields shown there are the personal details we currently hold against your account.
Correct Account Details
Edit inaccurate details directly in account settings. For fields that cannot be self-edited, submit a correction request via our support contact.
Ask a Privacy Question
Send your question through the support contact listed on this page. Include your account identifier so we can locate the correct records.
Request Account Closure
Contact support to start the account closure process. We will confirm which records are retained under local legal requirements and which are deleted.
PRIVACY CONTACT PATHS
How to Reach Us About This Policy
If you have a question about the data we hold, a correction you need made, or a request tied to this policy, the routes below are the right place to start. Have your account identifier ready when you contact us — it helps us locate your records without delay.
Live Chat Support
Open the chat widget from any page after login. Describe your privacy question and include your account ID. Our team will confirm receipt and follow up on your request.
Email Contact
Send your privacy request to our support email address shown in the account help section. Write your account identifier in the subject line for faster routing.
Account Help Center
The help section inside your account dashboard lists current contact options and response guidance. Check there for the most current contact details, as they are updated when routes change.
HOW WE PROTECT DATA
Our Approach to Data Handling and Account Security
Data security at kebutoto is built around limiting what we hold and controlling who can access it. Account credentials are stored in hashed form — we do not hold your password in readable text. Payment transaction references from DANA, OVO, GoPay and Bank Transfer are stored separately from your core account profile, so a single data point does not expose the full picture of your activity. We use cookies to maintain your session state across page loads; you can review and adjust cookie preferences through the settings shown in your browser or the cookie notice on the site. Data retention follows the requirements of the jurisdiction in which your account is registered — records tied to financial transactions may be held longer than general session data, as local law or eligible-region rules require. If you want to know the specific retention period that applies to your account, contact our support team with your account identifier.
Credential Storage
Passwords are stored in hashed form only. We never hold your DANA, OVO or GoPay PIN. Payment authentication takes place on each provider's own secure channel, not on ours.
Cookie Use
We use session cookies to keep your account active across page loads and analytics cookies to understand which lobby sections are used most. Adjust preferences in your browser settings or via the cookie notice.
Retention Period
General session data is held for a limited period. Transaction records — especially those linked to Bank Transfer or QRIS activity — may be held longer where local law or eligible-region rules require it.
Policy Updates
When this policy changes in a material way, we update the date shown at the top of the page and, where appropriate, note the change in your account notification area. Continued account use after an update means you have seen the revised version.
PRIVACY QUESTIONS ANSWERED
Frequently Asked Questions About This Privacy Policy
The questions below cover what we hear most from people reading this policy for the first time. If your question is not here, reach out through the support routes listed above.
What personal data does kebutoto collect when I open an account?
We collect the details you enter at registration — email address, username and any verification fields shown in the sign-up flow. We also collect session data automatically, including device type, approximate region and the pages you open during a session.
Does kebutoto store my DANA, OVO or GoPay credentials?
No. We record transaction references only — the confirmation code that ties a deposit or withdrawal to your account. Your wallet PIN and authentication tokens are handled entirely on the payment provider's own channel, not on ours.
How can I see what data kebutoto currently holds on my account?
Log in and open account settings. The personal details shown there reflect what we currently hold. For transaction records, your account dashboard displays your history. For records outside that window, contact support with your account identifier.
Can I correct or update the data tied to my account?
Yes. Some fields can be edited directly in account settings. For fields that are not self-editable — such as identity-verification records — submit a correction request through live chat or email support. Include your account ID so we can locate the right record.
How long does kebutoto keep my data after I stop using my account?
Retention periods depend on the jurisdiction and eligible region of your account. Transaction records linked to financial activity — Bank Transfer, QRIS, DANA — may be held longer than general session data, as local legal requirements apply. Contact support for the specific period that applies to your account.
Does kebutoto share my data with third parties?
We do not sell your personal data. Payment providers like DANA, OVO and GoPay receive only the transaction references needed to process your deposit or withdrawal. Each provider's own privacy policy governs what they do with that data on their side.