Reference

sakti77 Privacy Policy: Clear Data Choices

Clear data choices come first: our Privacy Policy explains what sakti77 collects when you open an account, use the mobile browser, or select DANA and QRIS.

Account data explainedCookie choicesRequest changes
sakti77 sakti77 Privacy Policy: Clear Data Choices
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact route helps when a privacy request and a wallet record meet. We ask you to contact support from the account-linked channel where possible, so we can match your request without exposing details to the wrong person. Include the relevant account step, such as phone verification or a QRIS receipt, and we will explain the next check. The same route can clarify whether access depends on local law.

Team online

Account-linked support

Use the support channel displayed after login and include your registered phone number. We use that account step to confirm identity before discussing stored details or changing a profile record.

Wallet record help

For DANA, OVO, GoPay, or QRIS questions, share the payment reference and date rather than sending a wallet password. We can trace the record and explain what data the request concerns.

Cashier-path requests

When a privacy question starts beside the cashier path, mention whether it concerns a bank transfer or virtual account. This helps us route the request to the correct account record.

SECURITY PRACTICE

Keep Account Data Under Your Control

We handle privacy through practical account steps rather than vague promises. Your registered phone, device session, wallet reference, and support request each serve a different purpose, and our Privacy Policy explains those…

Data handling

We use account details to create access, complete phone verification, answer support requests, and connect payment references to the correct record. We avoid asking you to send unrelated personal details through chat.

Cookie controls

Cookies and similar browser signals can remember a session or help us understand page use. Our Privacy Policy explains their purpose, and you can manage browser permissions through your mobile or desktop settings.

Account protection

Keep your login details private and sign out on shared devices. If a mobile session looks unfamiliar, contact us through the account-linked support route before requesting profile or wallet changes.

Retention periods

We retain categories for different periods based on account operation, payment reconciliation, support history, or legal needs. The applicable purpose matters, so a QRIS receipt may follow a different schedule from a cookie.

Who can contact us

You can ask about stored data, processing purposes, corrections, deletion, or a copy through our displayed support channel. We may verify the registered phone before releasing account-specific details.

Requesting changes

State the change clearly, such as correcting a phone number or asking about a DANA receipt. Include the account step involved, and we will explain any verification or legal reason affecting the request.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or asking about a stored record. We keep the route practical: identify the account step, name the payment reference when relevant, and contact us through the displayed support channel. Account availability depends on local law.

It covers account details, phone verification, device sessions, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone number for account creation, login checks, and identity confirmation before discussing private records. It also helps us connect a support request to the correct account.

Yes. It explains that a QRIS or wallet record may include a reference, amount, status, receipt, and time stamp so we can match payment questions without requesting your wallet password.

Contact us through the support channel shown after login, identify your registered phone, and ask for a data copy. We may complete an account check before releasing account-specific details.

Yes. Tell us which field is wrong, such as a phone number, and name the account step involved. We will verify the request and explain any reason a change cannot be applied.

Retention depends on the data category and purpose. Account, support, payment, and cookie records may follow different periods, which our Privacy Policy describes alongside operational or legal reasons.

Access depends on local law. Before opening an account or sending a request, confirm that use is permitted where you are. Our support route can clarify policy wording, but cannot replace local requirements.