Reference

Open sultanlotre Privacy Policy Before Account Access

Our Privacy Policy explains what we collect when you create an account, sign in from a phone, or check DANA and QRIS status in the cashier path.

Clear data purposeWallet contextAccount request pathIndonesia access

Explore Our Lobby Read FAQ

Check DANA And QRIS Data Paths

sultanlotre Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you open, access, or maintain a sultanlotre account through our website. We may receive details you enter, such as your phone number and account credentials, together with device signals used to keep a session secure. Payment records can show a selected

1
rail such as DANA, OVO, GoPay, QRIS, bank transfer, or virtual account, plus a reference and status needed to match your account activity. We do not ask you to send wallet credentials through casual messages. Access to the account and related services depends on local law,
2
and our handling of records follows the purpose described here. If you are in Bandung or elsewhere in Indonesia, the same request path applies: sign in, open account settings, and contact us through the support route when you need a privacy response.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

ASK THROUGH ACCOUNT SUPPORT

Contact Us When Privacy Questions Arise

A direct account route keeps privacy requests separate from ordinary lobby questions. Sign in first when you can, open the account or support area, and describe the record or action you are…

Account request Use the signed-in account path to ask what personal data is linked to your profile, why it is used, or which details you want corrected.

Wallet record For DANA, OVO, GoPay, QRIS, or bank-transfer records, share the transaction reference and date only so we can check status without exposing extra wallet details.

Device access If a phone or browser keeps an old session, tell us the device type and access time. We can help review the session path without requesting your private login secret.

HOW WE HANDLE RECORDS

Explore How Account Data Is Handled

We keep the Privacy Policy practical by connecting each data use to an account action you recognise.

Account details

When you create an account, we use the submitted phone and sign-in details to establish access, identify your profile, and respond to requests about the data attached to it.

Device signals

A phone or desktop browser may provide session, browser, and security signals. These help us recognise unusual access without treating your device data as a reason to collect unrelated content.

Cookies

Cookies can remember session choices and support account navigation. You can review cookie controls in your browser, although restricting them may interrupt sign-in or the account settings path.

Wallet matching

A DANA, OVO, GoPay, or QRIS reference may be linked to your account activity so a payment status can be checked. We do not need your wallet PIN for that match.

Retention

We retain account and payment records for the period needed for the stated service, security, dispute, or legal purpose. When that need ends, records are reviewed for removal or further protection.

Change requests

To request access, correction, or removal of eligible details, contact us from account support with the specific field or record. We may verify account ownership before making a change.

Ask About This Privacy Policy

These answers address the Privacy Policy questions you are most likely to have before opening an account. Each response points back to a practical account, device, or payment-data step so you can decide what to share and how to contact us.

The Privacy Policy covers data connected with account creation, sign-in, device sessions, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account.

We use your phone number to create and verify account access, help identify your profile, and respond to account requests. Please check the number before completing the account step.

Yes. It covers session and security signals from a mobile phone, tablet, or desktop browser. These signals help us review sign-in activity and support a request about an unfamiliar session.

We may retain a payment reference, selected rail, amount status, and time to match activity with your account. We do not ask for your DANA or QRIS PIN through support.

Yes. Sign in, open account support, and identify the data you want to access or correct. We may ask for an account check before sharing or changing records.

Send a removal request through the account support path and name the relevant profile field or record. Some data may remain while a security, dispute, or legal purpose still applies.

Yes. Account access and related services depend on local law. If you have a location or eligibility question, contact support through your account path before sharing additional personal details.

Open sultanlotre Privacy Policy Before Account Access

Contact Us When Privacy Questions Arise

Explore How Account Data Is Handled

Account details

Device signals

Cookies

Wallet matching

Retention

Change requests

Ask About This Privacy Policy

01 What does the sultanlotre Privacy Policy cover?

02 Why does sultanlotre need my phone number?

03 Does the Privacy Policy cover mobile and desktop access?

04 How are DANA and QRIS details treated under this Privacy Policy?

05 Can I request a copy or correction of my account data?

06 How do I ask for eligible data removal?

07 Does access to sultanlotre depend on local law?

Related Pages