Reference

Open raya 22 Privacy Policy Clearly

The raya 22 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS for account payments.

Account dataWallet recordsCookie choicesSupport requests
raya 22 Open raya 22 Privacy Policy Clearly
CONTACT ROUTES

Check Privacy Help Before Contacting Us

A clear contact path helps you act on the Privacy Policy without guessing which team handles your request.

Account access Use the support route attached to your account when you cannot complete phone verification…
Wallet record For a Privacy Policy question about DANA, OVO, GoPay or QRIS activity, share the…
Data request Ask us to correct, explain or remove personal data by naming the account contact…
DATA HANDLING

Browse raya 22 Privacy Controls

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

What we collect

We may receive your account contact details, phone-verification result, sign-in history, device and browser signals, cookie preferences and payment references.

Why we use it

Account data helps us provide access, respond to support and keep your chosen account details current.

Cookies on devices

Cookies and similar device storage can retain settings that make a return visit easier, such as a selected session or…

Account protection

We use phone verification, sign-in checks and security records to reduce unauthorised account access.

How long we retain

We retain account, security and payment-reference records only for the period needed for the stated purpose, account administration, dispute handling…

Requesting a change

You can ask us to access, correct or delete personal data, or question a particular use, by contacting support from…

Ask About Your Privacy Policy Rights

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. They explain the practical steps we use for data access, correction, cookies, security and contact requests. If your situation is not covered, send support a specific question from your registered account path.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, sign-in activity, support messages and payment references. It explains why we use each category, how we protect account access and how you can request access, correction or deletion where local law permits.

Yes. The Privacy Policy includes references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a reference, date or status to investigate an account question; we do not need your wallet PIN or password for a normal support request.

Contact support through the registered account path and ask for a data access request. Include the contact detail on the account and describe the records you need. We verify ownership before responding, then explain what can be supplied and any restriction that depends on local law.

You can ask us to correct inaccurate account details by contacting support or using the account step that lets you edit them. Tell us what is wrong and what should replace it. We may request phone verification or another ownership check before changing the record.

Cookies may remember a session, device setting or preference so your account path behaves consistently. Your browser controls can limit or remove them, although sign-in continuity may change. The Privacy Policy explains the purpose of these files, and support can help with a specific cookie question.

We use phone verification, sign-in records and device signals to identify unusual access and protect the account. A move from mobile to desktop can create a new security check. Use your own device where possible, keep credentials private and tell support about unfamiliar activity.

You may request deletion by contacting support from your registered account path. We verify the request and remove or restrict data where appropriate. Some account, security or payment references may need to remain for dispute handling, fraud prevention or a legal requirement that depends on local law.