Reference

Privacy Policy for satu lotre Accounts

satu lotre Privacy Policy explains what we collect when you open an account, sign in on mobile, browse rajabaccarat or use DANA and QRIS, and how we use…

Clear data purposesWallet reference detailsMobile access controls
satu lotre Privacy Policy for satu lotre Accounts
DATA HELP CHANNELS

Contact satu lotre About Your Data

A clear contact path helps when a Privacy Policy question involves your account or wallet record.

Live chat Use live chat from the account support area between 09:00 and 23:00 WIB for Privacy Policy questions, access corrections, or a request to identify the data connected with your satu lotre account.
Account path Start with your verified phone number and account reference when asking about a DANA, OVO, GoPay, or QRIS record. This lets us check the correct account without asking you to reveal a password.
Receipt check For a payment-data query, attach the date, rail name, and reference shown on your receipt. Remove card-like credentials or one-time codes first, then ask us to check the stored status.
HANDLING YOUR RECORDS

Account Records Behind Wallet Access

Privacy Policy choices are easier to use when each data practice has a clear reason. We separate account identity, device signals, cookie preferences, and payment references so a request can address the…

Data purposes

We use your phone number and account details to create access, deliver account messages, and connect support replies to you. Payment references help us match DANA, QRIS, or bank transfer status without requesting unrelated wallet content.

Cookies

Cookies and similar storage can keep a session active, remember language or page choices, and show whether a device has passed a sign-in check. You can ask support which cookie category relates to your request.

Device security

When you sign in from a phone or desktop, we may record device type, browser details, session time, and unusual access signals. These records help us investigate account access without storing your device password.

Wallet references

A DANA, OVO, GoPay, QRIS, virtual account, or bank transfer entry can include a reference code, amount, timestamp, and status. We use those fields to trace a cashier event and resolve a receipt question.

Retention requests

We retain records only for the operational, security, dispute, or legal purpose connected with them. Ask live chat to explain a retention period or whether a particular account record can be removed.

Change requests

To request access, correction, deletion, or a copy of your data, contact us from the verified account route. Include the requested action and phone number; we may ask for an account step to confirm identity.

Privacy Policy Questions for Your Account

These Privacy Policy answers cover the account actions we hear about most often, from phone verification to wallet references and device records. If your situation is different, use live chat from 09:00 to 23:00 WIB and describe the exact record or request. We will use the account path available to you and apply local-law conditions where relevant.

The satu lotre Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, and payment references. It explains why we use each category, how retention works, and how you can ask for access, correction, deletion, or clarification.

Phone verification connects an account request to the person controlling that number and helps us protect sign-in access. We use the verified route when handling a Privacy Policy request, changing account details, or checking a disputed wallet reference.

Yes. The Privacy Policy includes transaction references connected with DANA and QRIS, such as status, amount, time, and reference code. We use these details to match a payment event with your account and investigate a receipt question.

You can ask for a description or copy of data linked to your account through live chat. Send your verified phone number and request scope. We may confirm identity before responding, and access depends on local law.

Contact support with the incorrect field, the account phone number, and a matching reference if the issue concerns OVO, GoPay, bank transfer, or a virtual account. We check the source record before confirming whether a correction is possible.

You may ask about deletion through the verified account path. We assess the request against active account needs, security checks, disputes, and legal retention duties. Where local law permits, we remove eligible records or explain why a period still applies.

Cookies can maintain a session and remember selected settings, while device data can help identify unusual sign-in activity. The Privacy Policy explains these purposes. Ask live chat for a cookie or device-data query without sending your password or one-time code.