Reference

Privacy Policy for Your garuda55 Account

Your garuda55 Privacy Policy sets out how we handle account details, phone verification, wallet records and device access before you enter the lobby.

Account dataWallet recordsCookie choicesContact requests
garuda55 Privacy Policy for Your garuda55 Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact path helps when your account details, wallet receipt or access request needs attention.

Privacy request Send a request through our support contact path when you want to ask what account data we hold, why a detail is needed, or whether a correction can be considered. Include your linked phone number and request type so we can direct the matter correctly.
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy question, attach the payment reference rather than sending a full wallet password or security code. We use the reference to locate the relevant record while limiting the personal details shared in the request.
Access concern If a phone verification step or unfamiliar device affects account access, contact us through the same support route and describe the device path. We can review the account-security context without asking you to disclose your password in a message.
DATA HANDLING

What Our Privacy Process Covers

Our privacy process follows the real actions you take: creating an account, verifying a phone number, opening the lobby, selecting a wallet and requesting account assistance.

Account details

We use your account name, linked phone number and verification status to provide account access and route privacy requests to the right record. Please keep these details current, because an outdated phone number can make an account-change request harder to confirm.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with the correct account activity. We do not need your wallet password for that check. Send only the reference and the limited context requested by support.

Cookies and devices

Cookies and device signals can help keep your session connected, remember selected settings and identify unusual login behaviour. You can manage browser cookie settings, although changing them may affect account access, phone verification prompts or the way the lobby loads.

Account security

We may record login time, browser type and device details when protecting an account. If a sign-in looks unusual, we can ask you to confirm the linked phone number before discussing personal data or changing account details.

Data retention

We keep personal data only for the period needed for account operation, payment matching, security checks or a legal requirement. When a record no longer has one of those purposes, it can be removed or separated from direct account details.

Change requests

You can ask us to correct account details, explain a data use or consider removal where local law permits. Send the request through support with your linked phone number; we may verify ownership before making any account-data change.

Privacy Policy Answers for garuda55

These Privacy Policy answers focus on the questions you may have before opening an account or sending a wallet-related request. We explain what data connects to account access, how payment references are used, what happens on a new device and how to reach us. The same policy applies whether you browse from Indonesia on a phone or computer, where local law permits.

The garuda55 Privacy Policy covers account details, phone verification, cookies, device signals, payment references and support requests. It also explains retention, account-security checks and how to ask about correction or removal of personal data where local law permits.

We use your linked phone number to complete account verification, connect you with the correct account and confirm certain privacy requests. It also helps us investigate an access concern without asking you to share a password or wallet security code.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match receipts and status checks with your account, not to request your wallet password.

A new browser or device may create a security signal linked to the login attempt. We can ask for phone verification before discussing account data or changing details. Cookies may also affect session continuity when you move between phone and computer.

You can contact us through the support path and request a correction to account data. Include your linked phone number and describe the inaccurate detail. We may verify account ownership first, and the request is handled where local law permits.

Send a clear removal request through support with your linked phone number and the data you want considered. We assess the request against account security, payment matching and legal retention needs before confirming what can be removed.

Use our support contact path for a Privacy Policy concern and include the account phone number, relevant payment reference or device detail. Avoid sending passwords and wallet security codes. We will route the request for review of the specific privacy matter.