Reference

Privacy Policy For Your sandi55 Account

Our Privacy Policy explains what data we collect when you open a sandi55 account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account data explainedWallet records clarifiedCookie choices availableSecurity steps stated
sandi55 Privacy Policy For Your sandi55 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct account support route helps when you want to ask about a Privacy Policy item, correct an account detail or understand a wallet record.

Account data request Ask us which account details are connected to your sandi55 profile and why they are held. Include the account phone or email used during verification so we can locate the right record without asking you to reveal a password.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the related date and account step through support. We can check the wallet status trail while you keep full wallet numbers, security codes and login credentials private.
Correction request When a profile detail needs changing, tell us what appears incorrect and what the accurate detail should be. We may ask for an account check before changing it, because a verified phone step helps prevent another person from altering your record.
DATA HANDLING

What Your Privacy Choices Cover

Privacy at sandi55 is handled through practical account controls rather than broad promises. We separate sign-in details, verification records, wallet references and browsing signals so a request can be directed to the…

Account records

We may hold the name, phone or email details you provide during account creation, together with verification results and sign-in events. These records help us connect a request to your account and reduce confusion when the same person uses a phone and desktop.

Wallet references

A DANA, OVO, GoPay or QRIS status can be linked to an account transaction record. Bank transfer and virtual account references may also be retained for matching and support checks, without asking you to place a secret wallet code in a message.

Cookie controls

Cookies can keep a signed-in session active, remember a language or page setting, and help us understand which policy page brought you to an account action. Your browser lets you clear or block cookies, although some account steps may then need repeating.

Security checks

Phone verification before account access helps us distinguish your sign-in from an unfamiliar attempt. We may examine device and session signals when access looks unusual, while support messages should contain account context only and never a password or security code.

Retention periods

We keep each data type for the period needed for its stated account, security or payment-record purpose, subject to applicable legal duties. When a retention reason ends, records may be deleted, anonymised or restricted rather than kept without a continuing purpose.

Your requests

You can ask for access, correction or clarification through the account support path. Tell us the request type and the phone or email attached to your profile; we may verify ownership first, then explain what can be changed, removed or retained.

Privacy Policy Answers For sandi55

These Privacy Policy answers address the searches we hear most often before account creation. They explain what happens around phone verification, mobile access, cookies, local wallets and requests to see or change personal data. If your situation is different, use the account support path with the smallest amount of detail needed to identify your record.

The sandi55 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, wallet references, support requests and retention. It also explains how to ask for access or correction, including records connected to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the person who supplied the account detail and helps us identify unusual sign-in attempts. We may use the verification result during a support request, but you should never send a password, one-time code or wallet security detail through a message.

Yes. The Privacy Policy applies when you use a mobile browser or desktop browser to sign in, open the lobby or check an account wallet status. Device and session signals may support security checks, while browser cookie controls can clear saved settings and require a later sign-in step.

We link a wallet reference or status to the relevant account and payment step so support can trace a question without requesting your secret credentials. The same approach applies to bank transfer and virtual account references, with retention based on the purpose and applicable legal duties.

Yes. Use the signed-in account support path and state which detail is wrong, such as a phone or email record. We may confirm account ownership before making a change. That check protects the account and helps ensure a correction is made to the right profile.

Send an access request through account support with the phone or email attached to your profile and describe the data period or category you need. We may ask for an ownership check, then explain the available record set, any limits and the expected handling route.

Yes. Access and eligibility depends on local law and the checks applicable to your location. Our Privacy Policy still explains how data is handled when you reach an account step, but it does not remove local restrictions or replace requirements that apply in Indonesia.