Reference

batik77 Privacy Policy for Your Account Data

Clear choices for your account, device and wallet records are set out in the batik77 Privacy Policy.

DANA and QRIS recordsMobile cookie choicesPhone verification data
batik77 batik77 Privacy Policy for Your Account Data
PRIVACY CONTACT ROUTES

Privacy Help Beside Cashier Access

A clear contact path matters when a data question appears beside a wallet receipt or login step.

Account privacy request Send a request from your signed-in account when you want to ask what phone…
Wallet record question For DANA, OVO, GoPay or QRIS records, include the payment reference and date in…
Cookie support path If cookie choices affect a mobile sign-in or policy page, tell us your device…
HANDLING YOUR RECORDS

Mobile Cookies and Account Security

We handle privacy requests through practical account controls rather than broad promises. A phone verification step helps us avoid sending account data to the wrong person, while session records help us trace…

Data we collect

We may receive account details, phone verification results, device signals, session activity and payment references. The exact data depends on the action you take, such as signing in, checking a receipt or requesting account help.

Cookie choices

Necessary cookies support sign-in and page security. Preference or measurement cookies are handled according to the choices available in your browser or cookie prompt, so you can ask us what each setting does.

Account protection

We use phone verification and session checks to reduce mistaken disclosure. Never send a wallet PIN or full authentication code in a privacy request; our support route should receive only the details needed to locate your case.

Payment records

A DANA, OVO, GoPay or QRIS reference can connect a payment status to your account request. Bank transfer and virtual account records follow the same purpose-led approach for matching, disputes and security checks.

Retention period

We keep account and transaction records only for the period needed for service operation, security checks, disputes or legal duties described by the Privacy Policy. You may ask why a particular record remains stored.

Change or deletion request

Ask us to correct inaccurate account data or explain a deletion request through authenticated support. Some records may need to remain where a security, dispute or legal reason applies, depending on local law.

Privacy Policy Questions for batik77

These Privacy Policy answers address the searches we hear most often before an account is opened. You can ask about wallet references, mobile cookies, phone verification, retention or access from Indonesia, and we will keep the response tied to your actual request and the policy wording.

It covers account details, phone verification, device and session records, cookie choices, payment references and requests to access, correct or remove data. It also explains retention and contact routes.

No. A Privacy Policy request should never include a wallet PIN or full authentication code. We may retain a DANA or QRIS reference, status and related account details needed for matching.

We collect the details needed for account creation and phone verification, then may record device, browser and session signals. The policy explains the purpose of each category and when it is retained.

Contact us through the signed-in support route and ask for a data access request. We may verify your phone or account step first, then explain which records can be supplied.

Yes. Send the correction request through authenticated support and identify the inaccurate field, such as a phone detail or account record. We will assess it under the Privacy Policy and local requirements.

Open the cookie prompt or your browser privacy controls on the mobile device, then adjust optional preferences. Necessary session cookies may still operate so sign-in and policy access can function.

Some access, deletion or retention outcomes depend on local law. We explain the reason for any limitation and keep your request tied to the account, device or payment record concerned.