Reference

area138 Privacy Policy For Your Account

The area138 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support…

Account dataCookie choicesWallet contextAccess requests
Browse Our Lobby Read FAQ
area138 area138 Privacy Policy For Your Account
CONTACT PATHS

Privacy Policy Help From The Account Route

A clear contact path matters when a privacy question appears beside a login or wallet status issue.

Account privacy request Use the support contact shown inside your area138 account and state that your message concerns the Privacy Policy. Include your registered phone number only when requested, so we can locate the account without asking you to send a password or wallet PIN.
Wallet reference check If your question follows a DANA, OVO, GoPay or QRIS action, share the transaction reference and approximate time rather than a full wallet login. We can use that limited context to check which account record or payment status the Privacy Policy question concerns.
Access and correction For a copy, correction or removal request, tell us which account detail is affected and how we can confirm ownership. We may ask for the phone verification step connected with your account before changing personal data or discussing a stored record.
DATA PRACTICES

Cookies, Security And Your Privacy Choices

We keep this Privacy Policy practical by connecting each data practice to a real account action.

Data we receive

We may receive your account contact details, phone verification result, sign-in time, device or browser signals, support messages and transaction references. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, the useful record is generally status or reference data linked to the account action.

Cookie handling

Cookies can keep a session active, remember selected settings and help identify unusual access patterns. If you clear browser storage, you may need to sign in again and repeat the phone verification step. Cookie changes affect browser behaviour, not the accuracy of a completed payment reference.

Account security

Keep your password, verification code and wallet PIN private, including when you use a shared phone. We do not ask you to place those secrets in a support message. If a desktop and mobile session look unusual together, we may ask you to confirm account ownership before discussing personal data.

Record retention

We keep personal and transaction-related records for the period needed to provide the account service, investigate security events, resolve a support request or meet a legal need. When that purpose ends, we remove, anonymise or restrict the record where our systems and legal duties allow.

Who can request changes

The account holder can ask us to access, correct or clarify personal data connected with the account. A request from another person may require evidence of authority. This protects the account record when a phone number, wallet reference or device path is shared by more than one person.

How we respond

Send the request through the account support route with a clear subject such as data copy, correction, cookie question or deletion request. We will confirm what we need to check, explain any limit created by local law and respond through the contact path connected with your account.

Privacy Policy Answers For area138

These Privacy Policy answers address the searches we hear around account records, phone verification, cookies and Indonesian wallet references. We keep each answer tied to an action you can recognise, whether you sign in from a mobile browser in Yogyakarta, check QRIS status or ask support to correct an account detail. If your situation is not listed, use the account contact route and describe the record involved.

It covers data connected with your account, including contact details, phone verification, sign-in activity, device or browser signals, support messages, cookies and payment references. It explains why we use those details for access, security, account service and legal needs, with eligibility depending on local law.

When you use DANA, OVO, GoPay or QRIS, we may receive a status, reference or account-matching detail needed to identify the action. We do not need your wallet password or PIN for that purpose. Keep those secrets outside support messages and report only the reference requested.

Yes. Send an access request through the account support route and identify the account detail or record you want us to locate. We may confirm ownership through the phone verification step before sharing data, and we will explain any restriction that depends on local law.

Use the account support contact and name the detail that needs correction, such as a phone number or contact field. Do not send your password or wallet PIN. We may ask for account ownership confirmation, then update the record where the request is valid and technically possible.

Yes. Cookies and browser storage can support sign-in, remember selected settings and help us review unusual sessions on your phone or desktop. Clearing them can sign you out and require phone verification again. You can ask support how a cookie choice affects your specific browser path.

We retain records for the operational, security, support or legal purpose that requires them. A DANA, QRIS, bank transfer or virtual account reference may remain while a status question or legal duty is open. Afterward, we remove, anonymise or restrict it where permitted.

Start with the support route shown inside your account and state whether you need access, correction, deletion or a cookie explanation. Include only the details needed to identify your record. We will confirm the next step and explain if the request is limited where local law permits.

Related Pages

area138 Indonesia FAQ area138 Casino semobola About Us