Reference

bbca4d Privacy Policy for Your Account

bbca4d Privacy Policy puts account, cookie and wallet-record rules in one place, including what we collect when you verify your phone and use DANA or QRIS.

Account data clarityWallet record contextContact steps
bbca4d bbca4d Privacy Policy for Your Account
CONTACT PATH

Find QRIS Policy Help Near Login

A privacy question should not interrupt your account flow. Start with the support chat route shown near account help, and include the email or phone detail connected to your account without sending…

Support chat Use the support chat path beside account help for privacy questions, sign-in concerns or a request to locate a DANA, OVO or QRIS transaction reference.
Account contact Send your account identifier and the subject of your request through our displayed contact route; keep passwords, wallet PINs and verification codes out of the message.
Receipt check For a payment-data question, share the relevant bank transfer or virtual account reference so we can check the record without asking for unnecessary wallet credentials.
ACCOUNT SAFETY

Check Phone Verification Data Choices

We keep the Privacy Policy connected to real account actions rather than hiding it behind general wording.

Account details

We may handle the details you enter for an account, including contact data and phone verification status, so we can connect your sign-in with the correct account record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help match a transaction question; we do not need your wallet PIN to perform that check.

Cookies and devices

Cookies can retain session state and page preferences on your mobile browser. Clearing them may sign you out or remove saved settings, but it does not erase account records automatically.

Login protection

Phone verification and account checks help us distinguish your access from unusual sign-in activity. Never place a password, PIN or one-time code in a support request.

Record retention

We retain account, support and payment references only as needed for the stated service, security checks, dispute handling and legal duties that apply where local law permits access.

Requests and changes

You can contact us to ask what eligible data we hold, request a correction or raise a deletion question. We may verify account ownership before making a change.

Search bbca4d Privacy Policy Answers

These Privacy Policy answers cover the questions you are most likely to have before opening an account or sending a request. We keep the examples tied to account access, mobile cookies, phone verification and Indonesian payment references so you can find the relevant step quickly.

It covers account details, phone verification, cookies, device sessions, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification status to connect access with the correct account and help identify unusual sign-in activity. We do not ask you to place verification codes in support messages.

Yes. It explains how transaction references may support payment matching and receipt checks for DANA and QRIS, while your wallet PIN and private authentication codes should remain with you.

Cookies can preserve session state and page preferences in your mobile browser. Clearing them may sign you out or reset settings, but it does not by itself remove stored account data.

Where local law permits, contact us through the displayed support route with your account identifier and request type. We may verify ownership before supplying a copy or changing a record.

Retention depends on the purpose and applicable legal duties. Account, support and payment references may remain for security, dispute handling or required records, as described in the Privacy Policy.

Access and eligibility depends on local law. Where local law permits, you can read the policy, contact us about your data and ask how a regional rule affects your request.