Reference

alpha55 Privacy Policy For Your Account

alpha55 Privacy Policy explains what we collect when you open an account, sign in from a phone, contact support or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesContact requests
alpha55 alpha55 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Policy Help Near Your Account

A clear contact route matters when you want to understand or change personal data held with your account. We keep policy questions separate from game or wallet requests so your message can be matched to the right record. Use the account help route when you need a copy of your data, a correction, clarification about a device event, or help identifying a payment reference. Include the phone number linked to your account and the relevant date, but never send a password or wallet PIN.

Team online

Account data request

Ask through account help for the personal data linked to your profile. We may check the phone verification step before responding, so the request does not expose account details to another person.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the payment date and visible reference. We use those details to locate the record without asking you to share a wallet password.

Policy change request

If a name, phone detail or contact preference needs correction, tell us which field is inaccurate and why. We may request an account check before changing information that affects sign-in or payment matching.

DATA PRACTICES

How alpha55 Handles Privacy Details

We handle Privacy Policy questions through the same account controls used for sign-in and wallet status, giving each request a practical route.

Account collection

When you create an account, we collect the details needed for the account path and phone verification. Keeping those fields accurate helps us connect your requests, sign-in events and wallet references to the correct account.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us identify the payment event you ask about. Bank transfer and virtual account records may also be used to confirm status without storing your wallet password.

Device signals

We may record device type, browser details and sign-in time to protect account access. On a phone, these signals help us distinguish a normal return to the lobby from an unusual access attempt.

Cookies and settings

Necessary cookies can keep a session working and remember selected settings. You can manage browser cookie controls, although disabling required cookies may affect sign-in, policy access or the route from your account to the lobby.

Retention controls

We keep account, payment and support records only for operational, dispute or legal needs that apply to the relevant record. When retention ends, we delete, anonymise or restrict the data according to its use.

Your request

You can ask about access, correction, deletion, restriction or a copy of your personal data through account help. Include enough account context for us to locate the record, and we may verify your phone before releasing details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you share personal details with alpha55. They explain what happens during phone verification, how wallet references are used, why device signals appear in account records and how to ask for a correction or copy. If your situation is unusual, use account help and describe the specific record or date you want us to check.

The alpha55 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, disclosures, your requests and access conditions.

Phone verification helps us connect account access with the person completing the account step. We use the result to protect sign-in, respond to data requests and investigate unusual activity. It is not a request for your wallet PIN or account password.

Yes. The Privacy Policy covers payment references and status details connected with QRIS, DANA, OVO and GoPay, as well as bank transfer and virtual account records. We use these references to match a transaction question and do not need your wallet password.

Use the account help route and ask for the personal data connected with your account. Add your linked phone number and the relevant request details, but do not include a password or PIN. We may verify account ownership before sending information.

You can request a correction through account help by naming the field that is wrong and giving the accurate replacement. We may check your phone verification first, especially when the change affects sign-in, payment matching or another account-security control.

We retain each category only while it supports account operation, payment matching, support handling, dispute checks or a requirement that applies to the record. When the reason ends, we delete, anonymise or restrict the data according to its purpose.

The Privacy Policy describes our handling of data for supported access, but eligibility depends on local law. Our services are provided where local law permits. If you are unsure whether access is available from your location, contact account help before opening an account.