Reference

Privacy Policy for Your tiles slot Account

Our Privacy Policy explains how tiles slot handles the details connected with your account, including phone verification, wallet status and lobby access.

Clear data purposesPhone verification detailAccount access choicesIndonesia policy wording
tiles slot Privacy Policy for Your tiles slot Account
CONTACT THE TEAM

Contact Routes for Privacy Questions

A direct contact route helps you ask what we hold, why we use it or how to correct an account detail.

Account contact route Use the contact path attached to your signed-in account for a privacy request. We can use your verified phone number and account identifier to locate the correct record without asking you to share a password or one-time code.
Wallet data question If your request concerns DANA, OVO, GoPay or QRIS activity, tell us the date and reference shown in your account. We use that narrow detail to check the record while avoiding unnecessary wallet credentials or unrelated account history.
Access issue When a privacy request is blocked by login trouble, explain the account step that stopped you, such as phone verification or a device change. We will direct the matter to the account support route before discussing personal data.
DATA HANDLING

Account Data Controls at tiles slot

We handle privacy as an account process rather than a message hidden behind the lobby.

What we collect

We may receive your phone number, account details, sign-in timestamps, device or browser signals, support messages and payment references. For DANA, OVO, GoPay, QRIS and bank transfer activity, we use the reference needed to connect an account action with its status.

Why we use it

We use account data to complete phone verification, maintain access, investigate an unusual sign-in, respond to a privacy request and reconcile a payment reference. We do not treat your game or lobby activity as a reason to collect unrelated personal details.

Cookies and devices

Cookies and similar device signals can keep a session working, remember security settings and help us identify repeated login failures. You can manage browser cookies through your device settings, although changing them may interrupt account access or require phone verification again.

Account security

Phone verification is part of the account access path, and we may review sign-in or device changes when activity looks unusual. Keep your password and one-time codes private; our support route will not ask you to place either one in a privacy message.

Retention choices

We retain records for the operational purpose that created them and for any period required by applicable law. You can ask us which categories remain, why they remain and whether deletion or de-identification is available for the specific record.

Requests and corrections

You can ask us to access, correct or explain personal data linked to your account. Send the request through the account contact route with a clear description; we may confirm your identity before making a change or sharing account-linked details.

Privacy Policy Questions About Your Account

These answers address the searches we hear most often about the tiles slot Privacy Policy. They focus on account records, device access, local wallet references and requests for action. If your situation is not covered, use the account contact route and describe the exact record or login step involved. Access remains subject to local law.

It covers information connected with your account, including phone verification, sign-in events, device signals, support messages and payment references. It also explains cookies, security use, retention and how to request access or correction where local law permits.

Yes. The Privacy Policy explains how we handle references connected with DANA, OVO, GoPay and QRIS activity. We use those references to match an account action or status, not to request or store your wallet password or one-time code.

Use the contact path attached to your signed-in account and state that you want an account data request. Include your account identifier or verified phone number, then describe the categories you want checked. We may verify your identity before responding.

You can ask us to correct inaccurate account details through the account contact route. Tell us which field is wrong and what should replace it. We may request verification, especially when the change affects phone access, wallet status or account security.

Device and browser signals can help keep a session active, remember security settings and identify unusual login patterns. They also help us investigate repeated access problems. Cookie controls are available in your browser, but changing them may trigger another phone verification step.

Retention depends on why the record was created and on applicable legal duties. Account, support and payment-reference records may therefore have different periods. You can ask us which category remains, the reason for keeping it and whether removal or de-identification is available.

Where local law permits, you can request deletion or de-identification of specific personal data through the account contact route. We first check the request and any duty to retain a record, then explain what action is available and why some data may remain.