Reference

Privacy Policy for Your gerai55 Account

gerai55 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and access to the lobby.

Clear data purposesWallet record checksAccount access controlIndonesia privacy contact
gerai55 Privacy Policy for Your gerai55 Account
CONTACT DATA DESK

Ask About Privacy Before Account Access

A direct support request gives you a practical way to ask what data we hold, why a record is needed or how a payment reference was used. We ask you to contact us through the account help route rather than sending wallet PINs or full payment credentials in a message. Include the account phone number, the date of the relevant action and a short description of the request so we can locate the right record. Where local law permits, we will explain the next step for access, correction or deletion.

Team online

Account help

Use the account help path when a phone verification record, sign-in event or profile detail appears incorrect. We may ask you to confirm ownership through the registered phone before discussing account data, so a private request is not disclosed to another person.

Wallet status

For a DANA, OVO, GoPay or QRIS record, send the payment date, amount reference shown in your account and the wallet name. Do not include a PIN. We use those details to separate a pending status question from a request to change personal data.

Privacy request

Ask for a copy, correction or removal of eligible personal details through our support route. Tell us which account record you mean and how we should reply. We may retain a request history when a legal, security or transaction duty requires that record.

YOUR CONTROL PANEL

What We Handle and Why

Privacy Policy choices should be understandable before you open the lobby, so we connect each data use to a recognisable account action.

Account details

We may use your name or account identifier, registered phone number and verification result to create the correct account path.

Payment references

A payment record can include the selected rail, reference value, status and time connected with your request.

Cookies and device use

Our pages may use session cookies and device signals to keep you signed in, protect the account path and identify…

Account security

We use login events, verification activity and unusual device or session patterns to protect your account.

Retention choices

We keep personal details only for as long as needed for the stated account, security, support or transaction purpose, subject…

Changing your data

If your phone number, name or account detail is wrong, contact us with the exact field and a safe way…

Privacy Policy Answers for gerai55

These Privacy Policy answers focus on the questions you may have before opening an account or returning to the gerai55 lobby. We explain the records connected with phone verification, device sessions, local payment references and support requests in plain English. If your situation needs a decision about access, correction or retention, contact us through the account help path with the smallest amount of personal detail needed to identify the request.

It covers personal details and account activity connected with registration, phone verification, sign-in, wallet status, payment references, device sessions, cookies and support requests. It also explains why we use those records, how we protect access, when retention may apply and how you can ask about your data.

Phone verification helps us connect an account request to the person who controls the registered phone. We may use the result during sign-in, a phone detail change or an unusual device check. We do not need your wallet PIN or one-time code in a support message.

Yes. The Privacy Policy covers payment references and statuses linked to an account request, including DANA, OVO, GoPay and QRIS. We may also handle bank transfer or virtual account references for reconciliation. These records help us investigate a status without receiving your private wallet credentials.

We may record practical session and device signals such as browser session details, access time and security events. A mobile browser can retain a session cookie between login and the lobby. Clearing cookies may end that session and trigger phone verification when you return.

Contact us through account help and identify the record you want to access or correct. Include your registered phone number only where the support route requests it, plus the relevant date or field. We may confirm account ownership before responding, and the available action depends on local law.

You can send a deletion request through the privacy contact path and explain which account details it concerns. We will assess the request under applicable requirements. Some records may remain when needed for security checks, payment reconciliation, dispute handling or another legal duty.

Retention depends on the purpose of each record and any applicable legal requirement. Session details may serve a short security need, while payment or support records may need longer handling for reconciliation or disputes. Ask support for the retention context linked to your specific account request.