Reference

Open rakyat62 Privacy Policy Access

Our Privacy Policy explains how rakyat62 handles the account details you provide before you enter the lobby, including phone verification and wallet status.

Clear data purposesWallet record controlsMobile access notesContact request path
rakyat62 Open rakyat62 Privacy Policy Access
CONTACT POLICY HELP

Get Policy Help Through Account Support

A clear contact route matters when you want to ask what data we hold or why a wallet record appears in your account.

Account request Use your signed-in account path to ask about personal data, phone verification records or…
Wallet receipt For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference shown…
Device access If a mobile browser does not recognise your session, tell support which device path…
DATA CONTROL PRACTICE

Explore Device And Wallet Data Controls

Privacy choices should remain understandable when you move from phone verification to the lobby. We apply the Privacy Policy to account records, wallet references, device activity and support messages, with access limited…

Account collection

We use your phone number and verification result to establish the account path and help protect access. Your account settings are handled separately from wallet credentials, which should never be sent to our support route.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a payment status with your account. We use the reference for checking and support rather than requesting your wallet PIN.

Cookie choices

Cookies can keep a mobile session connected and remember a selected preference. If you clear browser storage, the next visit may ask you to verify the account again before showing account-specific content.

Security signals

Device and session signals help us spot access that does not match your usual account pattern. A security check may pause account access until we can confirm that the request came from you.

Retention handling

We keep account, payment-reference and support records for the period needed for their stated purpose, account protection and applicable legal duties. When that need ends, handling follows our internal retention process.

Change requests

Ask through the signed-in account support path if you want to access, correct or question personal data. Include a clear request and matching account detail so we can respond without exposing another account.

Check Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the route practical: check the signed-in account area, use the reference from DANA or QRIS when a payment record needs checking, and avoid sending secret credentials. Where access or eligibility is discussed, it depends on local law.

It covers account details, phone verification, device and session signals, cookies, wallet or bank references, support messages, retention and requests for access or correction. It also explains how these records are used for account operation, security, support and applicable legal duties.

We use the phone number and verification result to establish your account path and help protect access. If a sign-in pattern changes, the record can support an account-security check without asking you to reveal a wallet PIN or password.

Yes. When you use DANA, OVO, GoPay or QRIS, we may keep a payment reference or status record needed to match the transaction with your account and answer a receipt question. Wallet credentials remain private and should not be sent to support.

Use the support path inside your signed-in account and state that you want to access your personal data. Add the matching phone number or account reference, but leave out your password, wallet PIN and one-time code.

Yes. Send a correction request through the account support path with the record you believe is wrong and the accurate replacement detail. We may need to confirm account ownership before changing information tied to phone verification or payment status.

Cookies can support session continuity and remember a selected preference in your browser. Clearing them may remove that setting and require another account check. Your browser controls can manage stored cookies, while account-specific requests use the support path.

Yes. Account access and eligibility depend on local law. The Privacy Policy applies to the services available in your supported region, and we may ask for account or security checks before providing account-specific data.