Reference

Open rokok11 Privacy Policy Clearly

Our Privacy Policy explains how rokok11 handles the details you provide when opening an account, checking DANA or QRIS status, and moving through the lobby on mobile or…

Account clarityWallet contextDevice choicesSupport route
rokok11 Open rokok11 Privacy Policy Clearly
ASK OUR TEAM

Contact Us About Your Privacy Policy

A direct support path helps you handle a privacy question without guessing which account screen to use.

Privacy request Use support chat for a copy of the personal data connected with your account. Include your account identifier and the words Privacy Policy so we can route the request correctly. We may verify your phone before sharing any account-linked material.
Wallet reference If a DANA, OVO, GoPay or QRIS receipt appears beside the wrong account activity, send its reference through the account support path. We use the reference to check status and limit the discussion to the transaction record involved.
Correction request Tell us which account field or device detail needs correction and why. After an account check, our team can explain the next step, record the request and tell you if a legal or operational reason requires part of the record to remain.
DATA HANDLING

Explore How rokok11 Handles Your Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Account records

We use the account details you submit to create access, verify the phone connected to that access and respond to requests made through support. If a field changes, we compare the request with the existing account record before applying the update.

Device signals

Browser type, device signals and sign-in time can help us spot an unusual login or protect an account session. These signals support account security; they do not give us permission to read unrelated content stored on your phone or computer.

Cookies

Cookies can remember a session choice, language setting or route back to the account area. You can manage cookies through your browser controls. Turning some off may affect account navigation, but it does not remove your right to ask how cookie data is used.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain practical references such as status, amount record and time needed for account reconciliation. We use those references for the stated account or payment purpose, not for unrelated profiling.

Retention period

We retain records only while they support account operation, fraud checks, dispute handling or a legal duty. When a record no longer serves one of those purposes, our process is to delete it or separate it from direct account identification where appropriate.

Your request

You can ask what personal data we hold, request a correction, ask about deletion where available, or question a particular use. Send the request through support chat with enough account context for verification, and we will explain any limit that depends on local law.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the questions we expect you to ask before creating access or linking a local wallet. They explain the account step, the records connected with payment status, browser behaviour and the route for changing or receiving your data. If your situation is not listed, support chat can direct the request after confirming the relevant account details.

The rokok11 Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can request access or correction through support chat.

Yes. The Privacy Policy covers references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account status. We use those references to match a cashier event with your account and investigate a receipt or status question.

You can request a copy of the personal data linked to your account through support chat. Include your account identifier and explain that the request concerns the Privacy Policy. We may complete a phone verification step before releasing account-linked material.

Send the correction request through the account support path, identify the field that is wrong and provide the reason for the change. We compare the request with your account record first, then explain whether the correction can be applied.

Cookies may remember a session choice, language setting or route to your account area when you use a mobile browser. Your browser controls let you manage them. Some changes can affect navigation, while your Privacy Policy request rights remain available.

We keep account and wallet references while they support access, security checks, payment reconciliation, dispute handling or a legal duty. After that need ends, we follow a deletion or separation process. The exact outcome can depend on local law.

Use support chat from the account area and describe whether you need access, correction, deletion or an explanation of a data use. Add the relevant account identifier, device detail or wallet reference, but do not send unrelated private material.