Reference

beat4d Privacy Policy: Your Account Data Path

beat4d Privacy Policy explains how we handle the details connected with your account, phone verification and wallet activity.

Clear data purposesPhone verification stepsWallet activity contextIndonesia access wording
beat4d beat4d Privacy Policy: Your Account Data Path
CONTACT ROUTES

Get Privacy Help Near Account Support

Questions about our Privacy Policy should begin with the account support route available after you log in.

Account help Use the account help path to ask about data held for your login, phone…
Receipt matching For DANA, OVO, GoPay or QRIS questions, include the payment receipt or status reference…
Access questions If the Privacy Policy or an access notice is unclear, ask through support before…
HANDLING DETAILS

What Your Privacy Choices Cover

We keep the Privacy Policy practical by connecting each principle to an account action. Your login records, device behaviour and wallet references serve different purposes, so we describe them separately rather than…

Data handling

We use account, device and transaction data for stated operational purposes such as login continuity, phone verification, payment matching and security checks. We do not frame a visit to a game page as consent to unrelated data use.

Cookie choices

Cookies and similar device storage can help keep your session active, remember selected settings and show whether a page has loaded correctly. Your browser controls can manage these tools, although some account functions may then behave differently.

Account security

Phone verification and device signals help us check that an account request follows the expected access path. Never send a password through support. If a login looks unfamiliar, mention the event and time so we can investigate the record.

Data retention

We retain different records for different periods because login events, wallet references and legal requests do not serve the same purpose. Our Privacy Policy explains why a record may remain after an account action and when deletion can be requested.

Requesting changes

You can ask us to correct inaccurate account data or clarify how a particular record was created. Include the account identifier and describe the requested change precisely; we may need a verification step before altering protected details.

Policy contact

For a privacy question involving DANA, QRIS, phone checks or mobile access, contact account support with the smallest useful set of details. We will tell you what we need, why we need it and what happens next.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions we expect before you continue with beat4d. They cover the data connected with phone verification, local wallet references, cookies, device access and requests for correction or deletion. If your situation involves a specific receipt, login event or account record, use the support path above and provide only the relevant details. Access and eligibility depends on local law.

It covers account details, phone verification, login and device records, cookies, wallet references, security events, retention and privacy requests. It also explains how we handle data connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect an account request with the correct account and supports security checks during access. We use the verification result for that stated purpose, and we may request another check when a correction or protected account change needs confirmation.

Yes. When you use DANA or QRIS, we may handle the payment status and reference needed to match the wallet action with your account. The same principle applies to OVO, GoPay, bank transfer and virtual account records.

You can contact account support to ask what eligible data is held for your account or to correct an inaccurate detail. Describe the request clearly and provide the account identifier; we may verify your identity before releasing or changing protected data.

Cookies or device storage can preserve a session, remember settings and help us identify loading or security events. Browser controls can limit them, but login, phone verification or return-to-lobby behaviour may change when those controls are enabled.

Retention depends on the record and its purpose. Login events, security checks, wallet references and legal requests can require different storage periods. The Privacy Policy explains these purposes, while support can clarify a specific record linked to your account.

Access, eligibility, data rights and some retention duties can vary by location, so access depends on local law. We show applicable notices when relevant. If you are unsure whether a request applies in Indonesia, ask support before changing your account.