Reference

Open the Privacy Policy Before Account Access

sutra388 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or use DANA and QRIS.

Account clarityWallet recordsDevice controlsPolicy requests
Browse the lobby Read FAQ
sutra388 Open the Privacy Policy Before Account Access
ASK OUR TEAM

Contact Support About Privacy Questions

Privacy questions should follow the same account path used for login or wallet status help, so we can confirm which record you mean before discussing it.

Account privacy request Use the account help path when you need a copy of personal data, want to correct a phone detail, or need clarification about information connected with your sutra388 profile.
Wallet record question Ask us to trace the privacy meaning of a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference. We will ask for account context rather than your wallet password.
Security concern If a login, device, or verification event looks unfamiliar, use the support path beside account access. We can explain the recorded event and guide you through the next account-security step.
DATA PRACTICE

Explore Our Account Data Controls

We handle this policy area through practical account controls rather than broad statements. The sign-in path can create device and session records, while wallet activity creates payment-status references needed to match account…

Account details

We use the phone number and verification information you provide to identify your account and respond to account requests. If a detail changes, contact us through the account path so the correction reaches the right record.

Cookie choices

Cookies and similar browser signals can remember session settings and help us detect unusual sign-in behaviour. Your browser controls can manage cookies, although changing them may affect how the account access path functions.

Device signals

When you move from a phone login to the lobby, we may record device type, browser details, session timing, and security events. These signals help us investigate access concerns without asking for your private wallet credentials.

Wallet references

DANA, OVO, GoPay and QRIS activity can create references showing a payment request or status. We use those references to match support questions, not to request your wallet PIN, password, or one-time code.

Retention requests

We keep records for the period needed for the stated purpose or applicable requirements, then assess whether they should be removed or retained. Ask us for the category, purpose, and retention position connected with your request.

Change contact

To request access, correction, deletion, or another available privacy action, use the account support route and identify the relevant phone number. We may need account verification before sharing or changing personal information.

Find Privacy Policy Answers Quickly

These Privacy Policy answers cover the questions we expect you to ask before opening an account or checking an existing record. We keep the route practical: identify the account, name the data category, and use support when you need a response. Payment references, device details, cookies, and account verification each have a different purpose in our handling process.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support requests, and payment-status references. It explains why we use each category, how access is restricted, how retention is considered, and how you can ask about correction, deletion, or another available right.

Yes. When you use DANA or QRIS, we may receive a reference and status connected with the account request. The Privacy Policy explains that these records help match payment questions and account support. We do not ask for your wallet PIN, password, or one-time code.

Use the account support path and state that you want a copy of the personal data linked with your profile. Include the phone number attached to the account, but never include a password or one-time code. We may verify account ownership before releasing information.

You can ask for a correction through account support. Tell us which detail is inaccurate and provide the phone number connected with the profile. We may request an account check before changing it, because a corrected record must belong to the right account.

Cookies and related browser signals can preserve a session setting and help identify unusual sign-in behaviour. Your browser settings can control cookies. If you limit them, parts of the account access path may not work as expected, and support can explain the effect.

We retain each category for the period needed for its stated purpose or applicable requirements. The period can differ for account verification, wallet status, security events, and support records. Ask us to identify the category and explain its current retention position.

You may request deletion or another available privacy action through account support. We will assess the request under the Privacy Policy and local requirements, then explain any limit before proceeding. Access or eligibility depends on local law, so the result can vary by request.

Related Pages

sutra388 Indonesia Account information sutra388 Casino Access guide Champions League Mix Parlay