Reference

gaza88 Privacy Policy for Your Account Data

gaza88 Privacy Policy shows how we collect, use and protect the details connected with your account, from phone verification to DANA or QRIS records.

Clear data purposesWallet record contextAccount access stepsPolicy contact route
gaza88 gaza88 Privacy Policy for Your Account Data
CONTACT DATA HELP

Contact Us When Privacy Questions Arise

A clear support route helps when you want to ask what data we hold or why an account check occurred. Use the support path linked from your account area, and include your registered phone detail without sending a password or wallet PIN. We can then connect a privacy request with the correct account and check related payment receipts or status records.

Team online

Account help

Open account help after signing in and describe your Privacy Policy question. We use the registered phone detail to locate the account, while you should keep passwords, PINs and verification codes out of the message.

Cashier context

If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer, mention the transaction reference and date. This lets us compare the payment record without asking you to disclose wallet credentials.

Access request

For a copy, correction or removal request, state the exact data concern and the account phone detail. We may ask for an account check before changing records, helping prevent another person from accessing your data.

DATA HANDLING

Check How Your Account Data Moves

We handle data according to the reason it entered our systems: account access, security, payment matching, support or legal recordkeeping.

Account records

Your phone detail and verification status help us connect sign-in activity to one account. We may also record browser, device and session signals so an unusual access attempt can receive an additional check.

Cookies

Cookies can keep your sign-in path working and help us recognise a returning browser. Clearing them may require you to sign in again and complete the account step before reaching account features.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references support reconciliation. We use transaction identifiers and status details to match activity, not your wallet PIN or banking password.

Security controls

Phone verification, sign-in records and device signals work together when we check account access. Never share a one-time code with support; our team does not need that code to read a request.

Retention period

We keep account, support and transaction records only as long as needed for security checks, dispute handling and legal duties. When a record is no longer needed, our handling process addresses its removal.

Change requests

You can ask us to correct account data or explain its use through account help. Include the specific field or record, and we may verify ownership before making a change.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the questions we expect before account creation or a wallet check. They explain what we collect, how access requests work, why payment references appear in records, and where to send a request. If your situation is not covered, use account help with the registered phone detail and a concise description.

The gaza88 Privacy Policy covers data connected with account creation, phone verification, sign-in activity, device signals, cookies, support messages, payment references and security checks. It also explains retention and change requests.

We may collect your registered phone detail, verification status, browser and device signals, session records, support messages and transaction references. We use each category for account access, security, support or payment matching.

DANA and QRIS references help us match a transaction to the correct account and check an unclear status. The same operational purpose can apply to OVO, GoPay, bank transfer and virtual account records.

Open the account help path, identify the exact field that needs correction and provide your registered phone detail. We may verify account ownership before changing information or confirming the result.

Yes. Cookies and browser signals can keep a mobile sign-in path active and help identify unusual access. Clearing cookies may sign you out, so you may need phone verification again.

We retain records for the period needed for account security, payment reconciliation, dispute handling and legal duties. The period can differ by record type, after which our handling process addresses removal.

Yes. Use account help and describe the request without sending a password, wallet PIN or one-time code. Include the registered phone detail and, when relevant, a payment reference or date.