Reference

savaya55 Privacy Policy For Your Account

savaya55 Privacy Policy sets out what we collect when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet referencesDevice controlsYour requests
savaya55 savaya55 Privacy Policy For Your Account
REQUEST A HAND

Ask About Privacy From Support

A direct support request helps when you want to understand a data field, correct an account detail, or ask why a wallet reference appears in your history. Tell us the account phone number and the issue category, but do not send a password, one-time code, or full wallet credentials. We use the account step to locate the right record without asking you to disclose unnecessary payment secrets.

Team online

Account questions

Use our account support route when you need to ask what profile data we hold or why phone verification is connected with your account access.

Wallet records

For DANA, OVO, GoPay or QRIS references, share the visible transaction reference and date only; we can check the status without requesting your wallet password.

Correction requests

Ask support to correct an inaccurate phone number or profile field. We may request an account check before changing details linked to your sign-in.

DATA HANDLING

Browse How We Handle Your Data

Privacy depends on practical controls, not vague promises. We separate account credentials from wallet references, use device and sign-in signals to protect access, and keep records only for the operational or legal…

Account records

When you open an account, we use your submitted profile and phone verification details to create access and connect activity with the correct account record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match status or reconciliation details, not to collect your private wallet password.

Cookies and storage

Cookies or similar browser storage can remember sign-in state, language choices and security signals. You can manage browser permissions, though some account steps may stop working.

Device security

We may assess device, browser and sign-in signals when access looks unusual. If a check appears, complete the account step through the same phone path rather than sharing codes.

Retention periods

We retain records for account operation, dispute handling, security checks or legal duties, then remove or de-identify them when the applicable retention need ends.

Your requests

You can contact us to ask about access, correction, deletion or processing concerns. We may verify ownership before acting, and the result depends on local law.

Check Privacy Policy Answers

These Privacy Policy answers cover the account and payment questions you may have before opening access. If your situation is not listed, contact support with a short description and the relevant account reference, without sending secret credentials.

It covers data created through account opening, phone verification, sign-in, mobile browsing, wallet status checks and support requests. It also explains cookies, retention, security signals and ways to ask about your records.

The policy describes profile details, phone verification data, sign-in records, device signals and support correspondence. We use these details to provide access, protect the account and respond to your requests.

Yes. It explains how we handle DANA, OVO, GoPay and QRIS references used for status matching. The payment service may apply separate terms, and we do not ask for your wallet password.

Contact support with your account phone number, the field you believe is wrong and a safe description of the issue. We may verify ownership before changing data linked to your account.

You can submit a deletion request through support. We assess account, dispute, security and legal needs before acting, so deletion or restriction depends on local law and applicable retention duties.

Cookies and browser storage may retain sign-in state, language choices and security signals on your phone. Browser controls can remove them, but account access or verification steps may then require repetition.

Use our support route and state whether your request concerns access, correction, deletion, cookies or a wallet reference. Include only the account details needed to locate the record, never passwords or codes.