Reference

siap55 slot Privacy Policy For Your Account

siap55 slot Privacy Policy explains what we collect when you create an account, sign in from mobile, or use DANA and QRIS for an account transaction.

Clear data purposesWallet record contextAccount access controlsCookie choices
siap55 slot siap55 slot Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy Beside Your Account

A clear support route helps you resolve a data question without repeating your account history.

Account help Use the signed-in account path for a Privacy Policy question whenever you can.
Wallet record check If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference appears incorrect…
Data change request For a correction, access request, or question about deletion, tell us the account step…
HANDLING DETAILS

Privacy Controls From Login To Device

We keep this Privacy Policy practical by linking each handling step to an action you recognise: phone verification before account access, a device sign-in record, a wallet reference at the cashier, or…

Account data

We collect details such as your phone number, account identifiers, sign-in events, and verification status so we can provide account access and respond to account-specific requests. We do not need your DANA, OVO, or GoPay wallet password to match a transaction.

Cookies and browser use

Cookies and similar browser signals can keep your session connected, remember selected settings, and help us identify unusual sign-in behaviour. Your browser controls can clear or restrict cookies, although some account functions may then require another sign-in.

Device security

When you move from a phone login to the lobby, we may record device type, browser details, approximate network data, and time of access. These signals help us compare a new session with your account and prompt a verification step when needed.

Wallet references

For QRIS, DANA, OVO, GoPay, bank transfer, or virtual account activity, we retain the reference needed to reconcile the account transaction. The reference can show the rail and status, while private wallet credentials remain outside our records.

Retention approach

We retain personal data while it supports account administration, transaction reconciliation, security checks, support handling, or a legal duty. When a record is no longer needed for those purposes, we remove it or separate it from direct account identification where practicable.

Your request path

You may ask us to access, correct, or clarify personal data through support. Include the account phone number and the specific record, such as a device sign-in or QRIS reference, so we can verify the request and return a focused response.

Privacy Policy Answers For Indonesia

These Privacy Policy questions cover the account actions you are most likely to check before opening or using an account. We answer them in the same practical terms used by our support route: what is recorded, why a verification step appears, how wallet references are handled, and where to ask for a change. Access or eligibility depends on local law, so a local rule can affect how we respond to a request.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and transaction references. It explains how we use those records for account access, security, reconciliation, support, and legal duties where local law permits.

We may collect your phone number, account identifiers, verification status, device and browser details, sign-in times, support messages, and transaction references. We collect each category for a stated account, security, support, reconciliation, or legal purpose.

No wallet password is needed for our transaction matching. We may retain a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference and its status, allowing us to connect the record to your account without storing private wallet credentials.

Phone verification links account access to the number you provided and helps us identify an unusual sign-in. It also gives support a safer way to confirm an access or data request before discussing account-linked records.

Contact support through the signed-in account path and name the record you want to see or correct. Include your account phone number and a clear detail, such as a device event or QRIS reference, so we can verify and handle the request.

We keep records while they are needed for account administration, transaction reconciliation, security checks, support handling, or a legal duty. After that period, we remove them or separate them from direct identification where practicable.

Yes. Your mobile browser settings can clear or restrict cookies, and you can repeat that step when needed. Some sessions may then require another login because the browser no longer retains the setting or session signal.