Reference

Privacy Policy for Your nadim138 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your nadim138 account.

Clear data purposesWallet record controlsMobile and desktop access
nadim138 Privacy Policy for Your nadim138 Account
CONTACT DATA HELP

Get Privacy Policy Help Through Support

A direct support path helps you ask about personal data without explaining your entire account history.

Privacy request Send a clear request through our available support channel with your account identifier and the data action you want, such as access, correction, or deletion. We check account ownership before sharing personal details.
Wallet record check If a DANA, OVO, GoPay or QRIS record looks unclear, include the transaction reference and date. We use that detail to locate the relevant account entry without asking you to send an unnecessary password.
Login assistance When privacy access is blocked by a login issue, contact support through the same account-help route. We can explain the verification step and the documents or account details needed to protect your records.
SECURITY AND RETENTION

What We Do With Your Account Data

Privacy Policy choices are easier to use when each data practice has a clear purpose. We separate account access, payment status, support handling, and security checks so a request can be routed…

Account details

We use your submitted account details and verified phone information to identify your account, complete access checks, respond to requests, and prevent another person from receiving account data. We do not need your password in a support message.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status and resolve receipt questions. These records are handled for account support, security checks, dispute handling and other stated operational needs.

Cookies

Cookies and similar device signals can keep a session working, remember access preferences, and help us detect unusual activity. You can manage browser cookie settings, though changing them may affect account access or saved session behaviour.

Security checks

We may compare login timing, device signals and account actions to identify suspicious access. A security check can pause a request while we confirm ownership, especially when a wallet status change or phone detail does not match.

Retention period

We keep personal and transaction records for the period needed for account operation, security review, dispute handling, or a legal obligation described by our processes. When a record is no longer needed, we remove or de-identify it.

Your request path

You can ask what personal data we hold, request a correction, ask about deletion, or raise a concern through support. Include enough account detail for ownership checks, and we will explain any limit that depends on local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often. They explain what to send, how verification works, and which data practices apply when you access the service from Indonesia. If your request involves a specific transaction, keep the relevant receipt or reference ready so support can locate the correct record.

The Privacy Policy covers account details, phone verification, device and session signals, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks, requests for access, corrections and deletion.

Contact support with your account identifier, the phone or email detail attached to the account, and a clear request for access. We verify ownership before discussing personal records, then explain the available response path and any restriction that depends on local law.

Yes. The Privacy Policy covers payment references used to match account status and resolve receipt questions. If you contact us about QRIS, DANA, OVO or GoPay, provide the reference and date where possible. We do not need your password for this check.

Device signals and cookies help keep your session working, remember selected access settings, and identify unusual login behaviour. A mobile browser may create different signals from a desktop browser. You can change cookie settings, but account access may then behave differently.

You can ask support to correct inaccurate details or ask whether deletion is available for a specific record. We first confirm account ownership. Some records may need to remain for security, dispute or legal needs where local law permits.

We retain information for as long as it is needed to operate the account, complete security checks, resolve disputes, or meet a stated legal need. After that period, we remove or de-identify the record according to our retention process.

The page is available for you to read before an account step, while service access and eligibility depend on local law. If you are in Indonesia, support can explain the applicable account and data request path for your circumstances.