Reference

raiden fighter Privacy Policy for Your Account

raiden fighter Privacy Policy explains how we handle the details connected to your account, including phone verification, login records and wallet activity through DANA, OVO, GoPay or QRIS.

Account recordsWallet activityCookie choicesContact requests
raiden fighter raiden fighter Privacy Policy for Your Account
CONTACT PATHS

Check Privacy Questions Through Your Account

A clear contact path helps you ask what we hold about you, why a record appears or how to request a correction.

Account message Open your signed-in account area and send a privacy question with the phone number…
Wallet receipt For a DANA, OVO, GoPay or QRIS question, include the transaction reference and date…
Access request Ask for a copy, correction or clarification through the policy contact route linked in…
DATA HANDLING

Explore How We Handle Privacy Records

We organise privacy work around practical account events rather than broad claims. Phone verification, device checks, wallet references and support messages each serve a different operational purpose, while…

Account details

We use the phone number and account details you provide to create access, confirm ownership and respond to account questions.

Device signals

Login time, browser type and device signals can help us spot unusual account access.

Cookie settings

Cookies can keep a session active and remember basic choices.

Wallet records

Payment references for QRIS, bank transfer or virtual account steps help us trace status and reconcile an account entry.

Retention periods

We retain account, security and transaction records only for the operational, dispute and legal needs described in the Privacy Policy.

Change requests

You can ask us to correct inaccurate account details or explain a processing purpose.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. We explain the account step, device handling and contact route in plain language, while eligibility remains dependent on local law and availability where local law permits.

The Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm that the person requesting account access or a data change controls the profile. We may ask for it before discussing login history, wallet records or correction requests.

Yes. The Privacy Policy covers relevant mobile browser signals such as session details, device type and login timing when you access the account or lobby from a phone or tablet.

We use DANA and QRIS references to match an account transaction, check its status and respond to a receipt question. We do not need your wallet password to perform that record check.

You can send a request through the account contact route, identify the record you want copied or corrected and complete phone verification if asked. We handle the request under applicable local rules.

Retention depends on the record type and the operational, dispute or legal reason for keeping it. The Privacy Policy describes these purposes, and we remove or otherwise handle records when they are no longer needed.

Use the privacy contact route in your signed-in account footer. Include a short description, relevant date or transaction reference, and never send a wallet password or complete security code.