Reference

Privacy Policy For Your amavi5d Account

The amavi5d Privacy Policy shows what we collect, why we use it, and how you can ask about your account data before opening access.

Clear data purposesDANA and QRIS contextMobile browser accessWhere local law permits

Explore Our Lobby Read FAQ

How This Policy Covers Wallet Data

amavi5d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide when creating an account, including your phone number, verification response and chosen account credentials. We may also record device type, browser signals, login time, session activity and support messages so we can protect access and respond to account questions.

1
For payments, we handle references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity; we use those references to match status, receipts and account ownership rather than requesting unnecessary wallet secrets. We retain records for the period needed for security, account servicing and
2
legal duties, then remove or separate them when that purpose ends. Access to amavi5d and any data request depends on local law. The policy is available through the account area, and we update its date when our handling changes.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Data

A clear contact path helps when you need a copy, correction or explanation under our Privacy Policy. Start from the support route linked in your account area and include the phone number connected with your profile, without sending a wallet password or one-time code. If a payment receipt or status needs checking, mention the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so we can locate the relevant record.

Team online

Account data request

Use the account support route to ask what personal details we hold, why they are used, or which records are connected with your phone verification. We may ask for an account check before discussing details so another person cannot receive your data.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference through support. Bank transfer and virtual account queries can follow the same path, allowing us to compare the payment status with the correct account record.

Access and correction

If your name, phone detail or account record needs correction, tell us which field is wrong and what should change. We review the request against account ownership and apply the response where local law permits.

DATA PRACTICE

Data Choices Across The Mobile Path

We keep this policy practical by linking each data use to an account action you can recognise.

Account security

Phone verification helps us connect a sign-in with the right account before account details are discussed. We also use login and device signals to identify unusual access, and we will not ask you to share a wallet password or one-time code in support.

Cookies and browser data

Cookies and similar browser records help keep a mobile session connected, remember required settings and show the correct account state. You can manage browser permissions on your device, although removing necessary cookies may interrupt sign-in or cashier status display.

Payment references

When you use DANA, OVO, GoPay or QRIS, we may receive a reference, amount, status and timing needed to match the account record. Bank transfer and virtual account handling follows the same purpose, without storing your wallet login secret.

Session activity

We record selected account and lobby events, such as sign-in time, device type and a session connected with Speed Blackjack Live or Limbo Quick Arena. These records help investigate access questions and maintain a clear account history.

Retention decisions

We keep personal records only while they support account security, payment matching, support handling or a legal duty. When a purpose ends, we remove, anonymise or restrict the record according to the applicable retention need.

Policy changes

If our handling changes, we update the Privacy Policy date and publish the revised wording in the policy area. Checking this page before using your account helps you see the current purposes, choices and contact route.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from people considering amavi5d in Indonesia. They explain the practical route for checking records, managing browser choices and asking for changes, while access remains where local law permits.

It covers account details, phone verification, device and browser signals, session records, support messages and payment references. The policy explains why we use each category, how we protect access, how long records may remain, and how you can contact us about your data.

Yes. We explain that DANA, OVO, GoPay and QRIS activity may create a reference, status, amount and timing record for account matching. Bank transfer and virtual account records follow the same purpose; we do not need your wallet password to check a receipt.

Phone verification helps connect account access with the person who created the profile and reduces mistaken disclosure through support. It can also help us investigate a sign-in or payment question. We use the phone detail for stated account, security and service purposes.

You can use the account support route to identify the incorrect field and provide the replacement detail. We may verify account ownership before making a change. We respond to correction requests according to the Privacy Policy and where local law permits.

Cookies and similar browser records can keep your mobile sign-in connected, preserve necessary settings and display the right wallet status. Your browser lets you manage these permissions, but blocking required cookies may affect account access or cashier status visibility.

Retention depends on the reason for holding a record, such as account security, payment matching, support handling or a legal duty. When that reason ends, we remove, anonymise or restrict the record in line with the applicable Privacy Policy requirement.

Open the support route from your account area and ask for a data copy, purpose explanation, correction or removal. Include the phone detail connected with your profile, but never send a wallet password or one-time code. We handle the request where local law permits.

Privacy Policy For Your amavi5d Account

Where To Ask About Your Data

Account data request

Wallet record question

Access and correction

Data Choices Across The Mobile Path

Account security

Cookies and browser data

Payment references

Session activity

Retention decisions

Policy changes

Privacy Policy Questions For Indonesia

01 What does the amavi5d Privacy Policy cover?

02 Does the Privacy Policy explain DANA and QRIS data?

03 Why does amavi5d need phone verification?

04 Can I ask amavi5d to correct my personal data?

05 How do cookies affect this Privacy Policy?

06 How long does amavi5d keep account records?

07 Where can I request access to my Privacy Policy data?

Related Pages