Reference

in1234 Privacy Policy, Clearly Explained

Our Privacy Policy shows how we handle the account details, wallet records and device signals connected with your in1234 access.

Account detailsWallet recordsCookie choicesAccess requests
in1234 in1234 Privacy Policy, Clearly Explained
REQUEST HELP DIRECTLY

Wallet Receipt Help for Privacy Requests

A clear support path matters when a privacy question is tied to a wallet receipt or account sign-in. Start from your signed-in account and include the phone number attached to your profile, the relevant request and any DANA or QRIS reference. We use those details to locate the right record without asking you to resend unrelated account data.

Team online

Account access

If you cannot reach the privacy request path, tell us which sign-in step stopped and the device you used. We can direct the request without asking for your password.

Payment record

For a DANA, OVO, GoPay or QRIS question, share the transaction reference and date shown in your receipt. We use that pair to check the related wallet record.

Request status

After you submit a data question, keep the account contact available for clarification. We may ask for a phone verification step before discussing personal account details.

SIX DATA PRACTICES

Six Ways We Handle Account Data

Privacy work is part of the account flow, not a separate promise. We limit requests to the details needed for a clear decision, protect account access with phone verification and review device…

Purpose first

We use account and wallet details to provide access, match payment status and respond to your request. We do not ask for unrelated personal details to answer a Privacy Policy question.

Cookie controls

Cookies and similar device storage can keep a session active or remember basic preferences. Your browser settings can remove them, although some account steps may then need to be repeated.

Account security

Phone verification helps confirm that an account request comes from you. Never send us your password, wallet PIN or one-time code when asking about personal data.

Retention checks

We retain records only as long as needed for account operation, security checks or a legal request. Retention can vary by the type of record and local law.

Correction route

If your phone number or account detail is wrong, use the signed-in support path and identify the field to change. We may verify your account before applying a correction.

Data contact

Privacy questions can be raised through account support with the subject, account phone number and requested action. We use that route to keep your request connected to the right record.

Privacy Policy Questions for Your Account

These answers cover the searches we hear most often about the in1234 Privacy Policy. If your situation involves a wallet receipt, a device change or a correction request, use the signed-in support path and describe the specific record involved.

It covers account details, phone verification, wallet references, device signals, cookies, support requests and retention. It also explains how you can ask for access, correction or removal where local law permits.

When you use DANA or QRIS, a payment reference can connect a wallet status with your account request. We use that reference to check the relevant record, not to collect unrelated wallet data.

Yes. Submit an access request through the signed-in account support path, include the phone number linked to your account and describe the records you want. We may verify your identity first.

Send a correction request through account support and name the inaccurate field, such as a phone number. We may ask for phone verification before changing or confirming personal account details.

Retention depends on the record, its security purpose and any legal requirement. We keep account, payment-reference and support records only for the period needed under applicable rules.

Cookies or similar storage may support sign-in sessions and basic preferences on your mobile browser. You can adjust browser settings, but removing storage may require another account verification step.

Sign in, open the account support path and select a privacy request. Include your request type and account phone number; for wallet matters, add the DANA, OVO, GoPay or QRIS reference.