Reference

Privacy Policy for Your cumi46 Account

cumi46 Privacy Policy shows what data we collect when you open an account, sign in from a phone, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsDevice choicesAccess requests
cumi46 Privacy Policy for Your cumi46 Account
PRIVACY HELP ROUTES

Get Clear Answers About Your Data

A direct support path helps when a privacy question sits beside an account or wallet issue. Tell us which account step you reached, the device you used, and whether the matter concerns DANA, OVO, GoPay, QRIS or another payment record. We use those details to locate the relevant data without asking you to send a wallet password or full payment credentials. If you are in Bandung, the same account contact route applies.

Team online

Account data request

Ask us which personal data is linked to your cumi46 account, including registration details, phone verification status and sign-in records. We may ask you to confirm account ownership before sharing or changing anything, so your request does not expose private data to another person.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt does not match your account history, send the transaction reference and approximate time through our support route. We use the reference to check status records and avoid requesting your wallet password, PIN or complete card details.

Access correction path

For a wrong name, phone detail or other account field, contact us from the email or phone route connected with your account. We confirm the request, apply eligible corrections, and tell you if a record must remain for security, dispute handling or legal reasons.

DATA CONTROL DETAILS

What We Keep Safe Behind Your Login

Privacy is handled through practical account controls rather than broad promises. We limit access to staff and service partners who need data for a stated operational task, and we separate wallet references…

Account security

Your phone verification step helps connect account access to the contact detail you supplied. We also use sign-in time, browser and device signals to spot unusual activity. If a session looks different, we may ask for an extra ownership check before changing account data.

Cookie choices

A necessary session cookie can keep you signed in while moving between the lobby and account pages. We describe its role as part of this Privacy Policy. Clearing cookies may sign you out or remove saved page preferences, but it does not erase account records by itself.

Payment references

For QRIS Quick Deposit or a wallet transaction, we retain operational details such as reference, amount, status and timestamp. We do not request your DANA, OVO or GoPay password. Bank transfer and virtual account records can include the selected BCA, BRI, Mandiri or BNI route.

Device handling

When you open the mobile lobby, we may receive browser, operating system, language and session data needed to display pages correctly and protect access. We do not treat a device signal as your identity on its own; it is combined with account checks where needed.

Retention choices

We keep account, security and payment records for as long as needed to provide access, resolve a payment dispute, prevent misuse or meet a legal duty. When a record is no longer needed for those purposes, our handling process removes or anonymises it where permitted.

Your request

You can ask what data we hold, request a correction, ask for eligible deletion, or object to a specific use. Send the request through the account contact route with enough detail to locate it. We may verify ownership before responding or changing a record.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the connection between login data, device sessions and Indonesian wallet records without asking you to disclose sensitive credentials. If your situation is different, contact us with the account step, payment reference or device detail involved, where local law permits.

The cumi46 Privacy Policy covers account registration, phone verification, sign-in sessions, device signals, cookies, payment references and support requests. It also explains retention, security access and the ways you can ask for a copy, correction or eligible removal of your data.

No. Our Privacy Policy distinguishes a payment status record from wallet credentials. A DANA, OVO or GoPay transaction may provide a reference, amount, status and time, but you should not send us your wallet password, PIN or one-time security code.

Device and browser signals help us keep your account session working and identify unusual access. The mobile path may include operating system, browser type and session time. These signals are not treated as your identity alone and are handled with account checks when needed.

Use the contact route connected with your account and ask for an account data request. Include your registered phone detail or email and the specific record you want located. We verify ownership first, then explain what can be provided under the Privacy Policy.

Yes, you can ask us to correct an inaccurate account field through support. State the old and requested details, then complete any ownership check. Our Privacy Policy allows corrections where appropriate, although some security or legal records may need to remain unchanged.

QRIS records are kept for the period needed to operate the account, reconcile a receipt, handle a dispute, protect access or meet a legal duty. The record may include reference, amount, status and timestamp. We remove or anonymise it when those needs end where permitted.

Yes, the Privacy Policy applies to your account access from Bandung, Medan and other supported Indonesian locations. Availability and eligibility depends on local law. The same process covers account, device and wallet data whether you sign in from a phone or desktop.