Reference

Privacy Policy for ninja338 Accounts

Our Privacy Policy explains what we collect when you open a ninja338 account, sign in on mobile, or use DANA, OVO, GoPay and QRIS for account activity.

Clear data purposesWallet activity contextAccount access choicesContact path included

Explore Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

ninja338 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect account details that you provide during registration, including contact details used for phone verification before account access. We also receive technical details such as device type, browser settings, approximate access records and pages opened, which help us keep a sign-in session working across mobile

1
and desktop. Payment records can show a selected rail, amount, reference and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity; we do not use this page to request your wallet password or banking PIN. We may use cookies or similar tools to
2
remember sessions and understand which policy pages are opened. Access and eligibility depends on local law. You can ask what we hold, request a correction, or ask how long a record is retained through our support path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE TEAM

Reach Support About Your Privacy Policy

A direct support request gives you a practical route when a privacy question concerns your account, device or wallet record.

HOW WE HANDLE DATA

Browse the Privacy Policy Safely

Our handling approach follows the account steps you actually take: registration, phone verification, sign-in, wallet selection and support contact.

Registration details

During the account path, we use the contact details you submit and the phone verification step to connect access with…

Device signals

A mobile browser or desktop browser can send basic technical signals such as browser type, device details and access time.

Cookie choices

Cookies or similar storage may remember a sign-in session and help us see which policy pages are opened.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record may contain a rail name, reference, amount and status.

Retention checks

We keep account and support records for as long as needed for account operation, dispute handling or a legal requirement…

Change requests

To request access, correction or removal, contact support with your registered contact detail and a precise description of the data…

Find Answers About Privacy Policy

These Privacy Policy answers address the account and access questions we hear most often from people in Indonesia. They cover registration details, cookies, device records, payment references and requests to change stored data. If your situation is different, use the support route with the account contact detail and receipt reference that relate to your question.

The ninja338 Privacy Policy covers details collected during account registration, phone verification, sign-in, device access, cookie use, support contact and wallet activity. It also explains how you can ask about stored data, request a correction or ask whether a record can be removed.

Phone verification helps connect account access with the contact detail you submitted and helps us respond to account privacy requests. If you contact support about a profile, we may use that verification context to confirm that the request comes from the account holder.

Yes. The Privacy Policy covers payment references linked to account activity through DANA, OVO, GoPay, QRIS, bank transfer and virtual account rails. These records may show a selected rail, reference, amount and status, but a wallet PIN is not needed for a privacy request.

When you sign in through a mobile or desktop browser, technical records may include device type, browser settings, access time and session details. We use these signals to understand account access and investigate a sign-in concern, rather than to collect secret wallet credentials.

Cookies or similar browser storage can remember a session and help us understand which policy pages are opened. You can manage or clear them through your browser settings. Clearing storage may sign you out or change how the account access path works.

You can contact support with the registered contact detail on your account and describe the data you want copied or corrected. We may verify ownership before responding. A clear request helps us distinguish a privacy request from a DANA, OVO, GoPay or QRIS status query.

You can ask us to remove personal details where local law permits and where no operational, dispute or legal reason requires continued retention. Send the request through support, identify the account record involved and include any relevant receipt reference without sharing a wallet PIN.

Privacy Policy for ninja338 Accounts

Reach Support About Your Privacy Policy

Browse the Privacy Policy Safely

Registration details

Device signals

Cookie choices

Payment references

Retention checks

Change requests

Find Answers About Privacy Policy

01 What does the ninja338 Privacy Policy cover?

02 Why does ninja338 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data can ninja338 collect?

05 How do cookies affect the ninja338 Privacy Policy?

06 Can I request a copy or correction of my account data?

07 Can I ask ninja338 to remove my personal details?

Related Pages