Reference

alfamabet Privacy Policy for Your Account

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

Clear data purposesWallet record handlingAccount access controlsCookie choices
alfamabet alfamabet Privacy Policy for Your Account
HELP WITH PRIVACY

Get Policy Help Near Account Access

A direct account route keeps Privacy Policy questions separate from general lobby requests. Sign in first when you can, then use the account help path to ask about a stored detail, a wallet reference, or a correction. If sign-in stalls, include the email or phone identifier linked to the account without sharing a password or wallet PIN.

Team online

Account help

Use the account help path for Privacy Policy questions about your profile, verification step, sign-in record, or a correction request. We may ask for account details to confirm ownership.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the receipt reference through account help. Keep wallet passwords and security codes out of every message.

Access trouble

When your phone cannot reach the account page, describe the device path and last successful sign-in. We use that context to separate a privacy request from an access issue.

DATA CONTROL

How We Handle Your Privacy Choices

We treat account data as something you should be able to question and manage. The Privacy Policy sets out our approach to contact details, verification records, wallet references, device signals and cookies.

Account details

We use the contact details you submit to create and protect your account, respond to requests, and connect you with the correct record. Tell us if a phone number or email needs correction.

Verification records

A clear phone verification step may be required before account access. We use the result to protect the account and investigate access questions, not to request your private wallet code.

Wallet references

DANA, OVO, GoPay and QRIS references help us match a payment status to your account. Bank transfer and virtual account references may also remain in transaction records for reconciliation.

Device signals

When you sign in on mobile or desktop, we may record technical signals such as browser or device context. These checks help identify unusual access without reading unrelated files on your device.

Cookies

Cookies can remember sign-in choices, support page operation, and help us understand which policy page was opened. You can manage cookies through your browser settings, although some account steps may change.

Retention requests

We keep records only for the period needed for the stated purpose or applicable obligations. Ask through account help which category applies, and request correction or deletion where local law permits.

Privacy Policy Answers Before You Open

These Privacy Policy answers cover the questions we expect before an Indonesian account is opened or used. They explain the practical route for checking data, changing details, understanding cookies, and asking about wallet records. If your situation is unusual, use the account help path and describe the specific record or access event.

You can read the Privacy Policy at alfamabet.xyz/privacy-policy/. Keep this page available while creating an account so you can check data purposes, cookies, retention, rights and the account help route.

It covers contact details, phone verification results, account activity, device or browser signals, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Our Privacy Policy does not require you to send a wallet password or PIN through account help. Payment references and status details may be recorded, while private wallet security codes should remain with you.

Sign in and use the account help path, then name the detail that needs correction, such as a contact number or email. We may check account ownership before changing the record.

Yes. The Privacy Policy explains how to ask about stored account, device, cookie or payment-reference data. Send the request through account help, and we will assess it where local law permits.

When you sign in from a phone or desktop, technical context may be recorded to protect account access and spot unusual activity. We do not use that process to inspect unrelated device files.

Use account help and identify the data category, such as a profile detail, cookie record or payment reference. We explain the applicable retention position and assess deletion requests where local law permits.