Reference

Privacy Policy For Your ducati388 Account

The ducati388 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access the lobby from your phone or desktop.

Account dataWallet recordsCookie choicesAccess depends on local law
ducati388 Privacy Policy For Your ducati388 Account
CONTACT ROUTES

Get Privacy Help From Your Account Path

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel. Start from the account support path when you need a copy of your stored details, want to question a wallet record, or need help with a sign-in verification issue. Tell us the account phone number and subject of your request, but do not send a password or full payment credentials.

Team online

Account access

If your phone verification does not open your account, use the account support path and state that your request concerns the Privacy Policy. We can match the request to the relevant account record without asking you to disclose your password.

Wallet records

For a DANA, OVO, GoPay, or QRIS reference that appears incorrectly, include the date, amount, and visible reference shown in your account. We use those details to locate the record while keeping your wallet login and security codes private.

Data requests

To ask for access, correction, or deletion under the Privacy Policy, send the request through the available account contact route. We may ask for an account check before changing personal details or disclosing stored records.

DATA CONTROLS

What We Do With Your Account Data

Privacy at ducati388 is managed through practical account and payment controls rather than broad promises. We separate identity details from wallet references where operationally possible, restrict account changes behind verification, and use…

Account details

We collect details needed to create and maintain your account, such as your phone number and verification result. These details let us associate sign-in activity with the correct account and prevent a requested change from being applied to the wrong record.

Device signals

When you move from phone login to a desktop browser, our systems may record device and browser signals linked to the session. We use these signals for access checks and unusual activity detection, not as a substitute for your account credentials.

Cookie settings

Cookies can remember session state and help us understand whether a page request belongs to an active account. You can manage cookies through your browser settings, though disabling necessary cookies may interrupt sign-in or the Privacy Policy request path.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account action can create a reference, status, and timestamp. We use that payment record to reconcile your account activity and investigate a disputed status without storing your wallet password.

Account security

Phone verification and session checks help protect access before account details or wallet status are changed. Keep your verification codes private, sign out on shared devices, and contact us promptly if a sign-in or payment record is not yours.

Retention and changes

We retain personal and transaction records only as long as needed for account operation, security checks, dispute handling, or applicable legal duties. You can request correction or ask what records we hold through the account contact path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening access from Indonesia. We explain the data connected with phone verification, wallet references, cookies, device changes, and requests for access or correction. Where local law permits, you can use the account contact route to ask for a case-specific response.

The ducati388 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, security checks, retention, and requests to access or correct personal data. It applies when you create an account, sign in, use a wallet route, or contact us about your records.

We use your phone number to create or identify your account and to complete the account access check. It helps us connect a support request to the correct record. Keep verification codes private, because our Privacy Policy does not make those codes public or share them as ordinary account details.

Yes. The Privacy Policy covers the payment references, statuses, and timestamps connected with DANA, OVO, GoPay, and QRIS activity on your account. We use these records to reconcile an account action or investigate a disputed status, while your wallet password and security code remain outside our request path.

A phone, tablet, or desktop browser can create device and session signals when you sign in. We use them to check access and identify unusual activity. The Privacy Policy treats those signals as security data linked to the session, not as a replacement for your phone verification or account credentials.

Use the available account contact route and state whether you want access to stored records or correction of a specific detail. Include the account phone number and request subject, but never send a password or full wallet credentials. We may verify account ownership before releasing or changing personal data.

We keep payment references, statuses, and related account records for the period needed for account operation, security checks, disputes, and applicable legal duties. The exact period can depend on the record type and local requirements. You can ask through the account contact route how a particular record is handled.

Yes. Ask through the account contact route if you need clarification about cookies used for session state or page measurement. You can also adjust browser cookie settings. Necessary cookies may be required for sign-in and policy requests, so disabling them can prevent the account path from working correctly.