Reference

grenbet Privacy Policy For Your Account

Clear account, device and wallet-data choices are at the centre of the grenbet Privacy Policy.

Account dataWallet recordsDevice choicesPolicy requests
grenbet grenbet Privacy Policy For Your Account
POLICY HELP PATH

Privacy Help Beside Your Wallet Path

A clear contact route matters when a Privacy Policy question concerns your account or wallet status.

Account data help Use the account support path to ask which profile details we hold, including your…
Wallet status check For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time…
Privacy request route Send a removal, access or correction request from the account contact path.
DATA HANDLING

How grenbet Handles Account Data

We keep this policy practical by connecting each data activity to a visible account step.

What we collect

We may collect account details, phone-verification results, sign-in events, device and browser signals, support messages, and payment references connected with…

Why records matter

These records let us open the right account, match a wallet status, investigate a failed step, protect sign-in activity and…

Cookies on mobile

On a phone or tablet, cookies and session storage can remember sign-in state and page choices.

Account security

Phone verification is part of account access, while payment references remain separate from your wallet credentials.

Retention choices

We retain account, support and transaction records for operational needs or applicable obligations, then remove or restrict them when the…

Requesting changes

Ask for a copy, correction, restriction or eligible removal through the account contact path.

Privacy Policy Questions For grenbet

These Privacy Policy answers address the account steps Indonesian customers ask about most, from phone verification and mobile cookies to wallet references and correction requests. If your situation is different, use the account support path with the relevant reference.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps confirm the account access route and protect profile changes. We keep the verification result with the account record, and you can ask how that record is handled through support.

Yes. When you use a phone or tablet, we may process session, browser and device signals needed for sign-in continuity, security checks and page function. Browser settings control cookie removal.

We use payment references and status details to connect a DANA or QRIS activity with the correct account record. We do not ask you to send wallet passwords through our contact path.

You can request an account-data copy through the account support path. Tell us the profile or activity period involved, and we may confirm ownership before providing eligible records.

Send the correction request through the account contact route and identify the inaccurate field. We will check the account record, confirm ownership where needed, and explain any required retention.

Access depends on local law and the policy applies where local law permits. If your location or account status creates a restriction, contact support for the applicable account-path explanation.