Reference

Open toko138slot Privacy Policy Clearly

toko138slot Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet checksCookie choicesContact routes
toko138slot Open toko138slot Privacy Policy Clearly
ASK ABOUT PRIVACY

Contact Support About Your Data

A clear support route helps when you want to ask what data we hold or why a check was requested.

Account help Start with the account help path when your request concerns phone verification, sign-in records…
Wallet status For a DANA, OVO, GoPay or QRIS query, share the payment reference and approximate…
Policy request Ask us to explain, correct or update a personal detail through the same support…
DATA HANDLING

Browse toko138slot Privacy Controls

Privacy work is tied to ordinary account actions, so our process follows the path you actually take.

Data collected

We may handle your contact details, account activity, phone verification result, device signals and payment references. These details help us sign you in, protect the account, answer support questions and reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.

Cookie choices

Cookies and similar device storage can remember a session, support security checks and preserve a selected preference. You can adjust browser controls, but removing necessary storage may require another sign-in or interrupt a requested account action.

Account security

Phone verification helps connect access to the account you created. We also examine unusual sign-in signals and may pause a sensitive request until the account check is complete. Never send a password, wallet PIN or one-time code in a support message.

Retention approach

We retain account and payment references for as long as needed for security, support handling, reconciliation and applicable legal duties. The period can differ by record type. Ask support which category applies to your request and what removal options are available.

Correction requests

If your name, contact detail or another profile field is wrong, contact us through account help with the requested correction. We may verify ownership first, then record the change so the account history remains clear and protected.

Access questions

You can ask what personal data is linked to your account, how it is used and whether a specific record is retained. We assess the request under local requirements, and access depends on local law where the request is made.

Find Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. We explain the practical steps for access, correction, cookies, security and contact so you know what to prepare. If your situation is unusual, contact support with your account reference and we will assess the request under the policy and local requirements.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with your use of the site. We explain why each category may be handled, how it supports account security, and how you can ask about access, correction or retention.

Those wallet names may appear in a support or reconciliation record when you check a payment status. We use the relevant reference to locate the correct transaction and account. We do not need your wallet PIN, password or one-time code to investigate that record.

Use the account help path and ask for a personal data access request. Include the phone number linked to your account and any useful date or record reference. We may verify ownership before responding, and access depends on local law where the request is made.

Yes, you can ask support to correct an inaccurate profile detail, such as a contact record. Send the requested change through account help rather than opening a new profile. We may complete an ownership check first so an unknown person cannot edit your account.

Cookies can preserve a session, support security checks and remember a preference on your browser. You can change browser storage settings, although necessary cookies may be required for sign-in. Clearing them can remove the session and prompt you to verify access again.

Retention depends on the record, its security purpose, support needs, reconciliation requirements and applicable legal duties. A DANA, QRIS, bank transfer or virtual account reference may therefore remain longer than a temporary browsing signal. Support can explain the category relevant to your request.

You can contact support with a removal request and identify the account record involved. We assess what can be removed against security, reconciliation and legal requirements. Some records may need to remain for a defined purpose, and we will explain the applicable reason.