Reference

Privacy Policy for Your receh88 Account

Your receh88 Privacy Policy explains what we collect when you open an account, sign in, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesSecurity requests
receh88 Privacy Policy for Your receh88 Account
CONTACT ROUTES

Contact Paths For Privacy Questions

A clear contact route helps when you want to ask about a record, correct an account detail, or question a wallet reference. Sign in first when possible, then use the account support path near the cashier area so we can match your request to the correct account. Include the relevant date, payment rail and device path, but never send a password or wallet PIN.

Team online

Account privacy request

Use the support path connected to your account to ask what personal records we hold, why they are used, or which account step created a specific entry.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, provide the payment reference and status shown in your account. We use those details to trace the correct transaction.

Correction request

If your contact detail or verification record is inaccurate, send the affected field through support. We may ask for an account step that confirms your request belongs to you.

DATA CONTROLS

Security Across Login And Wallet Steps

Our privacy process follows the same account path you use from login to the lobby and cashier.

Data handling

We use contact details, verification results, device signals and activity records to operate account security, trace wallet status and answer privacy requests. We do not ask for your wallet PIN.

Cookie controls

Necessary cookies support sign-in continuity and security checks. You can review or clear browser cookies, although clearing them may require another account verification step.

Account security

We compare sign-in events with device and session signals to identify unusual access. If a check interrupts your account, contact support through the signed-in account path.

Retention periods

We keep account, payment and support records for the period needed to operate the account, resolve disputes and meet applicable legal duties, then remove or restrict them where possible.

Change requests

You can request a correction, access copy or eligible deletion by describing the account field involved. We may verify ownership before changing records tied to DANA or QRIS activity.

Who handles queries

Our account support route receives privacy questions and sends them for handling by the team responsible for account records, cookies, verification details and payment references.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often before registration. They explain the records created during sign-in, payment checking and support contact, plus the steps available if you need access or a correction. For a request tied to your own account, sign in first whenever you can.

It covers account details, verification records, device and session signals, cookies, support messages, and payment references created through DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use the reference, status and time to match a wallet or bank event with your account ledger. This helps us check a stalled cashier status without requesting your wallet password or PIN.

Yes. Send an access request through the account support path and describe the records you want to see. We may verify account ownership before releasing details connected with your sign-in or payments.

Contact support while signed in, identify the inaccurate field, and explain the required correction. For verification or wallet records, we may request an account step that confirms the request is yours.

We retain account, payment and support records for operational needs, dispute handling and applicable legal duties. When a record is no longer needed, we remove or restrict it where the applicable rules allow.

Yes. Account access and related processing depends on local law. Where local law permits, we handle your records under this Privacy Policy and provide the request paths described on this page.

Include your account contact detail, the request type, relevant date, and any DANA, OVO, GoPay or QRIS reference involved. Do not send a password, wallet PIN or unnecessary identity documents.