Reference

Privacy Policy For Your nawa55 Account

Our Privacy Policy explains how we handle the details connected with your nawa55 account, from phone verification before access to wallet records created through DANA, OVO, GoPay or…

Account clarityWallet recordsCookie choicesAccess requests
nawa55 Privacy Policy For Your nawa55 Account
HELP WITH PRIVACY

Get Clear Answers Through Account Help

A direct account-help route lets you ask about the Privacy Policy without mixing a privacy request with a general lobby question. Tell us which account detail, cookie choice or wallet record you mean, and keep your request tied to the email or phone number on your account. We can then explain the next step, check a payment reference or direct a correction request to the right place.

Team online

Account help route

Use the account help path when you want to ask how nawa55 stores login details, phone verification records or device-session data. Include the email or phone number linked to your account so we can identify the request before discussing account-specific details.

Payment record check

If your privacy question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the payment reference rather than a wallet password. We use that reference to locate the relevant status and explain which account record is involved.

Correction request

Ask us to correct an inaccurate account detail through the same support path used for your nawa55 account. We may request a verification step before changing phone, email or payment-linked records, helping prevent an unapproved person from altering your data.

DATA HANDLING

What Your Privacy Policy Covers

The Privacy Policy is built around the records created when you open, access and manage your account. That includes identity and contact details, sign-in events, device signals, cookie choices and payment references.

Account details

We use the contact details you submit for account access, phone verification and privacy-related replies. Keeping your phone number and email current helps us match a request to the correct nawa55 account before we discuss or change personal records.

Device sessions

When you sign in from a mobile browser, we may record device and session signals needed to keep the account secure and detect unusual access. These signals help us investigate a login question without requiring your wallet password or private message content.

Cookies

Cookies can remember a session, support account navigation and help us understand whether a page request came from an active account. Your browser settings can manage cookies, although changing them may require another login or affect some privacy-related page functions.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain payment references and status details needed to match a transaction with your account. We do not need your wallet password to investigate a receipt or status question.

Retention periods

We keep account, security and payment-linked records only for the period needed for account operation, dispute handling, legal duties or security checks. When a record is no longer needed for those purposes, our process removes or anonymises it where applicable.

Your request

You can contact us to ask what account data we hold, request a correction or ask how a cookie or wallet record is used. We may verify your control of the account first, then explain the available action under local law.

Answers About nawa55 Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access: what data is collected, how wallet records are handled, how cookies affect a mobile session and where to send a request. If your situation is different, use the account help route with the relevant reference and we will explain the applicable step.

The nawa55 Privacy Policy covers account and contact details, phone verification, sign-in and device-session signals, cookies, payment references and support requests. It also explains retention, correction requests and the way we handle privacy questions connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us confirm account control before access and before certain account changes. It also gives our support team a practical way to distinguish your request from an unauthorised message. The Privacy Policy explains how that verification record is used for access and security.

Yes. The Privacy Policy covers payment references and status details linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a receipt or status question with your account, without asking for your wallet password.

Cookies may keep your account session active, support navigation and help identify whether a request comes from an active device session. You can manage cookies through your browser. If you remove them, the mobile path may ask you to sign in again or change how some pages load.

You can request a correction through the account help route if your phone number, email or another account detail is inaccurate. We may ask for a verification step before making changes. We then explain the available action and any timing required under local law.

We retain account, security and payment-linked records for the period needed to operate the account, handle disputes, meet legal duties or investigate security events. The Privacy Policy does not promise one universal period because retention can depend on the record type and local law.

Send your Privacy Policy question through the account help path and identify the account detail, cookie choice or payment reference involved. Use the email or phone number linked to your account where possible. We may verify account control before discussing personal data or processing a change.