Reference

btr4d Privacy Policy for Your Indonesia Account

Your Privacy Policy choices stay clear from account creation through wallet checks, so you can understand what we collect and why.

Clear data purposesWallet record clarityAccount access controlsIndonesia-focused wording
btr4d btr4d Privacy Policy for Your Indonesia Account
PRIVACY HELP

Get Privacy Help Through Your Account

A privacy request should be easy to route, especially when a wallet receipt or phone check is involved. From your signed-in account, use the support path and include the email or phone number connected to your profile, the request you want handled, and any relevant reference. We use those details to confirm ownership before discussing account data, including when you reach us from a phone browser.

Team online

Account request

Ask us to access, correct or explain personal data through the signed-in support path. Include your account contact detail so we can match the request without exposing records to another person.

Wallet clarification

If DANA, OVO, GoPay or QRIS shows an unfamiliar reference, send the receipt code and date through support. We use the record to check the account link and payment status.

Access concern

For a lost phone, unusual sign-in or failed verification, tell us through account support as soon as possible. We may ask for account details before changing access or discussing stored records.

SECURITY PRACTICE

How We Protect Account Data

Privacy depends on practical handling, not just a page of promises. We separate identity details from payment references where our operating records allow, limit internal access to account work, and use sign-in…

Collected details

We may handle your name, contact route, verification result, sign-in history, device signals and account activity needed for access support. Payment records such as QRIS receipt references help us reconcile an account action.

Cookie controls

Cookies can keep a session active and remember basic settings on your phone browser. You can clear them through browser controls, although doing so may require another sign-in or repeat a security check.

Account security

Phone verification and sign-in checks help us distinguish your access from an unfamiliar device. Never send a wallet password through support; we only need the account details required to confirm ownership.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data, status results and receipt details. We use these records for matching, support and dispute handling rather than wallet credentials.

Record retention

We keep personal data while it supports account access, payment questions, dispute handling or a legal need described by the policy. When those purposes finish, records are removed or changed so they no longer identify you.

Changes and contact

To request a copy, correction, deletion or explanation, contact us through the account support path with your linked email or phone. We may verify the request first, then explain the action and any limits.

Privacy Policy Answers for btr4d Accounts

These Privacy Policy answers cover the account questions we expect before you open an account or send a support request. We keep the wording practical: what we collect, how wallet references work, how browser data is handled, and what you can ask us to change where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, payment references, support requests, retention and your available requests for access, correction or deletion.

Phone verification helps connect an account to the person requesting access and reduces mistaken disclosure. We may use its result during sign-in support without asking for your DANA, OVO or GoPay password.

Yes. The policy covers QRIS, DANA, OVO, GoPay, bank transfer and virtual account references, status results and receipt details used to match account actions and answer payment questions.

You can send a correction request through the signed-in account support path. Include your linked email or phone and explain the field that appears wrong; we may verify ownership before changing it.

Cookies can maintain your session and remember basic browser settings. You can clear or restrict them in your phone browser, but the next visit may require another sign-in or security check.

We retain records while they support account access, payment matching, dispute handling or a stated legal need. After that purpose ends, we remove or anonymise the data when appropriate.

Use the account support path and request deletion with your linked contact detail. We confirm ownership first and explain whether any record must remain for payment disputes or a legal obligation.