Reference

Open the ducati666 Privacy Policy

The ducati666 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Account dataWallet recordsDevice controlsSupport requests
ducati666 Open the ducati666 Privacy Policy
CONTACT ROUTES

Ask About Your Privacy Request

A clear contact path helps you resolve a Privacy Policy question without exposing account details in an open message. Use the support link beside the account and cashier path, then identify the phone number or account reference connected with your request. We use that step to confirm who is asking before discussing stored data, wallet records or device activity. Keep payment receipts available when your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Team online

Account privacy

Use the support path beside your account area to ask what personal details are connected with your profile. We may request your registered phone number or account reference before discussing the request, so private account details are not disclosed to an unverified contact.

Wallet records

For a privacy question involving DANA, OVO, GoPay or QRIS, include the transaction reference and approximate date shown in your receipt. We use those details to locate the relevant record while keeping your full wallet credentials out of the support conversation.

Access concerns

If a sign-in or phone verification step appears unfamiliar, contact us through the account support route before sharing another document or payment detail. We can check the session context, explain the next account step and help separate a privacy concern from a wallet status issue.

DATA PRACTICE

Explore Our Privacy Handling

Privacy decisions are tied to practical account events rather than broad statements. We handle the details needed to verify access, connect wallet activity with your account and respond to a request about…

Data we receive

During account creation, we may receive your phone number, verification response and details you submit for account support. Sign-in events, selected lobby activity and payment references can also create records. We use each category for the account, transaction or support purpose connected with it.

Cookies and sessions

Cookies can keep a signed-in session working while you move from the account area to a lobby. Device signals may help us recognise an active session or flag unusual access. You can manage browser cookie settings, though changing them may interrupt verification or account continuity.

Account security

Phone verification is part of the access path before we discuss account details. We use account references, session context and relevant payment records to check a request. Do not send a wallet PIN or password through support; those credentials are not needed for a Privacy Policy query.

Payment records

A DANA, OVO, GoPay or QRIS reference helps us identify the payment event linked to your account without requiring full wallet login data. Bank transfer and virtual account records are handled for matching, status checks, dispute handling and any period required by applicable local rules.

Retention choices

We keep personal data for the period needed to provide account access, settle a payment question, address misuse or meet an applicable legal requirement. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identification.

Change or access request

You can ask us to explain the data connected with your account, correct an inaccurate detail or request deletion where eligible. Send the request through the account support route and complete the identity check. We will explain any restriction when local law requires a record to remain.

Find Privacy Policy Answers

These Privacy Policy questions cover the account, wallet and device situations most likely to matter before you open access. We keep the answers specific to ducati666 and to the records created when you use the service from Indonesia. For a request about your own data, the support route and identity check still apply.

The ducati666 Privacy Policy covers account details, phone verification, sign-in and device records, payment references, cookies and support conversations. It explains why we use each category, how long records may remain and how you can ask for access, correction or deletion where local law permits.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match an account event, check payment status and handle a dispute without requesting your wallet PIN.

Phone verification helps us confirm account access before we discuss personal details or wallet activity. It also helps us distinguish your request from an unfamiliar session. If verification does not match, use support beside the account path and do not send a password or wallet credential.

You can submit a Privacy Policy request through the account support route and ask us to describe eligible records linked with your profile. We may verify your registered phone number or account reference first. Where local law permits, we can also explain correction or deletion options.

On a mobile browser, cookies may keep your session active while you move from phone verification to the lobby. Device signals can support session and security checks. You can change browser settings, but blocked cookies may require another sign-in or interrupt the account access path.

We retain account, payment and support records for the period needed to provide access, resolve disputes, investigate misuse or meet an applicable legal requirement. When those purposes end, we remove the record or separate it from direct identification, subject to rules that require continued retention.

The Privacy Policy is available for questions about our data handling, but service access depends on local law and is provided where local law permits. Your location may also affect which account or payment steps apply. Contact support if you need a location-specific privacy clarification.