Reference

Privacy Policy for Your gacormania Account

gacormania explains how we collect, use and protect the details connected with your account, phone verification and wallet activity.

Account detailsPhone verificationWallet recordsCookie choices
gacormania Privacy Policy for Your gacormania Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when you want to ask about stored details, a phone check or a wallet record.

Account privacy request Use the support link beside your account area to ask what personal details we hold or to request a correction. We will ask for account-matching details before discussing the record, so your request is connected to the right gacormania account.
Wallet record question For a DANA, OVO, GoPay or QRIS record, mention the payment rail, date and visible reference in your support request. We can then compare the account ledger with the transaction status without asking you to share a wallet PIN or one-time code.
Access concern If a phone verification step or mobile session appears unfamiliar, contact support through the account help route near the cashier area. We may pause the discussion until we confirm account ownership, helping keep private account details away from an unverified contact.
DATA PRACTICE

What We Do With Your Records

Privacy decisions are easier to assess when the handling is specific. We separate account access records from ordinary browsing signals, use transaction references to trace payment status, and treat phone verification as…

Account details

We may collect your registration details, phone number and verification result to create and protect your account. These details support the login path and help us distinguish an authorised account holder from an unknown person asking about private records.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we record the reference needed to match the transaction with your account. We do not need your wallet PIN or one-time code for a privacy request.

Cookies and sessions

Cookies and similar session tools can remember an active login, selected settings and security signals on your mobile browser or desktop. Removing them may sign you out or require phone verification again, but it does not erase records already held for account purposes.

Account security

We use phone verification, session checks and account-matching questions when private details are requested. If a login or device looks unusual, we may ask for another account step before sharing data or changing contact details.

Record retention

We keep personal and transaction records only for the period needed for account operation, security checks, dispute handling or a legal requirement. After that period, records are deleted or retained in a form that no longer identifies you where practical.

Change request

To request access, correction or deletion, contact us through the support route and state the action you want. Add your account identifier and relevant reference, then complete any ownership check needed before we assess the request under local law.

Privacy Policy Answers For Indonesia

These answers address the searches we hear most often about the gacormania Privacy Policy. They focus on the account step, wallet references, mobile sessions and the route for requesting changes, so you can decide what to share and how to reach us before using the account.

It covers account details, phone verification, device and browser signals, cookies, support messages and transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It explains why we use each category, how long records may remain and how to contact us.

Phone verification helps connect account access with the person who created the account and helps us respond safely to privacy requests. We may ask for an account-matching step before changing details or discussing a record. Account access depends on local law.

Yes. The Privacy Policy includes references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use the reference, amount status and account link to trace a transaction question, not your wallet PIN or one-time code.

Cookies can keep a mobile-browser or desktop session active, remember selected settings and support security checks between login and the lobby. Clearing cookies may sign you out or trigger phone verification again. Existing account and transaction records are not removed simply by clearing your browser.

Send a request through the support link near your account area and state which detail appears wrong. Include your account identifier and, where relevant, a payment reference. We will confirm account ownership before reviewing the correction under the Privacy Policy and local law.

You can ask us to delete personal details through the privacy support route. We assess the request against account security, payment tracing, dispute handling and legal retention needs. Some records may need to remain for those purposes, while other details can be removed when no longer needed.

Contact us through the account help route near the cashier path and describe the unfamiliar device or session. Do not send a password, wallet PIN or one-time code. We may require phone verification and review session details before discussing the account or changing access information.