LEGAL REFERENCE

Privacy Policy For Your 58 erek Account

58 erek runs live casino tables, slot rooms and sportsbook markets for Indonesia, and this Privacy Policy explains how we handle the account data behind that access. Open...

Indonesia privacy scopeAccount data useQRIS contextSupport contacts

Browse the Lobby Read FAQ

How We Handle Your Data

This Privacy Policy applies when you create, access, or manage your 58 erek account. We collect the details needed to run your account, verify access, secure sessions, record consent, and keep transaction references tied to your balance history. We use that data to provide the lobby where local law permits, protect your account from misuse, respond to your requests, and keep records

required by service, security, tax, and compliance duties in supported regions. We do not sell your personal data. We share limited data only with service partners that help operate logins, risk checks, support tools, payment references, analytics, and hosting. DANA, OVO, GoPay and QRIS may appear as account context when a transaction record is created, but this policy is about data handling,

access rights, retention, and contact routes.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Privacy Contact Routes You Can Use

If you want to ask about data access, correction, deletion, consent, or retention, start with the route that matches your account status. We keep privacy requests separate from general lobby questions so your request reaches the team that can check identity and records.

Team online

Signed-in live chat

Use live chat after sign-in when your privacy question connects to your account, recent session, or transaction record. We can confirm the request path and tell you what detail we need next.

Privacy email

Send email for access, correction, deletion, or consent questions that need a written trail. Include your account nickname, contact number, and clear request, but never include your password.

Account inbox

Use the account inbox when you want a privacy reply kept beside your 58 erek profile. It helps us link your request with the correct record without extra public messaging.

REVIEW SIGNALS

How We Check This Policy

Our privacy wording is maintained as part of the account experience, not as a detached legal file. We check whether each clause still matches the live casino, slots, sportsbook, support, security, and...

Policy owner

We assign policy ownership internally so privacy wording is checked before release. The owner tracks clause changes, market wording for Indonesia, and whether each section still matches our account flow.

Plain English

We write privacy terms in direct en-ID English so you can understand what data we collect, why we use it, and how to reach us without reading legal jargon.

Data mapping

Our checks map sign-in, lobby, support, and transaction reference data to policy clauses. If a field is added to the account flow, the policy must explain its purpose.

Partner checks

When hosting, risk, analytics, or payment-reference partners support our service, we check that their role is described here and that shared data stays limited to the stated purpose.

Change log

Material policy edits are dated and prepared for clear notice inside the site. We aim to keep changes visible before you continue with account activity.

Contact testing

We test privacy contact routes so requests do not disappear into general support. Each path should tell you what to send and how we verify your identity.

PLATFORM COMPARISON

Consistency Across Our Policy Pages

Privacy does not sit alone. We align this page with the cookie text, account terms, support scripts, security wording, and closure steps so the same data category is not described differently when...

Cookie privacy

The cookie text uses the same data categories as this Privacy Policy, so browser identifiers, device details, and analytics signals are not described in competing ways across pages.

Account terms

Account terms explain what you can do in the lobby; this Privacy Policy explains how related records are handled. We keep definitions aligned so rights and duties remain clear.

Promo notices

Promo wording may reference eligibility data, but privacy wording explains why that data is checked. We avoid hiding data use inside short campaign copy or pop-up text.

Security page

Security content describes how we protect accounts; this policy states which security data may be processed. Matching language helps you understand both protection steps and data use.

Local access

Where local law permits, access wording matches privacy wording for supported regions. We avoid promising availability in places where data handling or service access may differ.

Support scripts

Support scripts follow this policy when our team asks for identity checks. We keep questions narrow, linked to your request, and away from details we do not need.

Account closure

If you ask to close your account, retention wording here matches closure steps elsewhere. Some records may remain for legal, security, dispute, or compliance purposes before removal.

PLATFORM SNAPSHOT

Privacy Signals Across The Layout

This page is designed to make privacy choices easy to spot while you decide whether to open an account. The visible blocks focus on policy date, data categories, rights prompts, partner roles, retention cues...

Policy date The date block helps you see when the policy was last adjusted. It belongs near the opening copy so you can decide whether to read new clauses before continuing.

Account context Short cues explain that privacy applies to sign-in, lobby, support, and transaction records. This keeps the page tied to your account flow, not generic legal text.

Data categories Category cards group contact details, device signals, session records, and transaction references. Clear grouping helps you find the part that matches your concern without scanning every clause.

Rights prompts Rights prompts point you toward access, correction, deletion, and consent questions. Each prompt links back to contact routes so you can start a request with less friction.

Partner labels Partner labels name the service roles behind hosting, support tools, analytics, risk checks, and payment references. The aim is to show why limited sharing can happen.

Retention cues Retention cues explain that some records are kept only as long as needed, while legal or security records may stay longer. That helps set realistic expectations.

Privacy Questions Before You Join

We collect account details, contact records, device signals, session activity, consent records, security logs, and transaction references needed to operate your account and the lobby where local law permits.

We use your data to create access, secure sessions, show account balances, respond to requests, maintain records, detect misuse, and meet service or compliance duties in supported regions.

No. We do not sell your personal data. Limited sharing can happen with service partners that support hosting, security, analytics, support tools, risk checks, and transaction references.

Yes. Contact us through the privacy email, signed-in chat, or account inbox. We may verify your identity first so changes are made only for the correct account.

We keep records only as long as needed for service, legal, tax, dispute, security, or compliance purposes. Some account data may remain after closure when retention duties apply.

DANA, OVO, GoPay and QRIS references may appear in transaction records connected to your account. This policy explains how those references are stored, used, shared, and retained.