Reference

Privacy Policy for Your ningrat4d Account

ningrat4d Privacy Policy explains what we collect when you create an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
ningrat4d Privacy Policy for Your ningrat4d Account
HELP WITH YOUR DATA

Get Privacy Help Near Your Account Path

A clear contact route helps you resolve a data question without repeating your account story.

Account access If your phone verification or sign-in record looks wrong, tell us which device path…
Wallet reference For a DANA, OVO, GoPay or QRIS record, share the date, amount reference and…
Privacy request To request access, correction or removal where available, state the request clearly and provide…
HOW WE HANDLE RECORDS

Your Data Choices Inside ningrat4d

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Data collection

We collect registration details, verification results and technical sign-in signals because they help us identify your account and protect the access path. Browsing a page such as Rocket Crash may create a basic request record needed to load that page correctly.

Cookie settings

Cookies can keep a session active, remember a language or device setting and help us understand whether a page loads correctly. You can adjust browser cookie controls, although changing them may require another sign-in before the lobby opens.

Account security

We use phone verification and sign-in checks to reduce unauthorised account access. Never send us your password, wallet PIN or one-time code. If a device no longer belongs to you, contact us with the account identifier so we can review the access record.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the reference needed to match a cashier event with your account. We do not need your wallet password to investigate a receipt or status question.

Retention timing

We keep personal records while they support account operation, fraud checks, dispute handling or a legal requirement. When the relevant purpose ends, we delete or anonymise the record where practical, while limited security logs may remain for a defined need.

Changes and contact

If your name, contact detail or privacy preference needs correction, send a request through the available support route. We verify that the request comes from the account holder, explain the result and update the record where the request is permitted.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and device questions you may have before using ningrat4d. They explain what happens around registration, wallet references, cookies, access checks and requests to change or remove personal data. If your situation is not covered, use the privacy contact path with the account detail that lets us locate the correct record.

The Privacy Policy covers registration details, phone verification, device and browser signals, cookie settings, lobby requests and payment references. It explains why we use each category, how access is limited and how you can ask about, correct or remove personal data where local law permits.

No. Our Privacy Policy concerns the reference needed to match a DANA or QRIS payment event with your account, not your wallet password or PIN. When you ask about a receipt, send the visible reference and account contact, never a secret code.

A device and browser can create sign-in signals such as session details, browser type or security events. We use them to protect account access and diagnose loading problems. The Privacy Policy does not require you to send us your phone password or private device content.

Use the privacy support path and identify the email or phone detail linked to your account. Say whether you want access, a correction or removal where available. We may request an account-matching step before sharing records, so personal data is not disclosed to the wrong person.

Yes. You can change cookie controls in your browser and contact us if a stored setting still appears incorrect. Some session functions may require a fresh sign-in after that change. Our Privacy Policy explains that cookies support access, settings and page performance checks.

We retain records while they are needed for account operation, security checks, receipt questions, disputes or a legal requirement. After that purpose ends, we delete or anonymise them where practical. The exact period can depend on the record type and on what local law requires.

The Privacy Policy is intended for the Indonesia access path, but account access and eligibility depend on local law. If you are unsure whether the service is available to you, check the applicable local rules before creating an account or sending personal details.