Reference

dtg288 Privacy Policy For Your Account

The dtg288 Privacy Policy explains how we handle your account details, phone verification, device access and wallet records before you enter the lobby.

Account dataWallet recordsDevice accessPolicy requests
dtg288 dtg288 Privacy Policy For Your Account
CONTACT PATHS

Browse Privacy Help Through Your Account

A clear contact path helps when you need an answer about the Privacy Policy rather than a lobby instruction.

Account privacy request Use the support contact shown after account access and state that your request concerns the Privacy Policy. Include the phone number connected to your account so we can locate the right record without asking you to repeat unrelated lobby details.
Wallet record question If your request concerns DANA, OVO, GoPay or QRIS activity, include the receipt reference and approximate transaction date. For bank transfer or virtual account checks, we use the reference you provide to separate payment records from general account activity.
Data change request Tell us which account detail appears incorrect and what change you are seeking. We may ask for phone verification before changing personal data, because confirming the account holder helps prevent another person from altering your profile.
DATA PRACTICES

Switch Through The Main Privacy Controls

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account details

We handle the phone number and account details you submit during the opening step so we can identify your profile and respond to a Privacy Policy request. We do not need unrelated lobby preferences to process a basic data-access question.

Phone verification

Phone verification is an account-security step before access and before some data changes. It helps us check that a request about your profile comes from the person connected to that account, especially when the request involves wallet status or contact details.

Cookies and sessions

Cookies may keep a necessary sign-in session active and help the site remember the device path you selected. You can manage browser cookie settings, but disabling required cookies may interrupt account access or make a Privacy Policy request harder to complete.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a receipt with an account query. Bank transfer and virtual account references serve the same checking purpose. We use the reference to investigate status, not as a substitute for phone verification.

Retention questions

We retain account, support and payment-check records for the period needed to operate the service, resolve disputes and meet applicable obligations. Ask us how a specific record is retained, and we will assess the request against account status and local law.

Correction or removal

You can ask us to correct inaccurate details or explain whether a record can be removed. Send the request through the account support contact, identify the affected data, and complete any verification we require before we act on the change.

Ask About The dtg288 Privacy Policy

These Privacy Policy answers address the questions we expect before you open an account or send a data request. They cover the account step, device behaviour, local wallet references and the contact route. If your situation is not listed, use the support contact connected to your account and describe the record you want us to locate.

The dtg288 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references. It explains why we use those records, how retention works, and how you can ask about access, correction or removal where local law permits.

We use your phone number to create and identify your account, complete phone verification, and help prevent unauthorised changes. It also gives our support team a way to locate the correct profile when you ask about the Privacy Policy or a wallet-related record.

Yes. The policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account checks. We use those references to match a receipt or status question with the right account and investigate a mismatch.

Use the support contact shown through your account and state that you are making a Privacy Policy data request. Identify the account phone number and the records you want us to locate. We may request phone verification before releasing account-linked details.

You can ask us to correct inaccurate account details or explain whether a record can be removed. Describe the specific data and the requested change through the account support route. We assess each request against security needs, retention duties and where local law permits.

Required session cookies can affect sign-in and the mobile path used to reach your account contact. If you block them, you may need to sign in again or use another device. The Privacy Policy still applies, and support can explain the next account step.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains how we handle data when you use the available account path, but it does not change local requirements. Check your local position before opening an account or sending payment records.