Reference

Privacy Policy For Your sanca77 Account

Our Privacy Policy explains how sanca77 handles the data connected with your account, wallet activity and device access.

Account dataWallet activityDevice accessYour policy rights
sanca77 Privacy Policy For Your sanca77 Account
HELP WITH DATA

Get Help With Privacy Requests

A clear support path helps when you want to ask about data linked to your account.

Account access If your phone verification or login device creates a privacy question, contact our account support path with your registered phone number and the approximate access time. We use those details to locate the relevant event without asking you to disclose your password.
Wallet records For a DANA, OVO, GoPay or QRIS data question, include the payment rail and transaction reference with your request. If the matter concerns a bank transfer or virtual account, we check the matching account record before explaining what data we retain.
Policy changes To request a correction, deletion assessment or copy of account data, identify the account email or phone number and describe the exact change. We may ask for a verification step so one account holder cannot request another person's records.
DATA HANDLING

What Your Privacy Policy Covers

We keep this Privacy Policy practical by connecting each data use to an account, device or payment task.

Account details

We use your registered phone number and any required account details to complete phone verification, restore access and connect support replies to the correct account. Keeping these details current helps us avoid sending a privacy response to the wrong person.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event to your account. Bank transfer and virtual account references serve the same purpose. We use these records to check status, resolve duplicates and answer payment-related data questions.

Device signals

We may retain limited login, browser or device signals when they help identify an unusual access attempt or explain why your account path changed. These signals support account protection and troubleshooting; they are not a reason to build unrelated profiles about you.

Cookies

Cookies and similar session tools can keep your account path working between login steps and help us understand whether a page request belongs to an active session. You can manage browser cookie settings, although some account functions may then require extra checks.

Retention

We retain account, payment and support records only while they support account administration, reconciliation, security checks, dispute handling or a legal need. Retention can vary by record type and local law. Ask us which category applies to a particular request.

Your requests

You can ask what account data we hold, request a correction, question a use or ask whether deletion is available. Send the request through support with your registered contact detail. We verify the requester first and explain any limit that depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and wallet questions you may have before opening or using sanca77 from Indonesia. We keep the examples specific so you can identify what happens during phone verification, QRIS activity, device access and a request to change or remove account data. Where a right or access condition is controlled by location, it depends on local law.

The sanca77 Privacy Policy covers account details, phone verification, login and device events, cookies, payment references, support records and requests about your data. It explains why we use those records, how retention is assessed and how you can ask about a specific account record.

We use your phone number for the account access step and phone verification before discussing account records. It also helps us connect a support request to the correct account. If your number changes, request a correction through support after completing the required identity check.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use those references to match a status or receipt to your account, not to request your wallet password.

Device and cookie data can keep your login path active, identify an unusual access attempt and help explain a failed account step. Browser settings can limit cookies, but you may then face another verification step. We do not need unrelated device details for these tasks.

You can ask for a copy, correction or explanation of data linked to your account. Include your registered phone or email and describe the record, such as a QRIS receipt or login event. We verify the request first, and the available action depends on local law.

Retention depends on the record and why we still need it. Account, payment and support data may remain while it supports access, reconciliation, security checks, disputes or a legal requirement. Ask us about a named record, and we will explain the applicable retention reason.

Use our account support path for a Privacy Policy question and include the registered contact detail plus the record involved. You can mention phone verification, a wallet reference, a device event or a correction request. We will verify ownership before discussing account-specific data.