Reference

potatoto Privacy Policy for Your Account

Our Privacy Policy explains how we use the account details, device signals and wallet records connected with your potatoto access.

Account dataWallet recordsCookie choicesYour privacy requests
potatoto potatoto Privacy Policy for Your Account
PRIVACY HELP ROUTES

Get Privacy Help Near Wallet Status

A clear contact route matters when a privacy question arrives alongside a stalled login or wallet status.

Account privacy request Send your request through the account support path and identify the phone number used…
Wallet record question For DANA, OVO, GoPay, QRIS or bank transfer references, include the transaction reference rather…
Login and device concern If a new device shows an unfamiliar sign-in or cookie choice, tell us the…
YOUR DATA PATH

Account Security Behind Live Roulette Access

We handle this policy area through ordinary account controls rather than vague promises. Phone verification helps connect a request to the correct account, while device and sign-in records help us investigate access…

Data we receive

We may receive your account contact details, phone verification result, sign-in events, device signals and payment references. We use only the data needed to provide account access, answer requests and check account safety.

Cookie controls

Cookies can keep a session active, remember a selected setting and help us understand technical failures. Your browser controls can limit cookies, although changing them may affect login continuity or lobby display.

Account protection

We use phone verification and sign-in checks to reduce mistaken account access. Never send your password, wallet PIN or one-time code in a privacy request, even when asking about DANA or QRIS.

Record retention

We retain account, security and payment records only as needed for the stated service, dispute handling, safety checks or legal duties. The applicable period can depend on the record type and local law.

Sharing boundaries

We may share relevant data with service providers that help process access, security or payment references. We limit the request to its purpose and do not ask a provider for your private wallet PIN.

Requesting changes

You can ask us to correct an account detail, explain a recorded item or assess a deletion request through support. Include the verified account contact so we can protect your records from an unknown requester.

Privacy Policy Questions for Indonesia Accounts

These answers focus on the questions we expect before you open an account or connect a local wallet. They explain the practical route for data access, corrections, cookies and payment records, while the full Privacy Policy remains the controlling text where local law permits.

It covers account details, phone verification, device and sign-in events, cookies, lobby activity connected to your account, payment references and the ways we respond to privacy requests.

Phone verification helps us connect account access and privacy requests to the correct person. It also supports account safety when a sign-in or device event needs checking.

No. We may retain a DANA or QRIS reference and processing status for account support, but you should never send a wallet PIN, password or one-time code to us.

Use the support route inside your account and identify the verified phone or email connected with access. We will explain the available data request process where local law permits.

Yes. Send a correction request through support with the affected account detail and verified contact. We may ask for an account step before changing records linked to payments or access.

Your browser can limit or remove cookies, but login continuity, saved settings or some lobby displays may change. The Privacy Policy explains why each cookie category is used.

Retention depends on the record, support need, security check and legal duty. DANA, OVO, GoPay, QRIS and bank transfer references may therefore follow different periods.