Reference

napoleon4d Privacy Policy for Your Account

Your account details, phone verification and wallet records stay tied to a clear Privacy Policy on napoleon4d.

Phone verificationWallet record clarityCookie choicesData requests
napoleon4d napoleon4d Privacy Policy for Your Account
CONTACT YOUR WAY

Privacy Help Beside Your Account Path

A privacy request should not get lost beside a wallet question, so we keep the contact route close to your account settings. When you write to our support desk, include the phone number or account identifier connected with the request, the relevant payment rail, and the change you want us to check. We may ask for a simple identity confirmation before discussing records, especially when a request concerns QRIS, OVO or a device sign-in.

Team online

Account contact

Use the support contact path shown after account access and state that your request concerns the Privacy Policy. Adding your registered phone number helps us locate the correct account without asking you to send a wallet password or full payment credentials.

Wallet record check

For a DANA, GoPay, QRIS or bank transfer question, attach the receipt reference and date rather than a full wallet screen. We compare the reference with the account record, then explain what was stored and whether a correction request can be made.

Device access concern

If a mobile browser or desktop sign-in looks unfamiliar, contact support through the account path and describe the device and approximate time. We can review sign-in signals, explain the security step and help you secure the account before discussing private records.

DATA HANDLING

What Our Privacy Process Covers

We apply the Privacy Policy to the practical moments that affect your account: opening access, confirming a phone, checking a wallet status, browsing from a device and asking us to change a…

Account creation

When you open an account, we use the details you submit and your phone verification status to create the account record. This step helps us distinguish your account from another person using the same device and gives support a clear reference for privacy requests.

Cookie controls

Cookies can keep your session open, remember selected settings and help us understand whether a page loads correctly. Your browser controls can restrict or remove them, although changing cookie settings may require you to sign in again before viewing account or wallet records.

Payment matching

DANA, OVO, GoPay and QRIS references are used to match a payment status with the correct account. Bank transfer and virtual account records follow the same principle. We use the reference and status, not your private wallet password, when checking a receipt.

Security signals

We may record browser type, operating system, approximate connection details and sign-in time to identify unusual account access. A new mobile device can trigger an additional check. These signals support account protection and are not presented as a public profile.

Retention choices

We keep account, payment and security records only for the period needed for account operation, dispute handling, safety checks and legal duties. When a record is no longer needed for those purposes, our process is to remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct an inaccurate phone, account detail or payment reference through the support route. Tell us what appears wrong and provide the matching account identifier. We may retain a request record so we can show how the correction was handled.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening or using an account from Indonesia. We cover phone checks, wallet references, cookies, device access, record changes and the local-law condition. If your question is not listed, use the account contact path and include the specific record or payment reference you want us to examine.

It covers account details, phone verification, sign-in and device signals, cookies, payment references and activity connected with the account. It also explains why we use DANA, OVO, GoPay, QRIS, bank transfer or virtual account records when matching a payment status or handling a support request.

Phone verification helps us confirm that the account access request is connected with you and gives support a reliable account reference. We may use the verification status during a new-device check or privacy request, but we do not need your wallet password to match DANA or QRIS records.

Yes. Contact support through the account path, identify the field or payment reference that appears wrong, and explain the correction needed. We may ask for identity confirmation before changing a phone number or account detail, and we keep a request record showing how the change was handled.

On a mobile browser, cookies can keep your session active, remember account settings and help us detect page or sign-in issues. You can remove or restrict them in your browser controls. After that change, you may need to sign in again before viewing wallet or account records.

Yes. We may store a payment reference, amount, date, status and receipt detail needed to reconcile an account action. We do not request your private wallet password. For a question about a payment, send the reference rather than a full wallet credential or secret.

We retain account, payment and security records for the period needed to operate the account, resolve disputes, protect access and meet legal duties. When those purposes end, our process is to remove the record or separate it from direct account identifiers, subject to local requirements.

You can contact us through the account support route to ask what account, device or wallet records are connected with your access. We may verify your identity first. Availability of a request or account access depends on local law and applies where local law permits.