Reference

situs66 Privacy Policy For Your Account

Our Privacy Policy explains how situs66 handles the details you provide when you open an account, confirm your phone, access the lobby, or use DANA and QRIS.

Account detailsCookie choicesPhone verificationDANA and QRIS records
situs66 situs66 Privacy Policy For Your Account
PRIVACY HELP PATH

Get Privacy Policy Help Before Access

A clear contact path matters when your account details, cookie choice, or payment reference needs attention.

Account data request Ask us to identify the personal details connected with your situs66 account.
Cookie setting question Tell us if a cookie choice behaves differently on your phone or browser.
Payment reference check For DANA, QRIS, OVO, GoPay, virtual account, or bank transfer records, include the payment…
DATA HANDLING DETAILS

What Your Privacy Policy Covers

We handle privacy as part of the account path rather than as a separate promise. Registration information supports account access, device signals help us understand browser and phone sessions, and cookies remember…

Data we receive

We may receive your registration details, phone verification result, device and browser signals, cookie preferences, support messages, and payment references. For a QRIS or DANA status question, the reference helps us locate the relevant account event rather than asking for unrelated details.

Cookies on your device

Cookies can support login continuity, preference storage, and basic site operation. If you switch from a phone browser to another device, some choices may not follow automatically. Your browser controls can remove cookies, although certain account steps may then need to be repeated.

Account protection

Phone verification helps connect account access with the correct person. Keep your password and verification codes private, and contact support if a session or account detail looks unfamiliar. We will not ask you to place a password inside a payment receipt or support message.

Retention approach

We retain records for as long as needed for account service, payment matching, security checks, dispute handling, and applicable legal duties. A request to remove data may not erase every record immediately when a transaction or access obligation requires continued retention.

Requesting a correction

If your name, phone detail, or another account field is inaccurate, contact us with the change you want and enough detail to locate the account. We may verify ownership first, then update the relevant record when the request is supported and permitted.

How we respond

We assess privacy requests against the account record, device context, and local requirements. Explain whether you want access, correction, deletion, or a cookie answer. We will tell you if we need clarification or cannot complete a request because local law requires the record to remain.

Privacy Policy Answers For situs66

These Privacy Policy answers address the account questions you may have before opening access or returning to the lobby. We explain the practical connection between registration, phone verification, cookies, device use, and local payment references. If your situation is different, contact us with the smallest useful set of details and do not include your password or verification code. Requests are handled according to the account record and where local law permits.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references. We explain how these details support access, account protection, payment-status matching, and requests for access or correction. Eligibility and handling requirements remain subject to local law.

Phone verification helps us connect an account request with the correct person before account access. It can also help when you ask about a DANA, QRIS, or bank-transfer reference. Keep the code private; support should never need your password or verification code in a message.

Yes. DANA and QRIS transactions can create references, amounts, and status details needed to match a payment event with your account. We use those references for account service and status checks. Send only the relevant reference when asking for help, not your full sign-in details.

Cookies may remember selected preferences and support basic login or page functions on your browser. Removing them can require you to repeat an account step or reset a preference. Your browser provides cookie controls, and support can explain a function without requesting your password.

You can contact us to ask what personal details are connected with your account. Include the account step involved and enough information for ownership checks. We may withhold or limit a response where disclosure would expose another person or where local law requires a different process.

Contact support and state which account field is wrong, such as a phone detail or registration entry. We may verify that you control the account before making a change. If a record is tied to a payment or legal duty, we will explain any limit on editing it.

We keep records for the period needed for account access, payment matching, protection checks, dispute handling, and applicable legal duties. Retention can differ by record type. You may ask us about a specific record, although deletion may be restricted when continued storage is required.