Reference

Privacy Policy For Your alba slot Account

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

Account dataWallet recordsCookie choicesRequest changes
alba slot Privacy Policy For Your alba slot Account
CONTACT THE POLICY TEAM

Get Help With A Privacy Request

A clear contact path helps when your account record or wallet reference needs attention. Send a request through the support route connected to your account and include the registered phone number, the…

Account request Use the account support path to ask which personal details we hold, why a sign-in record appears, or whether a stored phone detail needs correction. We may ask for an account step that confirms you are requesting access to your own alba slot record.
Wallet reference For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference and date rather than a wallet password or full login secret. We compare the reference with our transaction record and reply with the relevant handling result.
Cookie choice If a cookie setting behaves differently on your phone and desktop, tell us the device path and browser step where it happens. We can explain which cookie supports account access and which preference can be changed without exposing your account.
DATA HANDLING CHECK

Six Privacy Controls Inside alba slot

We handle Privacy Policy requests through practical account checks rather than broad promises. A phone verification step helps connect a request to the right account, while device and session records help us…

Account records

We may hold your registered phone number, account identifiers, verification results and sign-in history. These details let us connect a Privacy Policy request to the correct account and reduce the chance of changing another person’s record.

Device signals

A phone or desktop sign-in can create device and session signals such as browser type, time and access pattern. We use them to identify unusual account activity and to assess a security request without reading private content on your device.

Cookie controls

Cookies can keep your account session active, remember a selected setting and help us understand whether a page step loads correctly. Your browser controls can remove or restrict them, although some account access steps may then need to be repeated.

Payment matching

DANA, OVO, GoPay and QRIS may return a payment reference, status and time. We use that limited transaction context to match your account and investigate a receipt question, not to request your wallet PIN or password.

Retention timing

We keep account, security and payment records for as long as needed for account operation, dispute handling and legal duties. When a record no longer serves those purposes, we remove it or separate it from direct account identifiers.

Change requests

Ask us to access, correct or clarify your personal details through the account support path. Include your registered phone number and the requested change; we may complete a phone verification step before releasing or editing a record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record is checked. They explain what alba slot may collect, how a request is verified and what happens when you use a phone, desktop or local payment rail. If your case is not covered, use the account support path and include only the details needed to locate your record.

It covers account details, phone verification, sign-in and device records, cookies, payment references and privacy requests. It explains how we use those details for account access, security, payment matching and legal needs. Service access depends on local law, including for account creation and continued use.

No. Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS password through support. We may receive a reference, status and time from the payment flow so we can match a receipt to your account and investigate a transaction question.

We may collect your registered phone number, account identifiers, verification results, sign-in times, device signals, cookie settings and payment references. We use each category for a stated account, security, payment or legal purpose, rather than asking for unrelated details during a Privacy Policy request.

Send the request through the account support path with your registered phone number, the detail you want corrected and a short reason. We may ask you to complete phone verification before changing the record. This process applies where local law permits and protects the account from unauthorised edits.

We retain account, security and payment records while they are needed for account operation, dispute handling or legal duties. After that need ends, we remove the record or separate it from direct account identifiers. A support request can ask which retention reason applies to a specific record.

Yes. Your phone browser can restrict or remove cookies through its privacy settings. Our Privacy Policy explains that some cookies keep a session active or preserve a selected setting. If you remove them, you may need to repeat the login or phone verification step.

Use the support route connected to your account and describe whether the request concerns account data, a device sign-in, a cookie choice or a DANA, OVO, GoPay or QRIS reference. Include the relevant date and registered phone number, but never send a wallet PIN or account password.