Reference

Privacy Policy For Your gamemodfree Account

Clear control over your account, device and wallet details starts with the gamemodfree Privacy Policy.

Account dataWallet recordsCookie choicesPhone verification
gamemodfree Privacy Policy For Your gamemodfree Account
CONTACT ROUTES

Get Privacy Help Beside Your Login

A clear support route helps you ask about personal data without searching through the lobby. Use the support link connected to your account area and include the email or phone detail attached to your profile, but do not send a wallet password or one-time code. We can help you identify a stored payment reference, explain a cookie choice, or route a request to correct account data. If access is unavailable, describe the device path you used, such as mobile browser or desktop browser, so we can locate the relevant session.

Team online

Account data request

Ask us to confirm which account details we hold by using the support route near login. Include your registered contact detail so we can match the request, then complete any identity check needed before we disclose or change personal data.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference and payment rail through support. We will check the account record without asking for your wallet password, PIN or one-time verification code.

Cookie or device help

Tell us whether you opened gamemodfree through a mobile browser or desktop browser when asking about cookies or session data. Our support route can explain the setting involved and help you understand why a fresh login may be requested.

DATA PRACTICE

What Our Privacy Process Covers

We keep this policy practical by linking each data use to an account action you can recognise.

Data collection

We collect account details when you create or update a profile, plus phone verification results and login events needed for access control. Browsing and device signals may be recorded to maintain a session, detect unusual activity and answer a support question.

Cookie controls

Cookies can remember a session, language choice or security state on the browser you use. You can manage browser cookie settings, although removing required cookies may sign you out or require phone verification when you return.

Account security

We use account checks around login and phone verification to reduce mistaken access. Never share your password, wallet PIN or one-time code with support. If a sign-in looks unusual, contact us through the account route and describe the device used.

Retention choices

We keep account, payment and support records only as needed for account operation, reconciliation, security checks and legal duties. Retention can differ by record type, so ask support which period applies to a specific DANA or bank transfer reference.

Correction requests

If your phone number, email or account detail is wrong, request a correction through support after signing in. We may verify ownership before changing it, helping prevent another person from redirecting account notices or wallet records.

Policy contact

For a Privacy Policy question, send the subject clearly and identify the account contact detail involved. We will use the support route to explain the relevant record, request further proof when needed and respond within the process available under local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to complete before entering the lobby. We cover phone verification, browser cookies, local wallet references, device access and requests to view or change data. If your situation involves a particular transaction or login event, include that detail in your support request. Access and any related request handling remain subject to local law, including the rule that access depends on local law.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use, retain and protect those records for account operation.

No. Our Privacy Policy distinguishes payment references from wallet credentials. We may retain a DANA or QRIS transaction reference to reconcile account activity, but you should never send us a wallet password, PIN or one-time code through support.

Phone verification helps connect account access to the contact detail you supplied and supports security checks when a session looks unusual. We record the verification result and related account event, not a request for your wallet PIN or one-time payment code.

Where local law permits, you can ask what account, device, cookie or payment-reference data we hold and request a correction. Use the support route near login, identify your registered contact detail and complete an ownership check before disclosure or changes.

Cookies can keep a mobile browser session, preference or security state available between visits. If you clear required cookies, the next login may ask for phone verification again. Our Privacy Policy explains this browser behaviour without requiring an installed application.

Retention depends on the record and its purpose. Payment references may remain for reconciliation, support, security checks and legal duties, while account or cookie records can follow different periods. Ask support about a specific OVO, GoPay or bank transfer reference.

Yes. Use the account support route and label your message as a Privacy Policy request. Include the registered email or phone detail, the record type involved and whether you seek access, correction or deletion. We may request identity proof before responding.