Reference

tanjung899 Privacy Policy for Your Account

Our Privacy Policy explains how tanjung899 handles the details connected with your account, mobile browser access and wallet activity.

Account dataWallet recordsCookie choicesPrivacy requests
tanjung899 tanjung899 Privacy Policy for Your Account
REQUEST HELP

Open The Right Privacy Support Path

A clear contact route helps you act on this Privacy Policy without guessing which team to reach. Tell us whether your request concerns account access, a DANA or QRIS receipt, cookies, stored contact details or a correction. Include the account identifier you use and the relevant date, but do not send a password or full wallet credentials.

Team online

Account access

Ask us to check account data linked with a phone verification step or a mobile-browser sign-in. We may request details that confirm the account belongs to you before responding.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the receipt reference and status shown in your account so we can trace the correct record.

Privacy changes

Request a correction, access copy or deletion assessment through our support route. We explain any identity check, retention reason or local-law restriction that affects the request.

DATA HANDLING

Browse How Account Data Stays Protected

Our handling process follows the practical moments where privacy questions usually arise: opening an account, moving between a phone and desktop browser, checking a wallet receipt and asking for help.

Account details

We may hold your phone number, account identifier and verification status to create access and help recover a session. Check that your details are correct before requesting a change.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match receipts with account activity. We use the reference for status checks rather than asking for wallet passwords.

Cookies and sessions

Cookies can keep a browser session working, remember selected settings and help us detect unusual access. You can manage browser cookie controls, though some account functions may then require another sign-in.

Security checks

Phone verification and sign-in signals help us distinguish your account from an unfamiliar device. Never share your password or verification code when contacting us about Privacy Policy matters.

Retention decisions

We retain records only while they serve account operation, payment reconciliation, dispute handling, security review or a legal requirement. When a retention reason ends, we assess the record for removal.

Your requests

You can ask for access, correction, deletion assessment or an explanation of use. Send the request through support with enough account detail for us to locate the right records.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the account and wallet questions you may have before opening access. If your situation is not listed, use the support path and describe the specific record, device step or payment reference involved.

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

Phone verification helps connect account access with the correct person and supports checks when a sign-in comes from an unfamiliar device. We do not need your password or wallet code for a policy request.

Yes. The policy covers data created when you sign in through a mobile browser, switch to desktop, keep a session active or adjust cookie settings. Some changes may require another sign-in.

We use DANA and QRIS references to match a receipt with your account, check a pending status and investigate a mismatch. Send only the relevant reference; never send a wallet password or security code.

Yes. Ask through our privacy support route and identify the account details involved. We may confirm ownership first, then explain which records can be copied, corrected or retained for a stated reason.

Retention depends on why the record exists, such as account operation, payment reconciliation, security checks, disputes or legal duties. We assess removal when that reason ends, subject to local requirements.

Use the support path for account access, wallet records or privacy changes. Include your account identifier and relevant date, and tell us whether the request concerns cookies, verification, payment status or stored details.