Reference

Privacy Policy For Your gbk slot Account

gbk slot Privacy Policy explains how we use account details, phone verification records, wallet references and device data when you access Auto Roulette, kudatogell or other lobby areas.

Account dataWallet recordsCookie choicesContact route
gbk slot Privacy Policy For Your gbk slot Account
CONTACT PATHS

Privacy Help Beside Your Account Route

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages. If your phone verification, wallet reference or data request needs attention, use the support route connected to your account area and include the email or phone detail attached to the account. We ask for enough context to locate the record, not a copy of your wallet password or one-time code.

Team online

Account data request

Ask us to confirm the personal data connected with your account, including the phone verification status and login contact. We will use the account detail you provide to locate the correct record and may request an additional identity step before sending private information.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date, amount reference and wallet name through the account support route. We can check the matching transaction record while keeping your wallet PIN, password and one-time code out of the request.

Policy change request

Use our support route when you need to correct a phone number, ask about retention or object to a stated data use. We will explain the available step for your account and may pause the change until ownership has been checked.

HANDLING DETAILS

How We Apply Privacy Controls

Our approach is practical: collect what an account step needs, restrict internal access and give you a route to ask questions.

Account collection

We collect details you enter during account opening, including a phone number used for verification, together with login events and device signals that help identify unusual access. We do not ask for your wallet password or one-time code as part of an ordinary policy request.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain transaction references needed to match account history and resolve status questions. These references are not the same as storing your wallet PIN, bank password or full private banking credentials.

Cookie settings

Cookies and similar device storage can keep a session active, remember a selected language or help us understand whether a page loads correctly. You can adjust browser settings to restrict cookies, although some account access steps may then need to be repeated.

Security checks

We use phone verification, login records and account-specific checks before discussing private data or changing important details. If access from a new device looks different, we may ask you to complete the account step again rather than disclose records immediately.

Retention timing

We keep account, support and transaction references only for as long as needed for the stated service, dispute handling, security checks or applicable legal duties. When a record is no longer needed, our handling process is to remove it or separate it from direct account identifiers.

Your requests

You can ask what data we hold, request a correction, ask about deletion where available or question a use described in this Privacy Policy. Send the request through account support with your account contact; we may verify ownership before completing it.

Privacy Policy Questions From Indonesia

These answers address the searches we expect you to make before opening an account or sending a data request. Each answer follows the same Privacy Policy described above and uses the account, wallet and device steps you will see when access is available where local law permits.

It covers information connected with your account, such as your phone number, verification result, login events, device signals, support messages and transaction references. It also explains cookies, retention, security checks and the route for asking about, correcting or deleting data where that option is available.

Phone verification helps us connect the account to the contact detail you supplied and reduces the chance of another person changing private account data. We record the verification result and related account event, not your phone password. Additional checks can apply before a sensitive change.

Yes. The policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account records. We use those references to match account activity and investigate status questions; we do not need your wallet PIN, bank password or one-time code.

Use the support route linked to your account area and state that you are making a data request. Include the account phone or email and describe the records you want. We may verify ownership first, then explain which records can be provided and in what form.

You can ask us to correct an inaccurate phone number or other account detail, and you can ask whether deletion is available for a particular record. Some transaction, security or legal records may need to remain for a stated period. We will explain the result for your request.

Cookies may keep your session active, remember a selected setting and help us identify page-loading errors on your mobile browser. You can restrict them through browser controls, but login or phone verification may need to be repeated. The same Privacy Policy applies on desktop and mobile.

Start with the account support route and identify the issue as a Privacy Policy concern. Tell us whether it involves login data, a DANA or QRIS reference, cookies, retention or a correction request. Do not send a password or one-time code; we will request only suitable ownership details.