Reference

alba55 Privacy Policy for Your Account

Your alba55 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and check wallet status.

Account dataWallet recordsDevice cookiesRequest path
alba55 alba55 Privacy Policy for Your Account
PRIVACY HELP ROUTE

Three Ways to Ask About Your Data

A clear contact path matters when a login, verification record or wallet reference does not look right.

Account support Use the support route beside your account area when you need to ask about phone verification, login records or the personal details attached to your alba55 account. Include the issue and your account identifier, but do not send a wallet PIN or private payment credential.
Wallet clarification If a DANA, OVO, GoPay or QRIS reference appears in your account history, ask through the cashier support path and name the transaction reference. We can explain the record held by us without asking you to reveal the password or security code for your external wallet.
Privacy request For a copy, correction or eligible deletion request, use the privacy contact route displayed with this policy. Tell us which account detail or device record you mean; we may first confirm account ownership before changing or disclosing personal data.
HANDLING IN PRACTICE

How We Handle Policy Requests

We apply the Privacy Policy to the account path you actually use, from phone verification through a mobile browser and wallet status checks.

Data use

We use account details, verification results and service records for the purposes described in this Privacy Policy. A payment reference helps us match a wallet event to your account; it does not give us access to your DANA, OVO, GoPay or bank credentials.

Cookies

Cookies and similar browser signals can remember a session, support account security and help us understand whether a page loads correctly on your device. You can manage browser cookie settings, though changing them may affect login continuity or the way policy choices are saved.

Account security

Phone verification is part of the account access path, and login events may be checked against device or browser signals. Keep your password and wallet security codes private. If a login looks unfamiliar, use the account support route before sharing any further personal detail.

Retention

We retain account, support and payment-reference records only for the purposes and periods described in the Privacy Policy, including security, dispute handling and legal duties. When a retention period ends, records are deleted or separated from direct account identification where applicable.

Who to contact

The privacy contact route is the right place for questions about data held by alba55, including a phone record, cookie choice, device signal or wallet reference. The support team may ask for account verification before confirming anything connected to your personal account.

Changing your data

You can request correction when your account detail is inaccurate or outdated. State the existing entry and the change you seek, then complete the ownership check we provide. Some records may need to remain when security, dispute or legal obligations require continued storage.

Privacy Policy Questions for alba55

These Privacy Policy answers address the account questions you are most likely to have before opening or continuing an alba55 account in Indonesia. They explain the practical handling of phone verification, cookies, device signals and local wallet references without asking you to guess which support path applies. If your question concerns a specific record, use the privacy contact route and mention the relevant account step.

The alba55 Privacy Policy explains how we handle contact details, phone verification results, login events, device signals, cookies, support messages and payment references. We use each category for stated account, security, service or legal purposes, and we do not treat a wallet reference as your wallet password.

Phone verification helps us connect the person completing the account step with the correct account and reduce mistaken or unauthorised access. The related result may be retained for the purposes described in the Privacy Policy. Whether access is available depends on local law.

Yes. The Privacy Policy covers payment references and status details that reach our account records from DANA, OVO, GoPay or QRIS. We use those references to match an account event or investigate a status question; we do not request your external wallet PIN or security code.

You can request a correction through the privacy contact route shown with this policy. Describe the inaccurate entry, such as a contact detail or account record, and complete the ownership check we request. We will assess the request against security, dispute and legal record duties.

Cookies can keep a session connected, save a policy choice and help us detect technical problems on your browser. Your device settings can restrict cookies, but login continuity or saved choices may change. The Privacy Policy explains the purposes linked to these browser records.

Retention depends on the purpose of the record and the period described in the Privacy Policy. Account, support and payment-reference data may remain for security, dispute handling or legal duties. When no stated purpose requires it, we delete or separate the record where applicable.

Open the account support area and use the privacy contact route displayed with this Privacy Policy. Name the request, such as access, correction or eligible deletion, and identify the relevant account record. We may confirm ownership before discussing or changing personal data.