Reference

poin123 Privacy Policy for Your Account

Our Privacy Policy explains what poin123 collects when you create an account, sign in, use Secure Account Access, or check DANA and QRIS payment records.

Clear collection rulesWallet record contextAccount request pathIndonesia access wording
poin123 poin123 Privacy Policy for Your Account
REQUEST ROUTES

Where To Send Privacy Questions

A clear contact route helps you ask about your personal data without explaining the same issue repeatedly.

Account contact Use the support contact displayed in your poin123 account area for a privacy request. Include your registered phone detail and the subject of the request, but do not send a password or full wallet credentials. We may ask for phone verification before discussing account-linked data.
Payment record help If your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, add the date and visible reference from your receipt. We can use that detail to identify the relevant status without asking you to disclose an entire payment instrument.
Access assistance When privacy settings or account access stalls on a mobile browser, tell us the device path and the page where it stopped. We can separate a sign-in issue from a data request, then direct your question to the correct account support route.
DATA PRACTICES

What We Do With Account Data

We handle privacy as an account process rather than a general statement. The records connected to Secure Account Access, wallet status, support contact, and device sessions help us answer requests accurately and…

Account details

We may hold details needed to create and maintain your account, such as contact information, phone verification status, sign-in history, and selected account settings. These records help us connect a privacy request to the right account and prevent disclosure to another person.

Payment references

A DANA, OVO, GoPay, or QRIS activity may leave a reference, amount status, timestamp, and account link in our records. Bank transfer and virtual account entries can serve the same matching purpose. We use these details for status checks and account questions.

Cookies and sessions

Cookies and similar session signals can keep your sign-in path working, remember necessary choices, and help us detect unusual access. A mobile browser and desktop browser may produce different session details. You can manage browser cookie controls, although some account functions may then require another sign-in.

Account security

We use sign-in records, phone verification, device signals, and account activity checks to reduce the chance of an unauthorised change. If Secure Account Access flags a mismatch, we may pause a request until you confirm account ownership through the contact route shown in your account area.

Retention period

We retain account, payment, and support records only for as long as needed for the stated account purpose, security checks, dispute handling, or a legal requirement. When a record is no longer needed, our handling follows the deletion or anonymisation process available under applicable local requirements.

Changes and requests

You can ask us to access, correct, clarify, or remove personal data through the account contact route. Tell us which record is involved, such as a QRIS receipt or phone detail. We may verify ownership first, and the result depends on local law and retention duties.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, wallet, device, and contact questions we expect you to ask before opening or using poin123 in Indonesia. Each answer stays focused on personal data handling rather than general account features. If your situation involves a specific receipt, sign-in attempt, or correction request, use the account contact route and include only the details needed to identify the issue.

The poin123 Privacy Policy covers account and contact details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention, and privacy requests. It applies when you access the site from a mobile browser or desktop, including activity linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account status.

We may record a payment reference, timestamp, account link, and status so we can match a DANA or QRIS event to the correct account question. The same approach can apply to OVO, GoPay, bank transfer, and virtual account records. These details support status checks and privacy enquiries.

Send an access request through the support contact shown in your account area. State the registered phone detail and the data category you want to access, such as sign-in history or a QRIS receipt. We may ask for phone verification before releasing account-linked details, and the outcome depends on local law.

Yes. The Privacy Policy covers necessary cookies, session signals, device details, and sign-in activity created when you use a mobile browser. Those records can differ from a desktop session and may help us protect Secure Account Access. Browser cookie controls may affect how often you need to sign in.

You can request a correction through the account contact route and identify the field that appears wrong, such as a phone detail or payment reference. We may verify ownership before changing it. If a record must be retained for security or legal reasons, the available correction path depends on local law.

We keep records for the period needed for account operation, security checks, payment status questions, dispute handling, or a legal requirement. Retention can differ by record type, including support messages and bank transfer references. When the purpose ends, we follow the deletion or anonymisation process available under local requirements.

The policy is provided for your account and data questions, while account access and eligibility depend on local law. If you need a privacy decision, contact us through the route shown in your account area. We will assess the request using the applicable requirements and the records connected to your account.