Reference

Open with elemen33 Privacy Policy clarity

elemen33 Privacy Policy sets out what we collect when you create an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account detailsDevice activityWallet recordsPrivacy requests
Explore Our Lobby Read FAQ
elemen33 Open with elemen33 Privacy Policy clarity
PRIVACY SUPPORT ROUTE

Reach support about Privacy Policy requests

A clear support path helps when your Privacy Policy question concerns a login, wallet reference or account detail. Start from the support route linked to your account and include the phone number connected to your profile, the date of the event and the payment rail involved. For a QRIS or bank transfer question, attach only the receipt details needed to locate the record. We use the same route for correction, access and deletion requests, while access remains subject to local law.

Team online

Account privacy request

Ask us to locate the personal details attached to your account. Include your account phone number and a short description of the requested Privacy Policy action so we can check the correct profile.

Wallet record check

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, send the payment date, amount reference and wallet name through account support. Please hide passwords, security codes and unrelated wallet activity.

Login data concern

When a device sign-in or phone verification looks wrong, tell us which device path you used and when it happened. We can review the account event without asking you to reveal your sign-in code.

DATA HANDLING PRACTICE

Check elemen33 data handling steps

Privacy Policy choices should be practical, not hidden behind general wording. We separate account details, device events and payment references so a support reply can address the exact record involved.

Account details

We use your phone number and verification responses to create, locate and protect your account. If you ask for a copy or correction under this Privacy Policy, we may request enough account evidence to avoid changing the wrong profile.

Device signals

A mobile browser or desktop session can produce sign-in time, browser type and security event data. We use these signals to identify unusual access and to help explain why a phone verification step appeared.

Cookies

Cookies can keep a sign-in state, remember a page setting and show whether an account step loaded correctly. Browser controls let you remove or restrict them, but the lobby or cashier path may ask you to repeat a step.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave references, timestamps and status results. We use those fields to match a receipt, investigate a delay and answer a Privacy Policy request.

Account security

Phone verification comes before account access, and we do not need your wallet password or one-time security code in support messages. If your device changes, review the sign-in event and contact support through your account route.

Retention requests

Some records remain while needed for account support, payment reconciliation, security checks or legal duties. You may ask what we retain, why it remains and whether a correction or removal request can apply to that record.

Find Privacy Policy answers before account access

These Privacy Policy answers focus on the questions we expect from an Indonesian account holder using a phone, wallet or bank rail. They explain what to send, where to ask and why some records may remain after a request. If your situation is unusual, use the account support route with the smallest useful set of details.

It covers account details, phone verification, device and browser events, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains how to ask about access, correction, removal and retention of those records.

We may keep a transaction reference, timestamp, status and receipt details needed to match activity with your account. We do not need your wallet password or security code. Send only the relevant receipt fields when asking support to check a DANA or QRIS record.

Yes. Use the account support route and request an account-data copy under this Privacy Policy. Include the phone number linked to your profile and enough identity evidence for us to confirm the request. The response and available action depend on local law.

You can ask us to correct an inaccurate account detail through support. State which field is wrong and provide the phone number connected to the profile. We may repeat phone verification before making a change, so the request reaches the correct account.

Device events help us investigate unusual sign-ins, while payment records help match receipts, wallet status and bank transfer results. We retain each record only for its operational or legal purpose, and a removal request is assessed under this Privacy Policy and local law.

Ask through account support if you want details about cookies linked to a page or sign-in event. You can also adjust cookie controls in your browser. Restricting them may clear a sign-in state or require phone verification again during account access.

Some access, eligibility and data actions can differ by region because they depend on local law. We apply the route available to your account and explain any restriction through support. You can still ask which data process or request option applies to your profile.

Related Pages

elemen33 Indonesia elemen33 Casino Champions League Mix Parlay About Us Live Blackjack Turbo