Reference

Open idr508 Privacy Policy Before Account Access

idr508 Privacy Policy gives you a clear view of how we collect, use and protect details connected with your account, including phone verification and wallet status.

Clear data purposesWallet record clarityPhone verification detailsRequest paths
idr508 Open idr508 Privacy Policy Before Account Access
REQUEST HELP DIRECTLY

Check Privacy Policy Help In Support Chat

A privacy question should not leave you guessing about the next step.

Account data chat Use our support chat to ask which account details connect to your phone verification…
Wallet record request If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date and…
Policy contact path For correction, deletion or access questions, ask support to route your message as a…
DATA HANDLING DETAILS

Switch Through idr508 Data Controls

Privacy controls work best when each data purpose is easy to identify. We separate account security records, payment references, support messages and cookie signals so a request can be assessed against the…

Account security

Phone verification is used to connect you with the account you are asking about. Login time, browser and device signals can help us investigate an unusual session, but support will still ask for an account check before discussing private details.

Cookies and sessions

Cookies can keep your mobile login, page preferences and security session working between visits. You can manage browser cookie settings, although blocking required cookies may interrupt account access or require another phone verification step.

Payment references

A DANA, OVO, GoPay or QRIS reference is handled as a transaction-related record. Bank transfer and virtual account references may be matched with the requested account event so status questions can be answered accurately.

Retention checks

We keep personal details only for the period needed for account operation, security review, support handling and applicable legal duties. When a retention reason ends, the record may be removed, anonymised or restricted from routine use.

Correction requests

If your phone number or another account detail is wrong, contact support and state what should change. We verify ownership first, record the request, and explain if a security or transaction record must remain unchanged.

Who to contact

Start with the support route shown beside your account or cashier path and ask for a Privacy Policy request. Include the account identifier and request type, but never send a password, wallet PIN or full payment credential.

Ask About Privacy Policy And Your Account

These Privacy Policy answers cover the account steps you are most likely to check before opening access. We explain what happens with phone verification, device signals, cookies, DANA and QRIS references, and requests to view or change your details. If your situation is outside these answers, contact support through the account route and mention the exact record or event you want us to check.

The idr508 Privacy Policy covers details used for account creation, phone verification, login security, wallet references, cookies and support requests. It also explains retention, correction and contact routes. Access and eligibility depends on local law, so check the current page before opening an account.

We use phone verification to help confirm that the person requesting account access or a data change controls the account contact. It can also support security checks after an unusual mobile login. We do not ask you to share a verification code in support chat.

We use payment references to connect a wallet or QRIS event with the account request and answer status questions. The reference is not a substitute for your wallet credential. Do not send a PIN, password or full payment secret when asking about a transaction record.

Yes. The Privacy Policy covers device, browser, IP and cookie signals used for session continuity and account security. A mobile browser may require another verification step after cookie removal or a device change. These signals help us assess access and are not used as a payment credential.

Contact support through the account path and state that you want a Privacy Policy data access request. Include the account identifier and a reachable contact detail. We may verify ownership before responding, and we will explain any record that cannot be supplied under applicable local law.

Yes. Send a correction request through support with the account detail that is wrong and the replacement detail. We first confirm account ownership, then check whether the change affects phone verification or a transaction record. Some security and payment records may need to remain unchanged.

Use the support route and request deletion under the Privacy Policy. We will confirm which account you mean and explain what can be removed, restricted or retained for security, transaction handling or legal duties. Where local law permits, we process the eligible part after verification.