Reference

Privacy Policy for Your gamewso55 Account

gamewso55 Privacy Policy explains what we collect when you open an account, use a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsDevice choicesPolicy access
gamewso55 Privacy Policy for Your gamewso55 Account
CONTACT PATHS

Ask About Your Stored Account Data

A direct support request gives you a practical way to ask about this Privacy Policy without sending sensitive wallet credentials. Use the account support route when a phone verification record looks wrong, a QRIS receipt is not matched, or you want to know which details are held for your sign-in. We may ask for account identifiers so we can locate the correct record, while you should never send a wallet PIN or full authentication code.

Team online

Account support

Send a policy question from the account support path and include the email or phone detail connected to your profile. We use that reference to locate your access record, phone verification status and any related request without asking for your DANA, OVO or GoPay security code.

Wallet status check

If a QRIS, bank transfer or virtual account receipt is not matched, share the transaction reference and date through support. We use those limited details to trace status, explain the record held for reconciliation and avoid requesting your wallet password or card credentials.

Policy request

For a copy, correction or clarification about personal data, state the account step involved and the result you want. We may verify ownership through your registered phone or email before discussing records, helping us avoid disclosing account details to the wrong person.

DATA PRACTICES

How We Handle Six Privacy Areas

Our handling process follows the account actions you take rather than treating every detail as permanent.

Account details

We collect details needed to create and maintain your account, such as contact information and phone verification results. These records help us distinguish your profile from another account during sign-in and support, and we use corrections you provide to keep the account path accurate.

Payment references

DANA, OVO, GoPay and QRIS may provide a reference, amount status and processing time for account matching. Bank transfer and virtual account records serve the same narrow purpose. We do not ask you to disclose a wallet PIN, one-time code or private wallet password.

Cookies and sessions

Our browser may store session cookies and preference signals so your account path remains connected while you move between pages. You can clear cookies through your browser settings, although doing so may require another sign-in or phone verification before account access continues.

Device security

We may record browser type, operating system, device signals and security events when you sign in from a phone or desktop. These details help us investigate failed access and unusual sessions. They are used for account protection, not as a request for your device contents.

Retention choices

We retain records while they serve account, security, payment matching or support purposes, then assess whether they are still needed. Ask through account support which category applies to you, why it remains stored and whether correction, restriction or removal can be considered.

Changes and contact

You can ask us to correct contact details, explain a payment reference or clarify a policy section. Include your account identifier and the specific record in question. We may confirm ownership through your registered contact before making changes or sharing account-related details.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we most often expect before access. They explain what you can ask, which payment references may appear, how device information is used and where to send a request. For account-specific help, use the support route rather than placing private credentials in a general message.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be used to match transaction status. Access depends on local law, and you can ask us to explain a relevant record.

Phone verification helps connect an access request with the correct account and reduces mistaken or unauthorised sign-ins. We may use the verification result when you ask about a profile change or payment status. We do not ask you to send your one-time code through support.

Yes. The Privacy Policy covers transaction references, status results and timestamps connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these details for account matching and support checks, not to request your wallet PIN or password.

We may collect browser type, operating system, device signals, session details and security events when you sign in. This helps us investigate failed access or unusual sessions on mobile and desktop. It does not mean we request the contents of your phone, gallery, contacts or private files.

You can ask us to correct an account contact detail, explain a stored payment reference or clarify another record covered by the Privacy Policy. Send the request through account support with the relevant identifier. We may verify ownership through your registered phone or email before changing information.

Retention depends on why a record is needed for account access, security, payment matching or support. We assess whether each category remains necessary rather than treating every detail alike. Ask account support about your specific record, its purpose and whether a deletion or restriction request can be considered.

Use the account support route to ask why access or eligibility is unavailable and how your related data is handled. We apply the wording where local law permits when describing access conditions. Include your account reference, but do not send wallet passwords, PINs or authentication codes.