Reference

Privacy Policy for your sage77 account

Your sage77 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move between mobile and desktop access.

Clear data purposesPayment record contextPhone verification detailsCookie choices

Explore Our Lobby Read FAQ

How we use account data

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

Our Privacy Policy connects each data use to a clear account need. We collect contact details and phone verification results when you create or recover access, then use them to protect the account from unauthorised entry. When you select DANA, OVO, GoPay, QRIS, bank transfer, or

1
a virtual account, we keep payment references and status details needed to match your request and resolve a receipt question. Device type, browser signals, and cookie events help us remember security choices and identify unusual sign-in behaviour. We do not describe access as universal: eligibility depends
2
on local law, and our policy applies where local law permits. You can ask what data we hold, why it is used, how long it remains, or which correction path applies. Payment chips: DANA, OVO, GoPay, QRIS.

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

PRIVACY SUPPORT

Contact routes for privacy questions

A direct privacy request helps us locate the right account record without exposing details to the wrong person.

Account access path Use the account support route when you need a copy of your personal data, an explanation of its use, or help confirming which phone number is linked to your sage77 account.

Payment record path For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the transaction reference and date so we can separate your request from another account.

Correction request path Tell us which account detail needs changing and why. We check the request against your verified account before updating contact data, correcting a record, or explaining why a record must remain unchanged.

SECURITY CONTROLS

Data controls behind sage77 access

We handle Privacy Policy requests as account matters, not as general lobby questions. Our process separates identity checks, payment references, device signals, and support messages so each detail has a defined purpose.

Account details

We use the contact details you provide to create, restore, and protect account access. Phone verification confirms that a recovery or privacy request is connected to the person controlling the registered number.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records may show a reference, amount status, and timing. We use those fields to match a payment question without asking for your wallet password.

Device signals

Your browser, operating system, and sign-in events can help us spot an unusual access attempt. These signals support account protection and are not treated as a replacement for your phone verification step.

Cookies

Cookies can remember sign-in preferences, security choices, and page settings on your device. You can manage them through your browser controls, although changing them may require another account check.

Retention periods

We keep records only for the operational, security, dispute, or legal reason described by the applicable process. Ask support which category covers a record and whether removal or restricted use is available.

Request verification

Before sending account data or changing a personal detail, we compare your request with the registered account step. Never send a password, full card detail, or wallet PIN in a privacy message.

Privacy Policy questions for Indonesia

These Privacy Policy answers cover the searches we hear most often from people considering a sage77 account. They explain the practical path for account data, payment references, cookies, device access, corrections, and deletion requests. If your situation is different, contact support through the account route and describe the record you want us to check. Access remains subject to local law.

It covers data connected with your account, phone verification, device access, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains purposes, retention, security checks, correction requests, and contact routes.

We use your phone number to create and protect account access, complete the verification step, and help confirm a privacy request. If you ask us to change or disclose account data, the registered number helps us avoid sending details to the wrong person.

Yes. The Privacy Policy covers the payment references and status details needed to match a QRIS, DANA, OVO, or GoPay request. We may also retain bank transfer or virtual account references for reconciliation, support checks, disputes, or another stated legal need.

Contact support through the account access route and ask for a personal data copy. Include the verified phone number, the account detail you want checked, and the relevant date. We may confirm ownership first, then explain what can be provided and in what format.

Yes. Send a correction request through support and identify the exact field, such as a phone number or contact detail, that needs attention. We verify the request before making a change, and we explain if a payment or security record must remain unchanged.

Cookies may retain security preferences, sign-in settings, or device choices so your next account visit follows the same path. You can adjust them in your browser. If cookies are removed, we may ask for phone verification again before allowing account access.

You can ask support whether deletion, restriction, or another privacy action applies to a specific record. We first verify the account request and then check operational, security, payment, dispute, and legal retention needs before confirming what can be removed.

Privacy Policy for your sage77 account

Contact routes for privacy questions

Data controls behind sage77 access

Account details

Payment references

Device signals

Cookies

Retention periods

Request verification

Privacy Policy questions for Indonesia

01 What does the sage77 Privacy Policy cover?

02 Why does sage77 need my phone number?

03 Does the Privacy Policy cover QRIS and wallet records?

04 How can I request a copy of my sage77 data?

05 Can I ask sage77 to correct my account details?

06 How do cookies affect Privacy Policy choices?

07 Can I request deletion of my sage77 data?

Related Pages