Reference

Privacy Policy for Your Account

Your helompo account starts with clear privacy handling for sign-up details, wallet activity and device checks.

Account data handlingDANA and OVO contextGoPay and QRIS recordsDevice and cookie checks
helompo Privacy Policy for Your Account
PRIVACY HELP

Contact Us About Your Data

Privacy support is handled through account-aware channels, not public comment threads. When you ask about account data, wallet references or device records, we check that the request comes from you before sharing or changing anything. Keep your registered mobile number and email reachable so we can verify you without exposing payment details in chat.

Team online

Live Chat

Use live chat daily from 09:00 to 23:00 WIB for privacy questions tied to login alerts, cookie choices or wallet checks. We ask for account matching details before discussing DANA, OVO, GoPay or QRIS records.

Email Desk

Send privacy requests to the support email shown inside your account menu. Include your username, registered mobile number and the data topic, but never send full wallet PINs, OTP codes or card-style secrets.

Account Menu

Open Profile, then Privacy Request, when you want to correct contact details or ask for a copy of account records. This path keeps your request linked to the signed-in account.

DATA CARE

Privacy Controls Around Aviator and Wallets

We built the policy around the moments where your data actually appears: sign-up, login, game entry, wallet movement and support contact.

Account Details

We collect the details you enter during sign-up, including username, contact number and email. These records help us identify your account, recover access and handle privacy requests without asking for unrelated personal documents first.

Payment Context

DANA, OVO, GoPay and QRIS references are used to match deposits, withdrawals and balance questions to your account. We record transaction codes, times and status markers, not your private wallet password or OTP.

Device Signals

We read basic device and browser signals when you sign in, such as IP range, screen type and session timing. These checks help us spot unusual access and protect your account from unwanted logins.

Cookies

Cookies remember session state, language preference and lobby movement so the page does not ask you to sign in repeatedly. You can clear them in your browser, though some account features may need a fresh login.

Retention

We keep account and payment records while they are needed for wallet reconciliation, security checks, dispute handling and legal duties. When a record is no longer needed, we delete it or remove direct identity markers.

Change Requests

You can ask us to correct contact details, explain stored records or remove data that we no longer need. We verify the request through your account before making changes to protect you from false requests.

Privacy Questions Before You Join

These answers focus only on how we handle your personal data, wallet references, device signals and privacy requests. If you are deciding whether to open an account, use them to understand what we collect, why we collect it and how to contact us when something needs correcting.

We collect the details you enter, such as username, mobile number, email and login credentials. We also record session timing, device signals and wallet references when you use DANA, OVO, GoPay or QRIS.

We use payment references to match wallet actions to your account, trace failed requests and answer balance questions. We do not ask for wallet PINs or OTP codes, and you should never share them with anyone.

Yes. Open Profile, choose Privacy Request, then tell us which contact detail or account record needs correction. We verify the request through your signed-in account before changing data that affects access or wallet checks.

Cookies keep your session active, remember basic preferences and help us understand whether a login belongs to your usual device. You can clear cookies in your browser, but you may need to sign in again afterward.

We keep records only while they are needed for wallet reconciliation, security monitoring, dispute handling and legal duties. After that period, we delete records or remove details that directly identify you where possible.

Only support and security staff who need the request to do their work can access it. We use account verification, internal access controls and request logs so your data is not handled through public channels.

Yes. Access depends on local law, so we may use location signals and account checks to confirm whether the service can be shown to you. These checks are used for access control and account protection.