Reference

1dolar Privacy Policy For Your Account

The 1dolar Privacy Policy explains how we collect, use, store and protect details connected with your account, mobile browser access and wallet activity.

Account dataWallet referencesMobile accessYour data choices
1dolar 1dolar Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact path helps when you need a copy of your data, an explanation of a wallet reference or a correction to account details.

Account contact form Open the support contact form from your signed-in account and choose the privacy subject. We use the account identifier to locate your request, then may ask for phone verification before discussing personal data or changing account details.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the receipt detail and approximate transaction date through account support. We can check the record without asking you to share a wallet password, card secret or one-time code.
Access problem If privacy support is blocked because you cannot sign in, use the account-help path shown on the login screen. Give only the requested account details; we use verification steps to reduce the risk of exposing your data to another person.
DATA PRACTICE

How We Handle Your Personal Data

Privacy choices should be understandable before you open an account. This part explains the working practices behind our Privacy Policy: which records support account access, why a mobile session may be logged…

Account details

We use details such as your phone number and account identifier to create access, complete phone verification and respond to account requests. If you browse Live Baccarat Table or a sports category, related activity may appear in account records used for service and security checks.

Payment references

A payment record can contain a method label, amount reference, timestamp and status connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use these fields to match your receipt and investigate a status question, not to request your private wallet credentials.

Cookies and sessions

Cookies and similar session signals help keep your signed-in state, remember security preferences and identify unusual browser behaviour. When you move from login to the mobile lobby, these signals can connect the session to your account; you can manage browser cookie controls, though some access steps may then stop working.

Account security

We may record sign-in time, device type, browser signals and verification events to protect your account. Phone verification before access helps us check that a request comes from you. We will not ask for your password or one-time code through an unsolicited support message.

Retention choices

We keep personal data only for as long as it supports the stated account, security, dispute or legal purpose, subject to applicable requirements. When a record is no longer needed, our handling may include deletion, restriction or removal of direct account links where that is available.

Changes and requests

You can ask us to access, correct or clarify personal data through the account contact form. Tell us which field or record concerns you, such as a phone detail or QRIS receipt reference. We may verify account ownership before making a change or sharing a copy.

Privacy Policy Answers For 1dolar

These Privacy Policy answers address the account and payment questions you may have before opening access from Indonesia. They explain what we collect, how to reach us, what happens on a mobile browser and which checks may apply when you ask for a change. If your situation is not covered, send the request through the account support route.

It covers account details, phone verification, browser and device signals, support messages, account activity and payment references. It also explains cookies, security checks, retention and requests to access or correct data connected with your 1dolar account.

Yes. The Privacy Policy covers payment references linked with DANA, OVO, GoPay and QRIS, including method labels, status details and transaction timestamps. We use those records to match receipts and investigate account questions without asking for your private wallet password.

Device type, browser signals, session time and verification events help us maintain account access and identify unusual sign-in behaviour. When you use a mobile browser to move from login to the lobby, these records can connect that session with your account security checks.

Use the account contact form and describe the specific request, such as a copy of account data or a correction to your phone detail. We may ask for account verification before responding, especially when the request concerns payment records or login access.

You can send a removal request through account support. We assess which records can be removed, restricted or de-linked while considering account security, dispute handling and applicable legal duties. Eligibility for a request depends on local law and the record’s purpose.

Cookies and session tools support sign-in continuity, security preferences and browser checks. You can adjust cookie controls in your browser, but disabling required cookies may interrupt phone verification or the path from login to the mobile lobby.

Use the support contact form available through your account or the login help path if access is blocked. Include your account identifier and a short description, but not your password, wallet PIN or one-time verification code. We use ownership checks before discussing personal data.