Reference

poster303 Privacy Policy for Your Account

poster303 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesAccess requests
poster303 poster303 Privacy Policy for Your Account
PRIVACY SUPPORT ROUTES

Get Privacy Help Before Account Access

A clear contact path matters when your account details or wallet record needs attention.

Account data request Ask us to confirm the account details connected with your registered phone number.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears unclear, send the payment time…
Access concern Tell us when a sign-in alert, browser change or phone verification issue relates to…
DATA HANDLING PRACTICE

How We Handle Your Account Data

We keep the Privacy Policy practical: each data type has a service reason, an access path and a contact option.

Account creation

We collect the details needed to open and maintain your account, including your phone number and verification result. A clear account step helps us distinguish your request from an unauthorised attempt to change personal data.

Cookie settings

Cookies and similar browser storage can remember a sign-in state, language preference or security signal. You can manage browser permissions, although turning some storage off may require another phone verification step.

Device signals

We may record device type, browser version and connection indicators when you sign in. These signals help us spot an unexpected switch from your usual phone and investigate access concerns.

Payment matching

For QRIS, DANA, OVO, GoPay and bank transfer activity, we retain references that help match a payment to your account. We do not need your wallet password to check a receipt or status.

Retention decisions

We keep personal data only while there is a service, security or record-keeping reason to do so. When that reason ends, we assess deletion, aggregation or anonymisation under our internal handling process.

Change requests

You can ask about access, correction or deletion through our support route. We first confirm your account connection, then explain which information can change and which records must remain for a valid operational reason.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the questions we most often receive before account access. They cover the data connected with sign-in, local wallet activity, cookies, device changes and requests sent to our support route. If your situation is not listed, contact us with the smallest amount of personal detail needed to identify your account.

The poster303 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains your options to ask about access, correction, deletion or retention.

We collect the account details you submit, such as your name and phone number, together with the result of required verification. We can also record sign-in time, device type and browser signals so we can protect account access and investigate an unusual request.

Yes. The Privacy Policy covers payment references, timestamps, amounts and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these records to match a payment without asking for your wallet password.

Cookies or browser storage can remember a sign-in state, language preference and security signal. You can change cookie permissions in your browser. If a required security cookie is removed, we may ask you to complete phone verification again before account access.

Yes. Send an access or correction request through our account-support route, using the registered phone number only through that secure channel. We confirm your connection to the account before sharing details or changing a record, which helps prevent an unauthorised request.

Retention depends on the reason for holding each record, including account security, payment matching and applicable legal duties. When a record no longer has a valid need, we assess deletion or anonymisation. You can ask support which category applies to your request.

You may ask us to delete personal data through the support route. We review the request against account-security, payment-record and legal needs, then explain the result. Access to the service depends on local law, and some records may need to remain for a valid reason.