Reference

Legal clarity before you join sgtoto

sgtoto puts account terms, eligibility wording, privacy requests and wallet record rules in one place, so you know what applies before you open an account.

Account termsPrivacy requestsDANA record contextAccess depends on local law
sgtoto Legal clarity before you join sgtoto
CONTACT PATHS

Three ways to reach legal support

Legal questions need a traceable path, not a vague chat reply. We route account-term questions, privacy requests and payment-record checks through channels that leave a reference number. You can start from Help, email us, or open the message panel after login. Our team reads English requests for Indonesia accounts and may ask for your username, registered phone number and Wallet History reference.

Team online

Live chat window

Use the Help bubble daily from 09:00 to 23:00 WIB for first contact. Ask for a legal request tag, then keep the chat reference if your question involves account terms, DANA records or access wording.

Email record desk

Send longer privacy or correction requests to the legal contact address shown inside your account area. Include your username, registered email and the date range, but never send your password or full wallet PIN.

Logged-in ticket

Open Account → Help → Legal request when you need a status trail. This path links your message to session logs, QRIS receipt checks and earlier replies without exposing private details in public channels.

ACCOUNT CARE

Six controls behind our legal process

Your legal request is handled with account evidence, not guesswork. We check login history, payment references, cookie consent choices and security events before we answer.

Data we collect

We keep registration details, login timestamps, device signals and wallet references needed to run your account. Payment labels such as DANA, OVO, GoPay and QRIS help us match a legal question to the right record.

Cookie choices

Cookies keep sessions active and help us spot repeated failed logins. You can clear them in your browser, but we may ask you to pass account checks again after the next login.

Account security

Change your password from Profile → Security if you think another person saw it. Our team will not ask for that password, and legal requests are handled through chat, email or logged-in tickets only.

Record retention

We keep account and wallet records for operational, dispute and legal reasons. Retention length can vary by record type, and we remove or mask data when it is no longer needed for those reasons.

Correction requests

If your name, phone number or email is wrong, contact us before opening a withdrawal request. We may ask for account screenshots from your own page to confirm the change path.

Access decisions

Access may be paused when eligibility depends on local law, account details conflict, or a payment reference cannot be matched. We explain the next account step through the same channel you used.

Legal questions before account access

The questions below focus on your rights, our records and the steps we use when a legal issue reaches us. They are written for practical account handling: where to ask, what to include and what we can change. If your question involves a payment rail, include the DANA, OVO, GoPay or QRIS reference shown in Wallet History.

Our account terms apply when you create login details, accept the account flow and use the wallet. Access depends on local law, and we may request confirmation if your location or account details need checking.

Start from Account → Help → Legal request after login, or email the address shown in your account area. Include your username, registered phone number and the date range you want us to check.

Yes, you can ask us to correct details that are incomplete or outdated. We may verify your request through Profile → Security, a registered email reply or a recent Wallet History reference.

We keep wallet references, timestamps, status labels and payment rail names such as DANA, OVO, GoPay and QRIS. These records help us answer disputes, account checks and legal requests without asking for private wallet passwords.

Cookies do not remove your request rights, but they help us link a session to your account. If you clear cookies, we may ask you to log in again before we can confirm the record.

A support handler first tags the request, then the account team checks records tied to your profile. For privacy or correction matters, we answer through chat reference, email or the logged-in ticket path.

Yes. We may pause or refuse access where local law permits, when account details conflict, or when a payment reference cannot be checked. We will state the next account step through your chosen contact channel.