Reference

Open Privacy Policy Before Account Access

naga15 --login Privacy Policy explains how we handle the details connected with your account, wallet activity and lobby access, including records linked to DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsCookie choicesAccess requests
naga15 --login Open Privacy Policy Before Account Access
REQUEST HELP CLEARLY

Ask About Your Privacy Policy Choices

A clear support path helps when you need to ask about the Privacy Policy rather than a wallet balance or lobby screen.

Account privacy request Use the support route inside your account to ask what personal data is linked…
Wallet record question If your question concerns DANA, OVO, GoPay or QRIS, mention the wallet name and…
Cookie or device query For a cookie choice or an unfamiliar mobile session, tell us the device path…
DATA HANDLING DETAILS

Browse How naga15 --login Handles Data

Privacy decisions are easier when each account action has a visible data reason. We connect phone verification with account access, keep wallet references beside the related account record and use security checks…

Account collection

During account creation, we collect the details needed to create and protect your profile, including the phone detail used for verification. We do not need you to place private account data in a public message when asking about this Privacy Policy.

Wallet references

A DANA, OVO, GoPay or QRIS action can create a payment reference, status detail and account timestamp. We use those records to match the wallet event with your request, while the wallet provider remains separate from our account records.

Cookie choices

Cookies can keep an account session connected, remember a selected setting or show which policy page was opened. Your browser controls can manage cookie storage, although changing those settings may affect how the account access page responds.

Session protection

When you move from phone verification to the lobby, we may use device and session signals to detect unusual access. If a session needs checking, return through the account page rather than sharing a password or verification code.

Record retention

Some account, payment and support records may remain after a request because we need to close an open action, resolve a wallet question or meet a legal requirement. The Privacy Policy explains the purpose before you ask about a record.

Change requests

You can ask us to correct, access or remove personal data through the account support route, where local law permits. Describe the record and account detail involved; we may need to verify that the request comes from you.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions that arise before account access: what we collect, how wallet records are connected, what cookies do and how to request a change. We keep the route practical for Indonesia, whether you opened the page on a mobile browser in Semarang or checked an account record from a desktop.

The naga15 --login Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security steps and ways to request access or correction.

We collect the details needed to create and protect your account, including contact data used for phone verification. When you select a wallet or bank route, related payment references and status details may be connected with the account action described in the Privacy Policy.

Yes. The Privacy Policy covers the account-side reference, status and timing details created when you use DANA or QRIS, as well as OVO and GoPay. It does not turn the wallet provider into our account system; each service keeps its own records.

We use cookies to keep an account session connected, remember selected settings and understand which policy page was opened. Your browser can remove or block cookies, but that may change how phone verification, account access or the Privacy Policy page behaves.

Sign in through your account page, open the support route and describe the record you want to access or correct. Include the account phone detail and the exact request. We may verify your identity before handling it, where local law permits.

Retention depends on the purpose of the record, such as completing a wallet action, resolving a support request, protecting an account or meeting a legal requirement. The Privacy Policy explains these reasons, and support can help identify the record involved in your question.

Yes. Use the account support route and state that the Privacy Policy question concerns an unfamiliar device or browser session. Do not send your password or phone verification code. We can review the account-side session detail and explain the next access step.