Reference

ids388 Privacy Policy for Your Account

ids388 Privacy Policy explains how we handle your account details, device signals, cookies and wallet records while you browse Auto Roulette, Sugar Rush or other lobby areas.

Clear data purposesWallet record contextPhone verification pathLocal access wording
ids388 ids388 Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Near Wallet Support

A clear contact path matters when you want to ask about a privacy record rather than a wallet result.

Data access request Ask us what account details, device signals or payment references we hold by using…
Correction request If your phone detail, wallet reference or account record looks wrong, send the specific…
Privacy contact Questions about cookies, retention or a prior request can be directed to the same…
DATA HANDLING

What This Privacy Policy Covers

We separate the data needed to operate an account from optional signals that help a page load correctly on your device.

Account details

We may hold your name, phone number, login record and verification result because these details connect you to the correct…

Device signals

A phone or desktop session can provide browser, operating system, approximate network and login-event details.

Cookies

Cookies can keep a session active, remember a selected language setting and measure whether the privacy page opened correctly.

Account security

Phone verification, login events and payment references help us check that an account request belongs to you.

Retention periods

We keep account, verification and wallet records for as long as needed for the stated purpose, account support and applicable…

Changes and requests

You can ask to access, correct, restrict or delete eligible personal data through account support.

Privacy Policy Questions About ids388

These Privacy Policy answers address the searches we hear most often about account records, local wallets, cookies and access. If your situation involves a particular DANA receipt, device session or phone verification step, use the account support contact so we can assess the exact record. Access and eligibility depend on local law.

The ids388 Privacy Policy covers account details, phone verification, login events, device signals, cookies, payment references and support requests connected with your account and access where local law permits.

We record the payment rail, reference, amount, time and status for DANA or QRIS so we can match a receipt to your account, check a wallet issue and keep an accurate transaction record.

Yes. The Privacy Policy covers records created when you use OVO or GoPay, including the selected rail, account reference and status. We do not request unrelated content from either wallet.

Use the support contact shown inside your account and ask for a data access request. Include your verified phone number and the record type you want checked, such as login or payment history.

You can request a correction through account help by naming the inaccurate field and explaining the change. We may ask for phone verification or a matching receipt before updating the account record.

Cookies can maintain your login session, remember a language choice and show whether a policy page loaded. Browser controls let you manage them, but removing cookies may require another account verification step.

Send a retention question through the support route displayed after login, naming the account record involved. We explain the applicable purpose and period, subject to legal duties and local-law requirements.