Reference

batak5d Privacy Policy for Your Account Data

Your batak5d Privacy Policy explains which account, wallet and device details we use when you open an account, verify your phone and enter the lobby.

Account clarityWallet referencesCookie choicesChange requests
batak5d batak5d Privacy Policy for Your Account Data
CONTACT ROUTES

Ask About Privacy Policy Through Support

A clear support route helps when you need to understand a data entry or wallet reference. Contact our account support path from the same account details used for phone verification, and include the subject of your Privacy Policy request. If a DANA or QRIS receipt is involved, keep its reference ready, while never sending a password or full wallet PIN. We can then direct your request to the right handling path.

Team online

Account data request

Tell us which account detail you want explained, corrected or removed. We may ask you to confirm the phone number linked during account access before discussing private records.

Wallet reference check

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date rather than secret wallet credentials. This helps us locate the relevant record safely.

Policy clarification

When a Privacy Policy paragraph is unclear, quote the section heading and describe your concern. We will explain the handling in plain English and note any local-law restriction.

HANDLING PRACTICE

What We Do With Your Account Records

We handle account data in defined steps rather than treating every detail alike. Phone verification helps connect a request to the correct account, while sign-in and device signals help us investigate unusual…

Collected account fields

We may use your contact details, verification status, sign-in events and support messages to operate the account. We collect only the fields needed for the stated account or security purpose.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a receipt with an account event. We use the reference for matching and status work, not secret wallet credentials.

Cookie controls

Cookies can keep a signed-in browser session working and help us understand a requested page path. You can clear or restrict them in browser settings, though some account steps may then need repeating.

Mobile device signals

On a phone, we may record device and sign-in signals used to protect account access. The browser path from phone verification to the lobby remains separate from your wallet password.

Retention approach

We keep records for the period needed to operate the account, resolve a support request, protect against misuse or meet a legal duty. The applicable period can depend on the record type.

Changing your data

Request a correction or privacy change through account support, using the verified contact path. State the field or request clearly; we may confirm ownership before making an account record change.

Privacy Policy Answers For batak5d Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or asking about an existing record. We cover phone verification, cookies, Indonesian wallet references, mobile access and change requests. If your situation involves a specific receipt or account event, use the support path with the reference available and avoid sharing passwords or wallet PINs.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains purposes, retention, security handling and how you can request a correction.

Phone verification helps us connect account requests with the correct account and reduce mistaken disclosure. We may ask you to confirm the verified contact route before discussing private account records.

Yes. The policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help trace status or receipt questions without requesting secret wallet credentials.

Contact account support through the verified contact path and name the exact field or record you want corrected. We may confirm ownership first, then assess the request under the Privacy Policy.

Cookies may keep your browser session active and support a requested account path. You can clear or restrict them in phone browser settings, although you may need to repeat sign-in or verification.

Retention depends on the type of record and why it was collected. We keep data as needed for account operation, security checks, support resolution or a legal duty, then handle it according to the policy.

Yes. Account access and eligibility depends on local law, and our handling applies where local law permits. If your location or request creates a restriction, support can explain the relevant policy path.