Reference

raja neko Privacy Policy for Your Account

The raja neko Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Account clarityWallet privacyCookie choicesPhone verification
raja neko raja neko Privacy Policy for Your Account
CONTACT YOUR WAY

Get Privacy Help Without Guesswork

A direct support route helps you ask about the Privacy Policy before changing account details or checking a wallet record.

Privacy request Send a clear request through our listed support channel when you want to know…
Wallet record If a DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI reference looks unfamiliar…
Account access When phone verification or a device sign-in blocks your privacy request, use the same…
OUR DATA PRACTICE

What We Keep Secure And Why

The Privacy Policy is applied to the records needed for account access, wallet reconciliation, fraud checks and support replies rather than to unrelated browsing.

Account records

We use your phone number, verification result and account activity to provide access and answer account questions. A fresh device sign-in may create a security event. We do not ask you to place a password or one-time code inside a privacy request.

Payment references

Payment records can include a DANA, OVO, GoPay or QRIS reference, plus a bank transfer or virtual account reference. We use these identifiers to reconcile status and receipts, not to request your wallet PIN or full banking credentials.

Device signals

Your browser and device may provide sign-in time, session details and security signals. These help us investigate unusual access when you move from a mobile phone to desktop. We use the signals for account protection and privacy support, not as a public profile.

Cookies

Cookies can preserve a session choice, language setting or security preference while you move between account pages. Your browser controls cookie removal and blocking. Some account functions may need a necessary cookie, while optional settings remain subject to the choices available on your device.

Retention timing

We keep a record only for the period needed for its stated purpose, account safety, dispute handling or a legal duty. Payment and verification records may therefore follow a different schedule from a temporary cookie. We review stored records and remove or anonymise them when appropriate.

Change request

You can ask us to correct an account detail, explain its use, provide a copy where available or delete it where local law permits. Send the request through our listed support channel; we verify account ownership first and explain any part we must retain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening a raja neko account. They explain the practical link between phone verification, wallet references, cookies, device access and support requests. If your situation involves a legal restriction or a record we must retain, we will explain that distinction through the account support route.

It covers account creation, phone verification, sign-in signals, cookies, payment references and support requests connected with your account. It also explains how we use, protect, retain and change those records. Access or eligibility depends on local law, so the policy applies with that condition.

We use your phone number to create an account, complete the required verification step and help protect access when a new device signs in. It also lets support locate the correct account. Do not send a password or verification code when asking about Privacy Policy rights.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay and QRIS when they are linked to your account. We use a reference, date and status to reconcile a receipt or investigate a query. We do not need your wallet PIN for that process.

Cookies can remember a session, language choice or security setting while you move between account pages on mobile or desktop. Your browser lets you remove or block them. Necessary cookies may support sign-in, while optional cookie choices remain under your browser and page controls.

You can request a correction through the support channel listed on our contact page. Tell us which account detail is wrong and what it should say, without sending a password or wallet PIN. We verify ownership first, then confirm the change or explain why a record remains.

You may ask us to delete or anonymise personal data where local law permits. Some account, payment or verification records may need to remain for security, dispute handling or a legal duty. We will identify the affected record and explain the reason before completing the request.

There is no single period for every record. Temporary cookie data, account details, device security events and payment references can have different retention needs. We keep each record for its stated purpose, account safety, dispute handling or legal duty, then remove or anonymise it when appropriate.