Reference

Open garuda404 Privacy Policy Before Account Access

Our garuda404 Privacy Policy shows how we handle your account details, phone verification, device sessions and wallet records before you enter the lobby.

Clear data purposesWallet record handlingPhone verification detailsMobile session controls
Explore Our Lobby Read FAQ
garuda404 Open garuda404 Privacy Policy Before Account Access
CONTACT PATH

Find Policy Help Beside Your Cashier

A clear contact path helps when you need a Privacy Policy answer about login data, a wallet reference or a deletion request. Start from the support route linked in your account area and include the relevant account step, payment rail and approximate request time. We can then check the right record without asking you to send a full password or private wallet credential.

Team online

Account data request

Use the support route in your account area to ask what account data we hold, why it is used and which verification step is needed before we respond. Please include your registered phone number only through the secure account path, not in an open message.

Wallet status question

If a DANA, OVO, GoPay or QRIS status appears unclear, send the payment reference through the cashier-linked support path. We use that reference to locate the relevant record, explain its status and avoid exposing unrelated account activity.

Privacy change request

For a correction, access request or removal question, tell us the account step concerned and the change you want. We may verify phone ownership before acting, because a privacy request must not expose your account to another person.

DATA PRACTICE

Check Security From Login To Retention

We keep this policy practical by connecting each data purpose to a real account action. Phone verification supports account access, payment references help us trace cashier status, and device session records help…

Account data

We may hold your account details, verified phone status, login events and chosen account settings. These records help us provide access and answer account questions; they are not treated as a reason to collect unrelated personal details.

Cookies

Cookies and similar browser tools can remember a session, keep account pages working and help us understand basic page activity. You can manage browser cookie settings, although changing them may affect login continuity or the path from login to the lobby.

Payment records

A cashier action can create a reference tied to DANA, OVO, GoPay, QRIS, bank transfer or virtual account status. We use those records to match a request, answer receipt questions and check whether the account step was completed.

Account security

Phone verification is an account step before access, and device session details can help us identify a login that needs checking. Never send us your password or wallet PIN; support can work from the account reference and verified contact path.

Retention period

We retain each data type for the period needed for its stated purpose, account support, security checks or legal duties. When that period ends, we remove, anonymise or restrict the record according to the applicable requirement.

Request changes

You can ask us to access, correct or explain data connected with your account through the support route. We may request phone verification and a precise account reference so a change reaches the correct record.

Ask About Privacy Policy And Your Data

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording direct so you can understand how garuda404 handles your data from phone verification through wallet status checks.

The garuda404 Privacy Policy covers account details, phone verification, device sessions, cookies, cashier records, support requests, retention and your rights to ask for access or correction. It applies when you use the site from Indonesia, where access depends on local law.

We use phone verification to connect account access with the correct person and reduce mistaken or unauthorised access. It can also help us confirm a privacy request before we disclose, correct or remove data from the relevant account record.

Yes. The Privacy Policy includes payment references and status records connected with DANA, OVO, GoPay and QRIS. Bank transfer and virtual account requests can create separate reference fields, which we use to match the cashier action and answer receipt questions.

We may use cookies or similar browser storage to keep your session active, support account pages and understand basic page activity. You can adjust cookie controls in your browser, but some changes may interrupt the login path or require another session.

Open the support route connected to your account and ask for a data access request. State the account step involved and use the verified contact path. We may confirm phone ownership before providing account data so it reaches the right person.

Yes. Send a correction request through the account-linked support path and identify the record or account step that appears wrong. We may ask for phone verification, then assess the request against security needs, account records and applicable legal duties.

We keep payment references and status records for as long as needed for the stated payment purpose, account support, security checks or legal duties. The exact period can differ by record type, including DANA, QRIS, bank transfer and virtual account data.

Related Pages

garuda404 Indonesia About Us Access guide garuda404 Casino Account information