Reference

Open petstoto Privacy Policy Before Account Access

petstoto Privacy Policy puts your account, wallet and device choices in plain English before you open an account.

Account dataWallet recordsCookie choicesPrivacy requests
petstoto Open petstoto Privacy Policy Before Account Access
PRIVACY SUPPORT

Ask Support About Privacy Requests

A privacy question should not require you to search through your account. Our support route can help you identify the request type, confirm which account record it concerns and explain the next step. Keep your verified phone number and any relevant receipt reference ready; never send a password or wallet PIN. Where local law permits, we can also explain how to request a correction or deletion.

Team online

Account privacy path

Use the support contact shown after sign-in to ask about account data, phone verification records or a correction request. We may ask for account details to confirm that the request is yours.

Wallet record help

If a DANA, OVO, GoPay or QRIS reference appears incorrect, share the transaction date and receipt code through our support route. We use those details to locate the relevant wallet record.

Device access question

For a mobile sign-in or cookie concern, tell us the device path you used and the affected account. We can explain the technical record involved without asking for your private login secret.

DATA PRACTICES

See How petstoto Handles Your Data

We keep privacy work connected to the account actions you take, rather than treating every record the same way.

Data we receive

We may receive your phone number, verification result, login events, device type, browser signals, support messages and payment references when you use account or wallet functions.

Why we use it

We use account and device data to complete sign-in, connect your wallet status, detect unusual access, answer privacy requests and keep records required for applicable legal duties.

Cookie controls

Cookies and similar storage can remember session settings and help us understand technical errors. Your browser controls can remove or restrict them, although sign-in features may then need another check.

Account security

Phone verification, sign-in records and device signals help us review access that does not match your normal account path. Do not share your password, one-time code or wallet PIN.

Retention approach

We keep each record only for the account, security, support or legal purpose that requires it, then remove or de-identify it according to our internal retention process.

Changes and contact

To request access, correction or deletion where local law permits, contact us through the support route shown in your account and describe the record you want us to check.

Browse Privacy Policy Questions Before Opening

These Privacy Policy answers cover the practical points you may check before creating an account. We focus on the records created by phone verification, mobile access, wallet use and support contact, so you can decide what to share. If your question is not listed, use the account privacy path and include only the details needed to locate your request.

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

We use the verification result to connect you with the correct account, reduce mistaken access and help investigate unusual sign-in activity. We do not need your password or wallet PIN for a privacy request.

Yes. It explains how device type, browser signals, session records and similar technical details may support sign-in, security checks and error handling when you use the mobile lobby.

We may retain transaction references, status details and receipt codes needed to connect a wallet action with your account, answer support questions and meet applicable legal duties. We do not need your wallet PIN.

Where local law permits, you can request a correction through the support contact shown in your account. Include the affected record and verified account details so we can confirm the request.

Retention depends on the record's account, security, support or legal purpose. We remove or de-identify records when that purpose ends, subject to duties that may require continued storage.

Sign in and use the support route displayed for your account. State whether you want access, correction, deletion where local law permits, or an explanation of a cookie or wallet record.