Reference

Privacy Policy for Your elloslot Account

The elloslot Privacy Policy shows what we collect, why we use it and how you can request changes before opening an account.

Clear data purposesCookie choicesAccount request pathWallet record context
elloslot Privacy Policy for Your elloslot Account
REQUEST HELP

Privacy Help Beside Login And Wallets

A direct support path helps you act on this Privacy Policy without searching through unrelated pages.

Account data request Ask us to locate the account data connected with your phone verification or login record. We may request enough account detail to confirm that the request belongs to you before discussing or changing anything.
Wallet record check For a DANA, OVO, GoPay or QRIS record, share the payment reference and approximate date rather than a wallet PIN. We use that narrower detail to trace the relevant record under this Privacy Policy.
Cookie question If a cookie choice behaves differently on your phone and computer, tell us the device path and browser setting. We can explain which cookie purpose applies and what adjustment request we can process.
DATA PRACTICES

Six Data Safeguards We Apply

Privacy work is handled through practical account steps rather than vague promises. We separate identity checks from ordinary browsing records, limit payment references to the task they support and keep requests tied…

Account details

We collect details needed to create and protect your account, including the phone verification step. We use those details to match your access request and investigate an account security concern.

Payment references

A DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI reference is used to identify the related wallet or bank event. We do not ask for your wallet PIN in a privacy request.

Cookie choices

Cookies can support sign-in continuity, security checks and preference storage. You can adjust browser controls, while some settings may affect how a protected account session is recognised.

Device security

We may record device and session signals when you sign in from a phone or computer. These signals help us spot unusual access and keep a requested account action connected to the right session.

Retention periods

We keep account, security and payment records for as long as needed for the stated service purpose or a legal requirement. When a record is no longer needed, our process removes or anonymises it.

Changes and contact

You can ask for access, correction or a privacy clarification through support. Include your account phone and request type, but omit passwords, wallet PINs and full payment credentials.

Privacy Policy Questions Indonesia Asks

These answers address the searches we hear before an account is opened or a wallet record is checked. Each response stays within the scope of the elloslot Privacy Policy, with practical steps for account data, device access, cookies and payment references. If your situation needs a record-level decision, use the support path above and describe the specific request.

It covers account creation, phone verification, login activity, cookies, device signals, payment references and privacy requests. The policy explains why we use each data type, how long records may remain and how you can ask for access or correction.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. Send the relevant reference, not a PIN, when you ask us to locate or explain a wallet record.

Contact support through the privacy request path and identify your account phone number plus the data category you want checked. We may verify account ownership before sharing details, so your request is not exposed to another person.

You can request a correction when an account detail or contact record is inaccurate. State what appears wrong and the replacement detail. We may retain the earlier entry where a security or legal record requires it.

On a phone, cookies may support sign-in continuity, security checks and saved preferences. Browser controls let you change choices, although removing a necessary cookie can interrupt a protected session or require phone verification again.

Retention depends on the purpose of the record, account security needs and any legal requirement. A payment reference may remain while it is needed for reconciliation or a request, then it is removed or anonymised through our process.

Yes. You can read this Privacy Policy and contact support before completing the account path. Ask about a specific data purpose, cookie setting or payment reference, and access remains subject to local law.