Reference

Open gojo177 Privacy Policy Before Account Access

gojo177 Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataCookie choicesDevice securityPrivacy requests
gojo177 Open gojo177 Privacy Policy Before Account Access
CONTACT PATHS

Browse Privacy Support From Your Account

A direct support route helps you ask about the Privacy Policy without sending sensitive details through random channels. Use the support chat connected to your account for questions about a data record, cookie setting, payment reference or access event. If you are in Semarang and a wallet status looks unfamiliar, include the date, payment rail and receipt reference rather than your password. We use those details to locate the relevant record while limiting what you need to disclose.

Team online

Policy questions

Use account support chat to ask which data category applies to your sign-in, profile, device or lobby record. We will point you to the relevant Privacy Policy section and tell you what details are needed for a clear response.

Wallet references

For a DANA, OVO, GoPay or QRIS question, send the payment date, rail name and receipt reference through support chat. Do not send a wallet PIN, password or full authentication code when asking us to check a record.

Access concerns

If your account opens on an unfamiliar device, contact us through the signed-in support path as soon as possible. We can review the access event, explain the related data use and help you secure the account without asking for private login secrets.

DATA HANDLING

Explore How Privacy Controls Work

We keep the Privacy Policy practical by tying each data category to an account action you can recognise.

Account records

We use the details you provide during account creation and verification to identify the account, help prevent unauthorised access and respond to account requests. We do not ask you to place passwords or wallet PINs into a support message.

Payment data

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create status, reference and receipt records. These records help us match a payment to the correct account, while wallet credentials remain outside our support request process.

Cookies

Cookies can keep a session open, remember language or device choices and help identify unusual sign-in patterns. You can manage browser cookie settings, but blocking required cookies may affect sign-in continuity and will not erase existing account records.

Device security

We may record device type, browser details, approximate network signals and sign-in time to protect the account. If Esports Valorant or Aviator Quick Arena appears in a session you do not recognise, contact support so the access record can be checked.

Retention periods

We retain data only for the period needed for account operation, security checks, payment matching, dispute handling or legal duties. The period can differ by record type, so a request to close an account may not remove every record immediately.

Your requests

You may ask what account data we hold, request a correction, ask about processing or seek deletion where applicable. Send the request through account support chat; we may verify account ownership before changing or disclosing personal data.

Ask What Privacy Policy Means

These Privacy Policy answers address the account and payment questions Indonesian customers commonly raise before opening an account. Each answer stays focused on personal data, access records, cookies, retention and the support route. If your situation is not covered, use the account contact path and include only the details needed to identify the request.

The gojo177 Privacy Policy covers account details, verification data, sign-in events, device signals, cookies, payment references and lobby activity. It explains why we use each category, how we protect it, how long records may remain and how you can contact us about your data.

We record payment status, receipt references and related account links for DANA, QRIS and other available rails so we can match a transaction, investigate a status issue and handle a dispute. We do not need your wallet PIN or password for that process.

Yes. Send a correction request through the support chat connected to your account and identify the field that appears wrong. We may ask for an account check before making changes, particularly when the request concerns verification details or payment records.

On a phone, cookies and similar tools may keep your session active, remember settings and help detect unusual access. You can change cookie permissions in your mobile browser. Required settings may affect sign-in, while changing them does not by itself erase account or payment records.

Retention depends on the type of record and why it exists. Account, security, payment and dispute records may remain for different periods because we need them for service operation, account protection or legal duties. The Privacy Policy explains this approach without promising instant removal.

Contact account support chat and provide the sign-in date, device type and any session detail you recognise. Do not send your password or authentication code. We can use the access record to explain the event and help you secure the account.

Account access and eligibility depends on local law. The Privacy Policy is available for you to read before submitting personal details, and some data rights or processing steps may vary according to the rules that apply to your location.