Reference

A clear Privacy Policy for your account

Our sarana356 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, use DANA or QRIS, and contact support about a…

Account data clarityWallet record detailsCookie choicesPolicy contact path
sarana356 A clear Privacy Policy for your account
CONTACT YOUR WAY

Get a direct answer about policy data

Questions about the Privacy Policy should reach the account support path so we can match your request with the correct sarana356 record. Include the phone number linked to your account, the relevant date and the payment reference when a wallet or bank entry is involved. We ask you not to send a password or full payment credentials. Requests from Jakarta or Surabaya follow the same account verification check, and access remains available where local law permits.

Team online

Account support

Use the support contact attached to your account when you need to ask what personal data we hold. We may verify your phone number before discussing records, so a request is connected to the correct account rather than disclosed to another person.

Payment record help

For a DANA, OVO, GoPay or QRIS question, include the payment reference and status shown in your account. We use those details to locate the relevant entry without asking you to share a wallet PIN, password or complete bank credentials.

Correction requests

If your phone, contact detail or account record needs correction, tell us which field is wrong and what should replace it. We check the account first, then explain whether the change can be made while legal, security or transaction records must remain.

DATA HANDLING

What our privacy process covers

The practical part of our Privacy Policy is the account trail: phone verification, sign-in signals, wallet references and the messages you send to support.

Account details

We handle the phone number and verification details needed to create and protect your account. When you sign in, we may compare account data with device or browser signals to identify unusual access and keep the account path connected to you.

Wallet references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, status and amount in our records. These details help us match a receipt to your account, answer a payment question and identify a repeated or conflicting transaction.

Browser cookies

Cookies and similar storage can retain a session choice or help us understand whether a page is operating correctly. Your browser settings can manage or clear them, although removing session storage may require you to sign in again.

Account protection

Phone verification is part of the account access step. We do not ask for your password in a support message, and we use account checks before discussing personal records, changing details or investigating a wallet reference.

Retention choices

We keep information only as long as needed for the purpose described in this policy, account security, transaction reconciliation or a legal requirement. Some payment and verification records may therefore remain after a request to close an account.

Your requests

You can ask what account data we hold, request a correction, ask about eligible deletion or raise a privacy concern through support. Include enough account detail for verification, and we will explain any reason a request cannot be completed.

Privacy Policy answers for sarana356

These Privacy Policy answers focus on the account and device questions you are most likely to have before opening or using sarana356. They cover phone verification, local wallets, cookies, deletion requests and the contact route for a privacy concern. Where access or eligibility is mentioned, it depends on local law.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, account protection and how to request a correction.

We use your phone number to create and identify your account and to complete the phone verification step before account access. It helps us connect a support request or payment reference to the correct account without asking you to send a password.

Yes. Our Privacy Policy explains how we handle the sarana356-side reference, status and amount for a DANA or QRIS transaction. DANA and QRIS operate their own systems and privacy terms, so their handling of data remains subject to those providers.

When you sign in through a mobile browser or another browser, we may record browser type, device signals, session details and access time. These details help protect the account and diagnose a page or login issue; they are handled for the purposes stated in this policy.

You can contact account support to ask which eligible personal data we hold or to request a correction. State the field that needs changing and complete our account check. We may retain transaction, security or verification records when a legal reason applies.

Send a deletion request through the account support path with your verified account details. We assess the request against active account needs, payment reconciliation, security records and legal duties. If some records must remain, we will explain the relevant reason rather than removing them.

Use the support contact linked to your account and label the message as a Privacy Policy concern. Include the account phone number, date and any relevant payment reference, but never include a password or wallet PIN. Account access remains where local law permits.