Reference

Open GAS1M With Privacy In View

GAS1M Privacy Policy explains how we handle your account, device and wallet details when you browse Sic Bo, Aviator or other lobby areas.

Account clarityWallet awarenessDevice controlsLocal-law access
GAS1M Open GAS1M With Privacy In View
CONTACT ROUTES

Reach Support About Your Privacy

A clear contact path matters when you want to ask about a stored detail, correct an account record or understand a wallet reference.

Account privacy request Use the support path beside account access to ask what phone or verification details are linked to you. We may ask for an account step that confirms the request belongs to you.
Wallet record query For a DANA, OVO, GoPay or QRIS reference, send the receipt or status context through support. We use that reference to locate the relevant payment event without requesting your wallet password.
Device access concern If a mobile browser or desktop sign-in looks unfamiliar, tell us the device path and approximate access time. We can review the account event and explain the privacy step available.
DATA PRACTICE

Secure Your Account Data Path

We keep this Privacy Policy practical: it explains what reaches our systems, why we use it and how you can ask for a change.

Account creation

When you open an account, we receive the details required for the account path, including your phone number and verification result. We use them to recognise your account during later access.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account. We do not need your wallet password to check that event.

Cookies and sessions

Cookies and session records can remember a sign-in state or device preference. You can clear browser cookies, but doing so may require another account verification step on your next visit.

Device security

A mobile browser and a desktop browser can create separate session records. If access does not look familiar, contact support with the device path so we can examine the account event.

Retention period

We keep account, payment and support records for as long as needed for account operation, payment disputes or legal duties. When a record is no longer needed, our handling moves toward removal.

Change request

You can ask us to correct an inaccurate phone, contact or account detail through the support route. We may verify ownership before changing records connected with wallet or account access.

Find Privacy Policy Answers

These Privacy Policy questions address the account steps Indonesian customers ask about most often. Each answer stays focused on data handling, wallet references, device access and the contact route available through GAS1M when you need a correction or clarification.

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

Phone verification helps connect an account access request with the correct account and helps us examine unusual sign-ins. We use the result for account security and do not treat it as a wallet password.

Yes. The policy includes QRIS, DANA, OVO and GoPay references, along with bank transfer and virtual account records. These references help us check payment status without storing your wallet password.

Yes. Contact support through the account path and identify the detail that needs correction. We may request an account verification step before changing a phone, contact or payment-linked record.

Cookies can remember a session or device setting when you use a mobile browser. Clearing them may sign you out and require phone verification again when you return to your account.

We retain records while they support account operation, payment disputes, support handling or legal duties. Once a record is no longer needed for those purposes, we move toward removal.

Use the support route beside account access or the cashier path. Include your account context and, when relevant, a receipt or device reference so we can direct the Privacy Policy request correctly.