Reference

sagatoto Privacy Policy For Your Account

Our sagatoto Privacy Policy shows how we handle the account details connected with DANA, OVO, GoPay and QRIS, from phone verification through wallet status checks.

Account dataWallet recordsCookie choicesMobile access
sagatoto sagatoto Privacy Policy For Your Account
CONTACT ROUTES

Privacy Policy Help Beside Your Account

A clear support route matters when you want to ask about personal data rather than a lobby feature. From your logged-in account, open the support area and describe the exact request, such as a phone change, wallet reference question or copy of stored account data. We may ask for account details needed to locate the correct record, but we will not ask you to send a password or one-time security code.

Team online

Account help

Use the account support route when your Privacy Policy question concerns phone verification, sign-in records or a request to correct the name and contact details attached to your account.

Cashier status

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, include the transaction date and account identifier so we can check the related record without requesting your wallet password.

Policy request

Tell us whether you want access, correction, deletion or a processing question answered. We will review the request against account security needs and the rules that apply where local law permits.

DATA PRACTICE

How Our Privacy Policy Handles Your Data

We keep this policy tied to actions you can recognise: opening an account, confirming a phone number, entering the lobby from a mobile device or checking a wallet reference.

Data we receive

We may receive your phone number, account details, verification responses, device type, browser session and payment reference. DANA, OVO, GoPay and QRIS details are used as transaction context, not as a request for your wallet password.

Why we use it

Account data supports phone verification, sign-in continuity, wallet matching and security checks. A device path from login to the lobby may also be recorded to detect unusual access and keep your account session from being misused.

Cookie controls

Cookies can remember a session and help us understand whether a login step has completed. You can manage browser cookie settings on your phone or computer, although disabling necessary cookies may interrupt account access.

Account security

Keep your password and verification code private, and sign out on a shared device. We may compare account, device and wallet signals before changing sensitive details, including a phone number or withdrawal destination.

Retention approach

We keep records only for as long as needed for the stated account, security, transaction or legal purpose. Retention can differ by record type, so a payment reference may remain after a browser session has ended.

Changes and contact

You can ask us to access, correct or delete eligible data through account support. We may need identity checks before acting, and some records may remain when retention is required where local law permits.

Privacy Policy Answers For sagatoto Accounts

These Privacy Policy answers cover the searches we expect you to make before opening an account or checking a wallet record. We focus on the practical points: what is collected, how mobile access works, which payment references may appear, how to request a change and what happens when local rules affect access. If your situation is not listed, use the policy request route with your account identifier.

It covers data linked to your account, phone verification, device sessions, cookies and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your access, correction and deletion request options where local law permits.

We use your phone number to create and protect account access, complete the clear phone verification step and help locate the right record if you contact support. Keep the number current, and request a correction through account support if it changes.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match a cashier event to your account, not to request your wallet password.

Cookies can keep your login session active and help confirm that a mobile step, such as moving from account access to the lobby, has completed. You can manage cookies in your browser settings, but necessary changes may prevent the account path from working.

You can request a correction through the logged-in support route and state which account detail is wrong. We may ask for verification before changing a phone number, wallet reference or identity detail, because account protection remains part of this Privacy Policy.

We retain each record for the period needed for its account, security, transaction or legal purpose. A completed mobile session may end quickly, while a payment reference or verification record can remain longer when required for account protection or where local law permits.

Yes. Access or eligibility depends on local law. If a local rule affects your account or a data request, we will assess the applicable requirement before responding. You can still contact us through account support to ask which part of the policy applies.