Reference

Open with clear privacy terms

Your DANA, OVO, GoPay and QRIS payment records, account login steps, and device sessions sit under this Privacy Policy when you use ectogel.

DANA data scopeOVO receipt recordsGoPay and QRIS logsSession controls
ectogel Open with clear privacy terms
HELP CHANNELS

Check your privacy contact paths

Privacy questions should reach the right team, not get buried in general account chat. We keep support paths separate so you can ask about access logs, payment receipts, cookie choices, or correction requests with enough context for us to act. Include your registered mobile number, approximate date, and payment rail if the request concerns DANA, OVO, GoPay or QRIS.

Team online

Live chat privacy request

Use live chat from 09:00 to 23:00 WIB when you need a same-day privacy check. We may ask you to confirm your registered mobile number before discussing account, session or wallet data.

Email data request

Send longer privacy requests by email when you need a copy, correction or deletion assessment. Add the account username, date range and payment rail so we can route the case without exposing extra data.

Account security route

If you see a login you do not recognise, open Profile > Security > Active Sessions and contact us. We can help you close sessions and check recent device signals.

DATA HANDLING

Manage your account data settings

We run the Privacy Policy through the same account flow you see in the lobby. That means the policy connects directly to registration, wallet checks, login history, cookie…

Account registration data

When you join, we collect your username, mobile number, password hash and verification status.

Payment rail records

DANA, OVO, GoPay and QRIS activity is recorded with timestamps, reference numbers and status labels.

Cookie and device signals

Cookies help keep your session active, remember basic preferences and detect repeated failed access attempts.

Game session logs

When you move from Speed Baccarat to Aviator or Royal Fishing, we may record session time, page activity and device…

Retention and deletion

We keep data only for account operation, dispute handling, security checks and legal needs.

Correction requests

If your mobile number, name match or payment detail is wrong, contact support with proof from the relevant rail.

Ask clear Privacy Policy questions

These answers cover the privacy topics you are most likely to search before opening or using an account. We focus on what data we collect, how payment details are handled, how long records stay with us, and how you can contact our team for changes. If your case involves access, eligibility or account closure, the result may depend on local law.

We collect your username, registered mobile number, password hash, verification status, device signals and basic account activity. If you use the wallet, we also record payment rail details and timestamps needed for account checks.

We store transaction context such as rail name, reference code, amount status, timing and account name match where needed. We do not ask for your wallet password, PIN or private app login details.

Contact live chat from 09:00 to 23:00 WIB or send email with your username, registered mobile number and the field you want corrected. We verify ownership before changing personal or payment-linked data.

Device and session signals help us protect your account from unusual access, repeated failed logins and wallet misuse. You can see active access under Profile > Security > Active Sessions and ask us to close sessions.

We keep account, payment and support records for the time needed to run the account, handle disputes, meet legal duties and protect security. Some records may remain after closure when local rules require it.

Yes, you can request deletion through support. We check your identity, account status and any pending wallet matters first, then tell you what can be removed and what must remain where local law permits.

Only trained support and account-security staff handle privacy requests. We limit access to the data needed for the case, such as login history, wallet references, support messages or correction documents.