Reference

familytoto Privacy Policy for Indonesia Accounts

Our familytoto Privacy Policy explains what account details we collect, why we use them and how you can ask about their handling.

Clear data purposesCookie choicesPayment referencesAccount requests
familytoto familytoto Privacy Policy for Indonesia Accounts
PRIVACY SUPPORT

Get Privacy Help Near Your Account

A clear contact path matters when a privacy question appears beside a login or wallet status issue. Start from the support route shown in your account area and include the phone number or account identifier connected with your request. We use the details you provide to locate the right record, check a payment receipt or status, and respond without asking you to send a wallet password.

Team online

Account data request

Ask us which account details are held, why they are used and which login or phone verification record matches your familytoto account. Include enough account context for us to check safely.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction reference and date through the account support route. We can check the recorded method and status.

Change or removal request

You can ask about correcting outdated account details or removing data that no longer needs retention. We may first confirm account ownership before changing records or discussing restricted details.

DATA PRACTICES

Cookies, Security and Data Choices

We keep this policy practical: each data category has a purpose tied to account access, payment matching, security or support.

Account details

We use the details you enter during account creation and phone verification to identify your account, restore the correct access path and respond to requests about your own records.

Device signals

When you sign in from a mobile browser or desktop, we may record device, browser and session signals. These help us spot unusual access without reading private wallet passwords.

Cookies

Cookies can keep a session connected, remember selected settings and help us understand whether a page request worked. Your browser controls can limit cookies, although some account steps may then need repeating.

Account security

Phone verification and session checks help protect account access. Never send a password, wallet PIN or one-time code through support; we use account details and references to confirm a request.

Retention period

We retain account, support and payment-reference records only for as long as needed for the stated purpose, account protection or applicable legal duties. You can ask why a record remains stored.

Your request path

To request a copy, correction or explanation, contact us through the support route connected with your account. We may verify ownership before releasing, changing or discussing personal records.

Privacy Policy Questions About Your Account

These answers cover the questions we expect before an account is opened or a payment record is checked. If your situation is not listed, use the account support route and describe the specific record or request.

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

We use the phone verification status to connect you with the correct account and protect access when a request is made. It also helps us distinguish account records during support checks.

Yes. The Privacy Policy covers the method label, reference, date and status needed to match a DANA or QRIS account action. It does not require your wallet password or PIN.

Use the support route shown in your account and ask for a copy of the personal records connected with your account. Include your account identifier; we may verify ownership first.

Yes. Send a correction request through the account support route and identify the outdated detail. We check ownership before changing records, especially where the request affects phone verification or payment matching.

Cookies can keep your mobile session active, remember settings and confirm that account pages load correctly. Browser controls can restrict them, but login or account steps may need to be repeated.

Yes. Access and eligibility depend on local law. Where local law permits, you can contact us about stored data, correction, retention or the handling of a specific account or payment reference.