Reference

axistogel Privacy Policy Explained Clearly

Our Privacy Policy explains what axistogel collects when you open an account, sign in from a mobile browser, or check a DANA, OVO, GoPay or QRIS wallet status.

Account dataWallet recordsCookie choicesAccess requests
axistogel axistogel Privacy Policy Explained Clearly
CONTACT PATHS

Privacy Help Beside Your Account Flow

A direct support route helps you resolve a privacy question without exposing account details in a public message.

Account help path Use the account help route to ask which personal details are attached to your…
Cashier status question For a DANA, OVO, GoPay or QRIS record, contact support through the cashier path…
Access recovery If mobile login stalls, tell us the device path and account contact used.
HANDLING YOUR DATA

Account Security And Privacy Controls

We keep this policy practical by connecting each privacy control to an account action you can recognise.

Data collection

We may receive your account contact, phone verification result, sign-in details, device path and wallet reference when those records are…

Cookie controls

Cookies can remember session choices and help us understand whether a mobile browser is returning to the same account path.

Account protection

We use account details, verification steps and sign-in signals to reduce unauthorised access.

Retention approach

We retain account, support and payment-status records only for the period needed for account operation, security checks, dispute handling or…

Correction requests

You can ask us to correct an inaccurate phone, contact or account detail through support.

Removal requests

You may ask whether eligible personal data can be removed.

Privacy Policy Questions For axistogel

These Privacy Policy answers focus on the account actions you are most likely to take on axistogel, from opening access on a phone to checking a wallet reference. If your situation is not covered, use the account help path and describe the specific record or request.

It covers account creation, phone verification, sign-in activity, device and browser signals, cookie choices, wallet references, support messages, retention and requests to correct or remove eligible personal data.

Phone verification helps connect an access request to the correct account and helps us identify suspicious sign-in activity. We may ask for verification before changing account details or releasing account-specific data.

Yes. The policy covers payment-status references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps when those records are needed to trace an account or support question.

Use the signed-in account help path and state which detail is inaccurate, such as a phone or contact record. We may verify your account before making a change to protect your access.

You can submit a removal request through support. We assess it under applicable rules; security, payment tracing or legal duties may require some records to remain where local law permits.

Cookies may preserve a session and selected site settings on your mobile browser. You can adjust cookie choices in the browser controls, though disabling some cookies may affect account access.

Yes. Send an access request through the account help path, identify the account contact used, and describe the record you want checked. We may verify ownership before responding.