Reference

rich7 Privacy Policy For Your Account Data

Your account details, wallet status and device sign-in records are covered by the rich7 Privacy Policy, so you can see what we collect and why.

Account dataWallet recordsDevice accessPrivacy requests
rich7 rich7 Privacy Policy For Your Account Data
REQUEST SUPPORT

Get Help With Privacy Requests

A privacy request starts with the support path inside your account, where we can connect your question to the right account record. This keeps a request separate from general lobby questions and helps us check wallet or device details safely. If you are in Denpasar or elsewhere in Indonesia, access remains where local law permits, and we ask you to use the account contact route rather than send sensitive details through an unverified message.

Team online

Account data request

Ask us to check the account details connected with your phone verification and sign-in record. We may request account identifiers before sending data or discussing a change.

Wallet record check

For DANA, OVO, GoPay, QRIS or bank transfer references, include the payment date and status shown in your account. We use those details to locate the matching record.

Access concern

If a mobile browser or desktop sign-in looks unfamiliar, contact us through the account support path. We can review the device record and help protect access without asking for your password.

DATA HANDLING

How rich7 Handles Account Data

We keep this policy practical by linking each data use to an account action, such as phone verification, a wallet status check or a device sign-in.

Collected details

We may receive your phone verification details, account profile entries, sign-in events and payment references.

Cookie use

Cookies and similar browser storage can remember a session path and basic device settings.

Account security

We use sign-in records, device signals and account checks to spot unusual access.

Payment matching

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references are used to match wallet activity with the correct account.

Retention periods

We keep categories of data for the period needed for account safety, payment reconciliation, dispute handling or a lawful request.

Changes and contact

To request access, correction or removal of eligible details, use the account support route and state the change clearly.

Privacy Policy Questions For rich7 Accounts

These Privacy Policy answers focus on the account steps Indonesian customers ask about most: phone verification, mobile sign-in, wallet references, cookies and requests to change stored details. If your case involves a specific payment or device, include only the reference needed to locate it and use the account support path.

The rich7 Privacy Policy covers account details, phone verification, device sign-ins, cookies, wallet references and support requests. It also explains retention, security checks and how to request access or correction.

We may store payment references and status data from DANA, OVO, GoPay and QRIS to match activity with your account. We use the reference for reconciliation and support checks, not as your password.

Phone verification helps connect account access to the correct person and supports security checks when a device or sign-in looks unusual. We may confirm ownership before discussing account data or changes.

The Privacy Policy includes device and browser records linked to mobile sign-in, session cookies and access attempts. Clearing browser storage can remove the session path and may require phone verification again.

Yes. Use the account support route, describe the correction and provide the account identifier requested by our team. We may verify ownership before changing profile, phone or payment-reference details.

Payment records are kept for the period needed for account safety, reconciliation, disputes or a lawful request. Ask support about the category connected with your DANA, QRIS, bank transfer or wallet reference.

You can request access to eligible account and device records through the support path. We may ask for ownership checks, and any access or eligibility decision depends on local law.