Reference

gurita4d Privacy Policy for Your Account

Our Privacy Policy explains how gurita4d handles the details you provide before account access, including phone verification, device signals and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet detailsDevice choicesSupport requests
gurita4d gurita4d Privacy Policy for Your Account
CONTACT DATA CARE

Three Ways to Ask About Privacy

A clear contact path matters when you want to ask what we hold or why we need it. Use the support route connected to your account access for a privacy request, and include the phone number or account reference you can verify. If your question follows a DANA or QRIS status check, we can separate payment references from the rest of your account record.

Team online

Account request

Ask through the account support channel when you want a copy, correction or explanation of data linked to your phone verification. We may confirm account ownership before discussing personal details.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, send the transaction reference rather than a wallet password. This helps us trace the relevant record while limiting sensitive credentials in support messages.

Device access

If a mobile browser remembers an old session, contact support with the device path and approximate login time. We can direct you through account security checks without requesting private device passwords.

OUR DATA PRACTICE

Six Privacy Details We Keep Clear

We explain our handling process in practical terms so you can decide what to share before opening the lobby.

Account records

We use your account details to create access, confirm phone verification and connect sign-in activity with the correct profile. We do not treat a separate game choice, such as Aviator or Bingo, as a reason to request unrelated personal details.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us identify a cashier event. We limit support requests to the reference needed for checking status and do not ask for wallet passwords.

Cookies

Cookies and similar browser storage can keep an account session, remember selected settings and help detect unusual access. You can clear them through your browser settings, although doing so may require phone verification again.

Security checks

Login time, device type and browser signals help us protect account access. When a request concerns a new phone or a changed session, we may ask you to confirm details already connected to your account.

Retention period

We keep account, payment-reference and support records only while they serve account operation, security, dispute handling or a legal requirement. When a record no longer has a valid purpose, our retention process removes or separates it.

Change requests

You can ask us to correct account details, explain a data use or request deletion where applicable. Send the request through the privacy support path, and we will first confirm that the request belongs to you.

Privacy Policy Answers Before Account Access

These answers focus on the searches you may make before opening a gurita4d account or returning from a mobile device. They cover what we collect, how wallet references are used, how to request a change and what access wording applies in Indonesia. If your case is unusual, send the details through the privacy support path rather than sharing credentials.

It covers account creation, phone verification, login events, device signals, cookies, payment references and support messages. It also explains retention, security checks and the route for requesting access or corrections.

Yes. The Privacy Policy explains that DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may identify a transaction. We do not ask support for wallet passwords or security codes.

Phone verification helps connect an account request to the person seeking access and supports account recovery. We may repeat that check before discussing personal records or changing details linked to your account.

Use the privacy support route connected to your account access and describe the record you want copied or corrected. Include a verifiable account reference, but never include a wallet password or private security code.

Yes. The policy covers mobile browser sessions, cookies, device signals and account activity in the same way as desktop access. Clearing browser storage may end your session and trigger phone verification again.

We retain account, payment-reference and support records only for account operation, security, dispute handling or a legal requirement. The retention process removes or separates records when the valid purpose ends.

Yes. You can contact us with a privacy question regardless of your access status. Eligibility depends on local law, and account access is available where local law permits; we will explain the relevant data path.