Reference

garasigame Privacy Policy for Your Account

garasigame keeps this Privacy Policy focused on the data you share when opening an account, signing in, checking wallet status or browsing titles such as Live Baccarat Gold…

Account dataDevice signalsWallet recordsYour requests
garasigame garasigame Privacy Policy for Your Account
HELP WITH REQUESTS

Get Clear Answers About Your Data

A clear contact route helps when a Privacy Policy question concerns a login, wallet reference or old account detail. Open the account help path and include the phone number or email linked to your profile, the topic of your request and any relevant reference without sending a password or full payment credentials. We use the details you provide to locate the right record and may ask for an account check before responding. If you are in Semarang, the same online route applies as it does across Indonesia.

Team online

Account help path

Use the help form connected to your account area for access, correction or deletion questions. Include your registered contact and request type so we can locate the correct profile without asking you to place a password or wallet PIN in a message.

Wallet status query

For a DANA, OVO, GoPay or QRIS record, send the transaction reference and displayed status through support. We compare that reference with the account event and payment response, while keeping card, wallet PIN and other secret credentials out of the request.

Security concern

If a login, phone verification step or device session looks unfamiliar, contact us through the account help route promptly. We may pause the conversation for identity checks, record the case, and explain the next account-security step without exposing private session data.

YOUR DATA CONTROLS

What Your Privacy Policy Covers

We handle this policy area through practical account controls rather than broad promises. Phone verification helps us connect an account request to the right profile, while session and device signals help us…

Collected account details

We may hold your registered contact details, phone verification result, login events and account preferences. These records help us identify your profile when you ask for a Privacy Policy action or need a status check beside the cashier path.

Device and session use

A mobile browser or desktop session can provide operating system, browser type, language, network indicators and page events. We use these signals to keep a session working and flag unusual access; they do not replace the account checks required for sensitive requests.

Cookies and storage

Cookies can retain a sign-in preference, support security checks and show which policy page was opened. You can clear or restrict them in your browser settings, although some account paths may then ask you to verify your phone again.

Payment matching

When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we record the rail, reference and status needed to match the event to your account. We do not ask for your wallet PIN or password in support messages.

Retention and removal

We keep account, support and payment-reference records for the period needed to operate the account, resolve a dispute or meet applicable duties. After that period, we remove or de-identify them where practical, subject to a valid retention requirement.

Requests and identity checks

To request access, correction or deletion, use the account help route and identify the profile involved. We may ask for phone verification or other reasonable proof before changing data, and the available action depends on local law.

Privacy Policy Questions for garasigame

These Privacy Policy answers address the questions you may have before opening an account or connecting an Indonesian wallet. We keep the wording practical: what is collected, why a device matters, how payment references are handled and where to send a request. When an answer depends on your location or a legal requirement, we say so directly and point you back to the account help route.

It covers data used for account creation, phone verification, login, device sessions, cookies, support and payment-status matching. It also explains retention, security handling and your request options for access, correction or removal where local law permits.

We use your phone number to create and identify the account, complete phone verification and help investigate an access request. It can also help us connect a wallet reference to the right profile, but you should never send a wallet PIN through support.

Yes. The Privacy Policy covers the payment rail, reference, amount status and related account event needed to reconcile DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. It does not require you to disclose a secret wallet PIN.

A browser session may provide device type, operating system, browser version, language, approximate network indicators and page events. We use those details for session continuity and security checks when you move from account login to the lobby on mobile or desktop.

Open the account help path and state whether you want access or a correction, then include the registered contact and relevant account detail. We may complete phone verification before responding, and the available scope depends on local law and required record retention.

You can send a removal request through support, and we will assess which records can be removed or de-identified. Some account, payment-reference or case records may need to remain for dispute handling or legal duties; the outcome depends on local law.

Use the account help route and describe the concern without including your password, wallet PIN or complete sensitive payment credentials. Add the page, account contact and any reference that helps us investigate. We will use that information to route the request correctly.