Reference

helompo Privacy Policy For Your Account

The helompo Privacy Policy explains what we collect when you open an account, browse Lucky Neko or use DANA and QRIS, why we use each detail, and how…

Clear data purposesWallet records explainedCookie choicesContact steps
helompo helompo Privacy Policy For Your Account
CONTACT YOUR WAY

Get Help With Privacy Questions

A clear contact route helps when you want to check a record, question a cookie or understand a wallet reference. Our support path is tied to your account details, so include the email or phone number used during registration and the relevant cashier reference. We can then separate an access issue from a Privacy Policy request without asking you to send a wallet password.

Team online

Account help route

Open the account help path beside the cashier area and describe your Privacy Policy question. Add the payment reference from DANA, OVO, GoPay or QRIS when your request concerns a transaction record.

Receipt and status check

Keep your payment receipt and status screen available when asking about stored transaction data. We use the reference to locate the relevant record without requesting your wallet PIN or full banking credentials.

Access clarification

If account access differs by location, tell us the country and device path you used. We will explain the applicable Privacy Policy route where local law permits, without asking you to bypass a local restriction.

DATA HANDLING

Six Practical Privacy Controls

We handle privacy through practical account steps rather than vague promises. Registration, phone verification, mobile browsing and cashier activity each create different records, so we describe them separately below.

Account records

When you open an account, we may store the contact details and phone verification result needed to connect you with your account. Check those details before entering the Live Dealer Lobby or the cashier path.

Device signals

A mobile or desktop visit can create technical signals such as browser type, session timing and security events. We use them to recognise unusual access and keep your account path connected to the right device.

Cookies

Cookies help remember your session and policy choices across pages. You can review cookie controls in your browser, although blocking necessary cookies may interrupt login, phone verification or the page showing your account status.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include amount, time, status and reference details. We do not need your wallet PIN to match a receipt with your account.

Retention period

We retain account, support and transaction records only for operational, dispute, security or legal needs described in this policy. When a record is no longer needed, our process removes or de-identifies it.

Change request

To request access, correction or deletion of eligible personal details, contact support from the email or phone linked to your account. We may verify ownership before changing records or disclosing account data.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or connecting a local wallet. If your situation is not covered, use the account help route with a specific record, device path or payment reference so we can respond to the right issue.

It explains the account, contact, phone verification, device and transaction details we may collect, why each record is used, how long it may remain, and how you can request access or correction.

Yes. The Privacy Policy covers transaction references such as payment time, status and receipt identifiers from DANA, QRIS, OVO, GoPay, bank transfer or virtual account use.

You can request a correction through the account help route using the email or phone linked to your account. We may verify account ownership before changing contact or verification records.

Cookies can keep your session, consent choice and account path connected while you move between pages on a mobile browser. Browser controls can block them, but login or verification may then stop working.

We keep account, support and payment records for operational, dispute, security or legal needs described in the Privacy Policy. After that need ends, records are removed or de-identified through our retention process.

Contact support from the email or phone connected to your account and identify the record you want to access. Include a receipt reference when relevant, but never send a wallet PIN or full banking password.

The policy is available for you to read, while account processing and eligibility depend on local law. We apply the relevant route where local law permits and can clarify location-specific questions through support.