Reference

168gg Privacy Policy For Your Account

Clear control over your account data starts here: our Privacy Policy explains how we handle login details, device signals and wallet records linked to DANA, OVO, GoPay or…

Account recordsWallet activityCookie choicesPolicy requests
168gg 168gg Privacy Policy For Your Account
CONTACT POLICY HELP

Where To Ask About Your Privacy Policy

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Use the support route shown after login, include the email or phone detail attached to your account, and tell us whether your request concerns access, correction, deletion or a payment reference. We can then locate the relevant record without asking you to send unnecessary personal details.

Team online

Account contact

Open the support route from your signed-in account and identify the email or phone detail connected to your Privacy Policy request. We use those details to locate the correct record.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the transaction reference and date. Do not send a wallet password or full payment credential.

Access request

Ask for a copy, correction or removal of eligible personal data through our contact path. We may verify account ownership before changing records or disclosing account-linked details.

DATA CONTROL STEPS

Inside 168gg Privacy Policy Handling

We treat privacy work as an account operation, not a hidden setting. Our process connects your request to the right account record, checks the scope of the request and keeps a written…

Collected account data

We may receive your account contact details, phone verification result, sign-in activity, device information and payment references. We collect these details for account access, transaction matching, safety checks and policy requests.

Cookie controls

Cookies and similar device storage can remember sign-in preferences and help us understand page errors. Your browser settings provide a way to remove or restrict them, although some account steps may then need repeating.

Account security

Phone verification before account access helps connect a sign-in to the right account. We also examine unusual device or login signals and may ask for additional ownership checks before discussing private records.

Payment references

A wallet or bank reference is handled as transaction data, not as permission to request your secret wallet code. DANA, OVO, GoPay, QRIS and bank transfer details help us match status and resolve a query.

Retention decisions

We retain records for the period needed for the purpose described in this policy, account security and applicable legal duties. When a record no longer needs retention, our process addresses its removal or restricted use.

Changing your details

Send a correction or removal request through the account support path, state which field is wrong and provide enough context to identify it. We verify ownership first, then confirm the action or explain its limit.

Privacy Policy Answers For 168gg

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. Each answer stays focused on personal data, wallet references, device activity and the steps available to you. Where an eligibility question arises, access depends on local law and the applicable conditions for your location.

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

Phone verification helps us connect account access to the correct person, reduce mistaken sign-ins and protect private records. We may use the result when handling a data access, correction or removal request.

Yes. The policy covers transaction references and status details linked to DANA, OVO, GoPay and QRIS. It also addresses bank transfer and virtual account references used to match an account transaction.

Use the support route available from your signed-in account, state that you are making a Privacy Policy data request, and identify the records you need. We may verify account ownership before responding.

Yes. Send the correction through the account support path and name the inaccurate field. Include the related account detail or transaction date, but never send a wallet password or secret code.

Cookies can retain sign-in preferences and help us identify page errors. You can restrict or remove them in your browser, though repeating phone verification or other account steps may be necessary.

You can ask us to remove eligible personal data through the account contact path. We first confirm ownership and assess retention needs, including security records or legal duties that may require continued storage.