Reference

grenbat88 Privacy Policy for Your Account

grenbat88 Privacy Policy explains how we collect, use and protect data when you open an account, check DANA or QRIS status, and enter the lobby from your phone…

Account dataWallet recordsCookie choicesAccess requests
grenbat88 grenbat88 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Your Data

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages. Use the support request path connected to your account area, describe the record you are asking about, and include the relevant wallet or device context. We use those details to route a request about access, correction, deletion or a payment record.

Team online

Account support path

Open the support route beside your account access and state whether your request concerns phone verification, login activity or a stored contact detail. We can then match the request to your account record.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and receipt status shown during the cashier step. This gives us a practical route to locate the relevant record.

Change request route

Ask through the account support path when you need data corrected or want to understand retention. We may request an account step to confirm that the request comes from you.

SIX DATA CONTROLS

Six Controls Behind Your Privacy Policy

We apply the same Privacy Policy process across account creation, wallet checks and mobile access.

Account creation

When you open an account, we collect the contact and verification details needed to create a usable login. Phone verification helps us connect the correct person with the account record.

Mobile device signals

A mobile browser may send device type, session time and security signals when you move from login to the lobby. We use these signals to identify unusual access, not to replace your account details.

Cookie settings

Cookies can keep a session active and remember selected account settings. You can clear or restrict them through your browser controls, although some account steps may need to be completed again.

Account security

We use login events, verification results and device signals to protect account access. If a sign-in or wallet status appears unusual, our support path may ask for matching account details.

Record retention

We retain account, wallet and security records only for the period needed for the stated account, payment matching or security purpose. You can ask support how a particular record is handled.

Policy changes

If this Privacy Policy changes, we place the revised wording on this page and show the applicable date. Check the page before an account step when you want the current data practice.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. If your situation is different, use the support route with the account step, payment reference or device detail that matches your question.

It covers account creation, phone verification, login activity, device signals, cookies, wallet records and requests to access or change your data. The same scope applies on mobile browsers and desktop access.

We record payment references, status and receipt details so DANA or QRIS activity can be matched to the correct account. This helps us investigate a missing status without requesting unrelated account data.

Yes. Send a correction request through the account support path and identify the field that needs changing. We may ask you to complete a verification step before making the change.

The policy allows us to record device type, session time and security signals when you use a mobile browser. These records help protect login access and are separate from your wallet receipt details.

Yes. Use your browser privacy controls to clear or restrict cookies. Afterward, your session or selected settings may not remain, so you may need to complete the account access step again.

Retention depends on the purpose of the record, such as account security, payment matching or a requested support check. Ask through the support route for the handling of a specific record.

Use the support request path connected to your account area. Include your account step, the relevant DANA, OVO, GoPay or QRIS reference, and the change or access request you want us to review.