Reference

Privacy Policy for Your marjan989 Account

The marjan989 Privacy Policy shows what we collect when you open an account, verify your phone and move between the lobby and wallet page.

Account dataWallet referencesDevice signalsPrivacy requests
Explore Our Lobby Read FAQ
marjan989 Privacy Policy for Your marjan989 Account
CONTACT ROUTES

Ask About Privacy Near Your Account

A clear contact path helps when you want to know what the Privacy Policy means for your own account. Start from the support route linked beside the cashier area and include the phone number or account identifier you used during verification. We may ask for enough detail to locate your request, but never ask you to send a wallet password or a full payment credential. Your request is handled as a data matter, not as a lobby enquiry.

Team online

Account support

Use the support link beside the cashier path for a Privacy Policy question about your account record, phone verification or login history. Include the email or phone detail attached to the account so we can locate the correct record without asking you to repeat sensitive wallet credentials.

Wallet status

For a DANA, OVO, GoPay or QRIS data query, send the transaction reference and date shown in your account history. We use that reference to check the matching status while limiting the payment details visible to our support staff.

Access request

If you want a copy, correction or deletion request under this Privacy Policy, state the action clearly in your support message. We may verify account ownership through the phone path before changing records or disclosing account-linked data.

HANDLING DETAILS

What We Do With Account Data

The practical parts of our Privacy Policy sit around the actions you take: phone verification, login, wallet selection and support contact.

Data collected

We may collect your phone number, account identifiers, login timestamps, device type, browser details and support messages. When you use a local wallet, bank transfer or virtual account, transaction references and status values can be attached to the account record for matching and dispute checks.

Cookie choices

Cookies can keep a necessary login session active and remember basic access choices on your phone or desktop browser. You can clear them through your browser controls, although removing required cookies may sign you out or interrupt the account path back to the lobby.

Account security

Phone verification is used before account access, and device or login signals can help us notice an unusual return. If a sign-in looks different, we may request an account check before showing wallet records, protecting the data attached to your DANA, OVO, GoPay or QRIS activity.

Retention periods

We keep account, support and transaction-reference records only as long as needed for the purpose described in this Privacy Policy, including security checks, disputes and duties that depend on local law. When a record is no longer needed, our handling process moves it toward deletion or restricted storage.

Data sharing

We may share limited data with service partners that help process account access, security checks or payment-status matching. A wallet reference is not the same as a wallet password. We do not invite partners to use your account details for unrelated purposes.

Your changes

You can contact us to request access to eligible data, correction of an inaccurate account detail or deletion where local law permits. Tell us which record concerns you, and we may verify ownership through the phone or account path before making a change.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account and wallet questions we expect before you open access. They cover the data created by phone verification, the device path back to the lobby, payment references and the contact steps for a correction or deletion request. If your situation is not covered, use the support route beside the cashier area and describe the exact account record involved.

It covers account details, phone verification, login records, device signals, cookies, support messages and payment-status references. The policy also explains retention, limited sharing, security checks and your route to request access, correction or deletion where local law permits.

No. We may receive a transaction reference or status result when you use DANA, OVO, GoPay or QRIS, but your wallet password is not needed for that match. Never send a wallet password through support, chat or an account request.

Phone verification links the account to the contact detail you supplied and helps us protect account access. It can also support an ownership check when you ask about login history, wallet references or a Privacy Policy request involving your account.

We may record device type, browser details, login time and related security signals when you access the account on mobile or desktop. These details help identify unusual access and keep a necessary session working; they are handled for account and security purposes.

Yes. Send a support request that names the account record and asks for access or correction. We may verify ownership through your phone or account path before responding. Requests are assessed under the Privacy Policy and rules that depend on local law.

We retain selected account, support and transaction-reference records for the period needed for security, dispute handling or legal duties. The exact period can differ by record type and jurisdiction. When retention is no longer needed, data is deleted or placed in restricted storage.

Use the support link beside the cashier path and include your account identifier, the subject of the request and any relevant transaction reference. We may ask for a phone-based ownership check, but you should not send a wallet password or complete payment credential.

Related Pages

marjan989 Indonesia Account information Live Sic Bo Elite Live Roulette Salon Basketball Live Bet