Reference

Privacy Policy For Your sastoto Account

Our Privacy Policy explains what we collect when you open a sastoto account, sign in from a phone or desktop, and use account services where local law permits.

Account dataWallet recordsCookie choicesSecurity requests
sastoto Privacy Policy For Your sastoto Account
ACCOUNT HELP ROUTES

Get Privacy Policy Help Before You Proceed

A clear contact path helps when you want to understand a data record, correct an account detail or ask why a wallet status is connected to your account history. Our support route is focused on privacy questions rather than general lobby assistance. Include the account contact used for sign-in, the relevant date and the request you want us to assess. Do not send a password or full payment credentials. We may ask for account verification before discussing private records, including requests made from a phone used in Bandung or another Indonesian location.

Team online

Account data request

Use the account support path to ask what personal details are linked to your sastoto profile. Include your sign-in contact and a clear request for access or correction; we verify ownership before sharing account-specific records.

Wallet record question

If a DANA, OVO, GoPay or QRIS status appears unfamiliar, tell us the payment rail, date and visible reference. We can check the account record without asking you to disclose a password, card number or complete wallet credentials.

Cookie preference request

Ask through the privacy contact path if you need help understanding cookies or changing a browser choice. Tell us which device and browser you used, because a preference saved on mobile may not match one saved on desktop.

HANDLING YOUR DETAILS

What Our Privacy Policy Covers In Practice

The practical side of our Privacy Policy is simple: we connect each data use to an account, security, payment or service purpose.

Data we receive

We may receive the contact details you enter for account creation, phone verification results, sign-in records and messages sent through support. Payment actions can add DANA, OVO, GoPay, QRIS, bank transfer or virtual account references to the account history.

Why we use it

We use account details to create access, check ownership and respond to your request. Payment records help us match a status or receipt, while device and session signals help identify unusual sign-ins. Each use should relate to account operation, security or support.

Cookies on your device

Cookies can remember necessary session settings and selected preferences so a sign-in flow works across the pages you open. A choice made in a mobile browser may not carry to desktop, so check the cookie controls again when changing devices.

Account security

Phone verification is requested before account access, and we may compare sign-in signals with earlier activity when protection is needed. Never share a password or verification code in a support message. We use ownership checks before discussing private account details.

Retention approach

We keep records only for as long as needed for the purpose described in this Privacy Policy, account support, security checks or applicable legal duties. The period can differ by record type, so ask us to clarify retention for a specific account or payment reference.

Changes and contact

You can ask us to correct account details, explain a data use, provide eligible access or address a privacy concern through the account support path. Include enough context to locate the record, but remove passwords, full wallet credentials and unnecessary identity details.

Privacy Policy Answers For sastoto Accounts

These Privacy Policy answers address the practical questions that come up before account access: what is collected, how wallet records are treated, what cookies do and how to contact us. We keep the answers tied to the account flow rather than describing unrelated games or general platform features. If your question concerns a specific record, include its date and payment reference when you contact support.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your choices and how to ask about access, correction or retention.

Phone verification helps us confirm that the person requesting account access controls the submitted contact. It can also support account recovery and security checks. We may ask for additional ownership details before discussing private records, but you should never send a password or verification code.

Yes. The Privacy Policy covers payment status and reference data connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account actions. These records help us match a requested account transaction or investigate a status question without needing full wallet credentials.

Contact us through the account support path and state that you want a copy of eligible data linked to your profile. Provide the sign-in contact and a useful date or reference. We verify ownership first, then explain what can be supplied under applicable requirements.

Yes. Send a correction request through the privacy contact path and identify the account detail that is inaccurate. We may ask you to confirm ownership before making a change. Do not include a password, verification code or complete DANA, OVO, GoPay or QRIS credentials.

Necessary cookies can support a sign-in session and page settings, while preference cookies can remember choices in your browser. A mobile setting may not apply on desktop. Use the available cookie controls or contact us if you need help understanding or changing a choice.

Retention depends on the type of record and the reason it was collected. We may keep account, security or payment references for support, protection and applicable legal duties, then remove or anonymise them when no longer needed. Ask us about a specific record for a clearer response.