Reference

rajaspin Privacy Policy for Your Account

Our rajaspin Privacy Policy shows how we handle account details, device signals and payment records when you use DANA, OVO, GoPay or QRIS.

Account data clarityWallet record controlsCookie choices
rajaspin rajaspin Privacy Policy for Your Account
REQUEST HELP DIRECTLY

Get help with privacy requests

A privacy question should not leave you guessing. We keep a support route close to the account and cashier areas so you can ask about stored data, a wallet reference or a device sign-in without explaining your whole account history. Include your registered phone number and the request type, while removing passwords and wallet credentials from your message.

Team online

Account data request

Use the support path shown in your signed-in account to ask what account details are held. We may confirm your phone verification before discussing records tied to your profile.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference through support. We compare it with the account transaction trail without requesting your wallet password.

Device access concern

Tell us when a phone or desktop sign-in does not look like yours. We can help check account access events and explain the next verification step before data is changed.

CLEAR HANDLING PRACTICE

What our privacy controls cover

We explain each privacy control in practical terms so you can decide what to share before using your account.

Account data

We use your registered contact details and verification status to connect requests with the correct account. When you ask for a copy or correction, we first confirm ownership through the account step.

Cookies and devices

Cookies and device signals can remember session settings and help identify unusual access. You can manage browser permissions, but changing them may require another sign-in when you return.

Account security

Phone verification adds an account check before access to protected areas. We do not ask for DANA, OVO, GoPay or bank passwords, and you should never place those credentials in a support request.

Retention periods

We retain account and transaction references only for the period needed for account operation, dispute handling, security checks and legal duties. The policy explains how those purposes affect retention.

Correction requests

If your phone number or another account detail is wrong, contact support from the signed-in account and describe the change. We may request a verification step before updating the record.

Policy contact

For a privacy-specific request, name the data area involved, such as cookies, device access or QRIS receipts. We use that detail to route your question without collecting unrelated account content.

Privacy Policy answers before account access

These Privacy Policy answers cover the searches we hear most often before an Indonesian account is opened. They explain what we collect, why wallet references appear, how device checks work and where to send a request when you need a correction or clarification.

The rajaspin Privacy Policy covers account details, phone verification, device signals, cookies, payment references, retention and requests to access, correct or remove eligible data.

No. We use transaction references and status details for DANA or GoPay activity, but you should never send wallet passwords, bank credentials or one-time codes through support.

QRIS and OVO references help match a payment receipt with the correct account status. We use that record for account support and transaction checks, not to request wallet login credentials.

Sign in, open the support path near your account controls and state that you want a data request. We may confirm your registered phone number before sharing account-linked details.

Yes. Send a correction request from the signed-in account, identify the inaccurate field and provide the requested replacement. We may complete a phone verification step before making changes.

Cookies can retain session settings, while device signals help us identify unusual sign-ins. Clearing cookies may sign you out and can trigger another account check on return.

Where local law permits, we use the minimum account and verification details needed to assess access. Eligibility handling follows the purposes and retention rules described in this Privacy Policy.