Reference

Open your aroma4d Privacy Policy first

Our aroma4d Privacy Policy explains how we handle your account details, phone verification, wallet records and device access before you enter the lobby.

Account dataWallet recordsCookie choicesPolicy requests
Explore Our Lobby Read FAQ
aroma4d Open your aroma4d Privacy Policy first
CONTACT PATHS

Switch to support when privacy questions stall

A direct account route keeps a privacy question separate from a wallet-status issue. From the account area, use the available support contact path and include the email or phone detail linked to your account, the request you are making and any relevant date. We use those details to locate the right record without asking you to repeat unrelated payment data.

Team online

Account access

If you cannot open the Privacy Policy after phone verification, contact us through the account support path and identify the email or phone detail on your account. We can help locate the policy page without requesting your DANA, OVO or GoPay passcode.

Wallet record

For a privacy question about QRIS, bank transfer or virtual account records, tell us the transaction date and wallet type rather than sending a secret code. We use the smallest useful reference to check the record and explain its handling.

Data request

To ask for access, correction or deletion where local law permits, send the request through our listed account contact route. Include the account detail needed to identify you and describe the requested change clearly so we can respond to the right record.

DATA PRACTICE

Browse how aroma4d handles your data

We keep this policy practical: each account step creates a clear reason for the data involved.

Collection

We collect details you provide during account opening, including contact information and phone verification data. We may also record login, device and browser signals needed to connect a request with your account and investigate unusual access.

Cookies

Cookies can remember your page choices and help keep an account session connected while you move from login to the lobby. Your browser settings control some cookie behaviour, and changing them may affect how the Privacy Policy page loads.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create payment references linked to an account record. We use those references for status checks and account protection, not as a reason to request your wallet password.

Account security

Phone verification is an account step before access, while device and login signals can help us identify an unfamiliar session. Keep your phone detail and sign-in credentials private; our support route will not ask for a wallet passcode.

Retention

We retain account, support and payment references for the period needed to provide the requested service, protect records and meet applicable obligations. If you ask how long a specific record is kept, contact us with its account context.

Policy changes

When we change this Privacy Policy, we update this page so you can check the current wording before opening an account or submitting a request. For a correction or removal request where local law permits, use the account contact path.

Check Privacy Policy answers before joining

These Privacy Policy answers focus on the account decisions you make before opening access from Indonesia. They explain what happens around phone verification, mobile browsing, local wallet references, cookies, retention and contact requests, so you can decide what to submit and where to ask for clarification.

The aroma4d Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. Those references can relate to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when connected with your account activity.

Phone verification helps connect account access and privacy requests to the correct account. It also helps us investigate an unfamiliar login. Keep your verification details private, and contact support through the account route if a verification step does not match your details.

Yes. The Privacy Policy applies when you read the page or sign in through a mobile browser, including the path from login to the lobby. Cookies and device signals may behave differently when browser settings change, but the policy still governs the data handling.

Where local law permits, you can ask what account, support, cookie or payment-reference data we hold about you. Send the request through the listed account contact path and include the identifying detail needed to locate your record without sharing a wallet password.

Use the account support route and state which detail is incorrect, such as a contact record or phone-verification detail. Add the account identifier needed for matching. We may need to confirm the request before changing the record, where local law permits.

Retention depends on the type of record and the reason it was created. Account, support and payment references may be kept for service, security and applicable obligations. Ask through the account contact path for the period connected with a specific record.

Yes. You can ask how a DANA or QRIS reference connected with your account is handled, and the same applies to OVO, GoPay, bank transfer or virtual account records. Share the date and reference context, never a wallet password or private access code.

Related Pages

aroma4d Indonesia Badminton Open Bet Makassar Lucky Slots aroma4d Casino FAQ