Reference

007n7 Privacy Policy for Indonesia Wallet Access

007n7 Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet statusCookie choicesPolicy requests
Explore Our Lobby Read FAQ
007n7 007n7 Privacy Policy for Indonesia Wallet Access
HELP WITH YOUR DATA

Privacy Questions Beside Your Cashier

A clear support route helps when a privacy request and a wallet receipt arrive together.

Account request Use the account help route to ask what personal data we hold, why it is used, or which details are connected with your login. Include your registered phone number so we can match the request safely before discussing account records.
Wallet receipt check If a DANA, OVO, GoPay or QRIS reference appears beside a privacy question, send the transaction reference and status only. We can compare it with our records while keeping your wallet PIN, password and full payment credentials out of the conversation.
Access correction When your phone verification or account details need correction, contact support from the signed-in account path where possible. We may ask for a verification step before changing identifying data, protecting your account from an unauthorised request.
HOW WE HANDLE DATA

Account Security From Login to Lobby

We handle privacy as an operating task, not as a statement kept away from the account flow.

Data collection

We collect details you provide during account creation, including your phone number and verification response. We also receive technical signals such as device type, browser path, login time and lobby actions needed to protect access and keep the account session working.

Cookie controls

Cookies and similar storage can keep your session active, remember selected settings and help us identify unusual login behaviour. You can review available cookie choices through your browser controls, although blocking necessary storage may affect account access.

Account protection

We use phone verification before account access and compare sign-in details with device and session signals. If a request looks unusual, we may pause the change and ask you to complete an account check before releasing personal data.

Payment records

For DANA, QRIS, bank transfer and other listed rails, we retain reference data and status events needed to match a cashier action. We do not need your wallet PIN to check whether a receipt reached the correct account record.

Retention periods

We keep information only for the period connected to account operation, security checks, support handling or transaction reconciliation. When a record no longer serves one of those purposes, our processes address removal, restriction or anonymisation where applicable.

Change requests

Ask us to access, correct or remove personal data through the signed-in support route. State the exact change and the phone number on the account; we may verify ownership before acting, especially when the request affects wallet history or login protection.

Privacy Policy Searches About 007n7

These Privacy Policy answers cover the questions we expect you to ask before opening an account or linking a local wallet. They explain the records connected with account access, the way payment references are handled, and the route for requesting a change. If your situation involves a legal restriction, we will assess it where local law permits and explain the next step through the account support path.

The 007n7 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, lobby activity and payment-status references. It explains why we use each category, how long records may remain, and how you can request access or correction through account support.

Yes. The Privacy Policy covers the DANA and QRIS references, status events and timestamps needed to reconcile an account action. We may also handle OVO, GoPay, virtual account and bank transfer references, but we do not ask for your wallet PIN.

We use your phone number to create the account record, complete phone verification before account access, protect sign-in recovery and connect a support request to the correct account. It may also help us identify a wallet-status question without exposing another account's details.

Open the signed-in account help route beside the cashier and ask for access to your personal data. Include your registered phone number and a clear request. We may verify account ownership first, then explain which records can be supplied under applicable local requirements.

You can request correction of inaccurate account details through support. Tell us which field is wrong and what it should show, such as a phone number or verification detail. We may ask for an account check before changing information linked to wallet history.

On a mobile browser, cookies or similar storage can keep your login session, remember settings and flag unusual device activity. Browser controls let you remove or restrict them. Necessary storage may still be required for account access, while optional choices depend on the available settings.

You may ask about deletion or restriction through the account support path. We assess the request against account security, unresolved support matters and transaction record duties. Where local law permits, we remove, restrict or anonymise eligible records and explain any data we must retain.

Related Pages

007n7 Indonesia FAQ Account information About Us Indonesia Football Reels 506