Reference

Privacy Policy for Your bahtera78 Account

bahtera78 Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet contextDevice controlsLocal-law access
Explore Our Lobby Read FAQ
bahtera78 Privacy Policy for Your bahtera78 Account
CONTACT THE TEAM

Get Privacy Policy Help Inside Your Account

A direct support route helps you ask about personal data without guessing where a request belongs. We keep privacy questions separate from game or wallet choices, while still using the account and cashier paths to locate the relevant record. Include your account contact, the date of the event and the request you want handled; do not send a full wallet password or one-time security code.

Team online

Account contact

Use the account support path to ask what contact, verification or sign-in details are linked with your profile. We can use the account step to locate the right record, while you should keep passwords and one-time codes out of the message.

Wallet query

For a DANA, OVO, GoPay or QRIS privacy question, mention the payment rail and cashier date rather than sending full wallet credentials. We can check the related status reference and explain which details are retained for that transaction.

Correction request

If your name, phone detail or account record needs correction, send the specific field and a safe way to reach you. We may request an account check before changing data, so the request stays connected to the correct profile.

DATA HANDLING

What Our Privacy Policy Does With Records

The practical side of this Privacy Policy is visible in ordinary account actions: a phone check before access, a device session when you sign in, and a payment reference when a wallet…

Account details

We collect details you provide during the account path, such as contact data and verification material. This lets us connect a sign-in to the correct profile before account or cashier details appear, instead of exposing one account's records to another.

Device signals

A mobile browser may send session and device signals when you move from login to the lobby. We use these signals to recognise an active session, identify unusual access and help support trace a sign-in issue without requesting your private phone contents.

Cookies

Cookies and similar browser storage can keep a sign-in session, remember a selected language or preserve a page path. If you clear them, you may need to repeat the phone check or sign in before reaching the lobby.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions can create references such as amount status, timing and matching account details. We use those records to reconcile the cashier path and handle a payment question, not to request your wallet password.

Account security

We may pause access or ask for an additional account check when sign-in behaviour does not match the profile. Keep your password private, sign out on shared devices and contact support if a session reaches the lobby without your action.

Retention and changes

We retain records for as long as they serve account operation, security, support or record duties, then assess whether they are still needed. To request access, correction or deletion where applicable, contact us with the field and account detail concerned.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers cover the searches we expect before you open an account: what we collect, how wallet records are matched, what happens on mobile, and how to request a change. Where a request depends on a legal or account check, we explain the next step rather than asking you to guess.

It covers account details, phone verification, sign-in activity, device session signals, cookies, support requests and payment references. It also explains why we use those records for access, security, cashier matching and record duties. Access depends on local law and the policy is available before you open an account.

Yes. When you use DANA or QRIS, we may handle a reference showing the related account, timing and payment status. The same approach applies to OVO, GoPay, bank transfer and virtual account actions. We do not need your wallet password to match a cashier record.

Phone verification connects the account step to the person requesting access and helps reduce mistaken or unauthorised sign-ins. We may use the verification result when you enter the mobile lobby or ask about a wallet status. Keep one-time codes private and do not place them in support messages.

A mobile browser can create a session record when you sign in, move to the lobby or return to the cashier path. Cookies may keep that session active. Clearing browser storage can require another sign-in or phone check, but it does not give us access to your private phone files.

You can contact support with the specific field that appears wrong, such as a contact detail or verification record. We may ask you to complete an account check before making a change. That step helps us protect the correct profile and avoid altering another account's data.

We keep personal and transaction records while they are needed for account operation, security, support or record duties. Retention can differ by record type and legal need. When you ask about deletion or access, tell us which data you mean so we can assess the request accurately.

Use the account support path and state that your request concerns the Privacy Policy. Add your account contact, the relevant date and a short description, but never send a password or one-time code. If the question concerns DANA, OVO, GoPay or QRIS, name that rail for faster routing.

Related Pages

bahtera78 Indonesia Account information ligaangkasa kucingslot About Us