Reference

gul911 Privacy Policy For Your Account

Our Privacy Policy explains which account, wallet and device details we use when you open gul911 and move from phone verification to the lobby.

Account dataWallet recordsDevice choicesContact routes
gul911 gul911 Privacy Policy For Your Account
CONTACT THE POLICY TEAM

Reach Support When Privacy Questions Stall

A direct support path helps you ask about the Privacy Policy without guessing which account screen to use.

Policy chat Use the signed-in support chat for a question about the Privacy Policy, a data…
Wallet query When DANA, OVO, GoPay or QRIS activity appears unfamiliar, share the transaction reference rather…
Access contact If you cannot reach the account screen, contact us through the route displayed on…
HOW WE HANDLE RECORDS

Browse gul911 Data Handling In Six Steps

Our handling process follows the account journey rather than collecting every possible detail.

Account creation

When you open an account, we use the details submitted in the account form to create your profile and support phone verification. We keep the record connected to your login so a privacy request reaches the correct account.

Wallet records

A DANA, OVO, GoPay or QRIS action can create a reference, amount status and time record. Bank transfer and virtual account activity may also carry a matching reference, allowing us to trace a status without storing your wallet PIN.

Device protection

We may record device, browser and session signals when you sign in from a phone or desktop. These checks help us notice unusual access and protect the account; they do not give us access to unrelated files on your device.

Cookies

Cookies can remember a session, language choice or security state so you do not repeat the same account step on every page. You can manage browser cookie settings, although disabling some cookies may interrupt login or policy access.

Retention period

We retain account, security and transaction records only for the period needed for the purpose described in the Privacy Policy, including legal or dispute needs. When a record is no longer needed, our process addresses deletion or further restriction.

Your request

You can ask us to access, correct or clarify account data through support chat or the listed contact route. We may verify your identity first, then explain what can be changed, what must remain, and why.

Check Common gul911 Privacy Policy Questions

These Privacy Policy answers focus on the searches you may make before opening an account or contacting us about data. We explain the account step, wallet records, cookies, device signals and request routes in practical terms. If your case involves access or eligibility, remember that access depends on local law. For a record tied to your own account, use the support path rather than sending sensitive credentials in an open message.

It covers the account details, phone verification, login events, device signals, cookies, game-session records, wallet references and support messages we handle. It also explains our purposes, retention approach, security steps and how you can request access or correction.

We use your phone number for the account path and phone verification before account access. This helps connect a request to the correct account and supports login protection. We do not ask you to share a verification code in a public support message.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay or QRIS, along with relevant bank transfer or virtual account status. These records help us match an account action and investigate a receipt without requesting your wallet PIN.

Contact us through signed-in support chat or the contact route displayed on our site. State whether you want access, correction or clarification, and include the account email or other requested identifier. We may complete an identity check before handling the request.

We may use cookies for a session, security state or page preference when you open the site on a phone or desktop. Browser controls let you manage them. If you block required cookies, login or Privacy Policy access may not work as expected.

The retention period depends on the purpose of the record, account security needs, legal duties and possible disputes. Our Privacy Policy explains the applicable approach rather than promising one fixed period for every record. We address deletion when the reason for keeping data ends.

You can send a deletion request through the listed support route, and we will assess it against the Privacy Policy and applicable duties. Some security or transaction records may need to remain for a period. Access or eligibility depends on local law.