LEGAL REFERENCE

Privacy Built Around Your Account

42 erek puts privacy beside the lobby from the first account screen: we explain what we collect, why we need it, and how your choices stay visible while...

Account dataPrivacy choicesSecurity recordsIndonesia support
Enter Game Lobby Read FAQ
42 erek Privacy Built Around Your Account

How This Privacy Policy Applies

This Privacy Policy explains how 42 erek handles personal data connected with account creation, sign-in checks, profile settings, support requests, device security, and activity inside our lobby where local law permits. We collect only what helps us run your account, protect access, answer you, meet legal duties, and keep service records accurate. We may process payment-related references, including DANA, OVO, GoPay, and

QRIS labels, when those details are needed for reconciliation or support, but this policy is about data handling rather than payment promotion. By opening or continuing your account, you agree that we use your data in the ways described here, and you can contact us to ask about access, correction, deletion, or retention.

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

SUPPORT

How To Reach Our Privacy Team

Privacy requests work better when they reach the right place. Use the paths below for account data questions, correction requests, consent choices...

Privacy email Use the privacy email for access, correction, deletion...
Account help panel Open the account help panel when your privacy...
Contact form Send a clear request through our contact form...
PLATFORM TRUST SIGNALS

How We Keep This Policy Current

We treat this policy as live brand copy, not a forgotten legal block. Our internal checks focus on plain wording, accurate data categories, local access wording, and contact...

Policy owner

A named internal owner keeps the privacy wording aligned with how our account, security, and support teams actually handle data...

Plain-language edits

We remove vague legal phrasing when clearer wording can explain the same privacy point. The aim is simple: you should...

Local wording check

Access language is checked against supported regions and where local law permits. That keeps the policy honest about availability without...

Data category mapping

Each data category links back to a purpose, such as account security, support, legal compliance, or service records. We avoid...

Retention checks

We check retention wording against real record needs, including dispute handling, legal duties, and account safety. When a record is...

Change control

When privacy wording changes, we keep the new version consistent with related pages. Material changes are written plainly so you...

Consistency Across Our Policy Pages

Our legal pages should feel connected when you move between them. The privacy page, terms, cookie text, and support wording use the same definitions where possible, so your...

Account dataWhere another page mentions your account details, this policy explains the privacy reason behind that collection. We keep the language aligned so the same field is not described in conflicting ways.
Security checksSecurity wording stays consistent across account access, device checks, and support verification. This privacy page explains the data side, while other pages explain the service rule attached to it.
Cookie referencesCookie wording connects to this policy when browser data helps us remember sessions, measure page stability, or protect sign-in. The same purpose language appears wherever cookie tools are described.
Support recordsWhen support pages ask you to provide account details, this policy explains how those records are stored, used, and retained. The goal is one privacy meaning across every contact path.
Marketing choicesAny page that invites you to receive updates should match this policy's consent wording. You can choose message preferences without changing how core account security data is handled.
Regional accessWhere access is described for supported regions, privacy wording also explains the data checks we may need. We do not separate availability language from the data handling behind it.
Policy updatesChange language across our legal pages follows the same style: clear date cues, plain wording, and practical contact options. That helps you compare updates without decoding different legal tones.
PLATFORM SNAPSHOT

Policy Layout Cues You See

The policy page uses visible cues to help you scan privacy duties before you open an account. These blocks are not lobby features; they are layout signals that show where data categories, choices, security...

01
Short policy summary The first block states the privacy purpose before legal detail begins. You can quickly see that the page covers account data, security records, contact requests, and your choices.
02
Clear data labels Data categories are named in plain language, such as profile details, device signals, support messages, and payment references. That helps you understand the record type before reading the longer explanation.
03
Choice markers Choice sections show where you can ask for access, correction, deletion, or message preference changes. We place them near contact routes so action does not feel hidden away.
04
Security cues Security paragraphs explain why we log sign-ins, device signals, and suspicious access attempts. The wording connects each record to account protection instead of leaving the reason unclear today.
05
Retention markers Retention blocks explain that some records must stay for legal, support, or safety reasons, while other data may be deleted or anonymised when the purpose ends for us.
06
Contact prompts Contact prompts sit beside rights language so you know how to act on a privacy concern. We keep the next step close to the explanation that creates it.

Privacy Questions Before You Join

We collect account details you provide, sign-in records, device signals, support messages, and activity needed to operate the lobby. Each category must connect to security, service delivery, legal duties, or your request.

When those labels appear in account records, we use them to reconcile a request, trace a support issue, or meet record duties. We do not treat them as open permission for unrelated messaging.

Yes. Contact us with the account email and the field you believe is wrong. We may verify your identity first, then correct the record when the request is valid.

You can ask for deletion, and we will assess the request against legal, security, and support needs. Some records may need to stay for a limited period before removal.

We limit support conversations to details needed for the case, verify account control before sharing data, and keep records for follow-up. Please avoid sending documents or screenshots we do not request.

Yes, privacy wording may change when our account flow, security checks, legal duties, or support paths change. We update the page date and write changes in plain language.