LEGAL REFERENCE

How layarslot Handles Your Account Data

This is our privacy policy — the plain-English version of how we collect, store and use the data tied to your layarslot account. We've written it for you...

Account dataCookie useRegion-awareDANA-readyPolicy v3
layarslot How layarslot Handles Your Account Data

Our Privacy Posture for Indonesia

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

PLAYER SUPPORT

Privacy Contact Paths

If anything in this policy is unclear, or you want to exercise a data right, reach us through one of these channels. We route privacy questions to a dedicated reviewer rather than the general lobby desk.

Team online

Privacy Inbox

Email [email protected] with your registered username and the request type — access, correction, or deletion. We confirm receipt within one working day and resolve most tickets inside a week.

Live Chat Escalation

Open the lobby chat widget and type 'privacy' to skip the standard queue. Our agent will hand the thread to a data reviewer who can act on policy-level requests for your account.

Postal Reference

For formal notices tied to Indonesia data protection rules, request our registered mailing address through the privacy inbox. We respond with the correct postal route for your jurisdiction within two days.

TRUST MARKERS

How We Review This Policy

This document isn't a static page we forgot about. Here's who looks at it and how often.

Quarterly Review

Our policy text is reviewed every three months against current Indonesia data rules and any platform changes. The last revision date sits at the foot of the policy so you can see when it last moved.

Legal Sign-Off

A qualified counsel familiar with Southeast-Asian online gaming rules signs off each revision before it goes live. We do not push policy changes through without that external check.

Engineering Audit

Our infrastructure team confirms that the storage and encryption claims in this policy match what's actually deployed. If a system changes, the policy wording is updated in the same release.

Data Minimisation

We test new lobby features against a 'do we really need this field' question before launch. If a feature works without collecting extra data, that's the version we ship to your account.

Breach Protocol

If a data incident affects your account, we notify you directly through your registered email within the timeframe Indonesia regulation requires, with a plain summary of what happened and what we did.

Staff Training

Every team member with account access completes privacy training before their first shift and refreshes it annually. Access logs are kept so we can trace who viewed what, should you ever ask.

Consistency Across Our Policy Pages

Our privacy text lines up with the other legal documents on the site. Here's how the pieces fit together.

Terms of ServiceThe terms page defines your account contract; this privacy page defines what data that contract produces. Both use the same definitions for 'account', 'session' and 'payment reference'.
Cookie NoticeCookies sit in their own notice but follow the same retention logic described here. Session cookies clear at logout; preference cookies last as long as your lobby settings need them.
AML PolicyAnti-money-laundering checks may require us to hold ID documents longer than standard account data. That exception is flagged in both this policy and the AML page so the rules match.
KYC WorkflowDocuments you upload during identity checks follow the storage rules described in section three here, and the KYC page references this policy for retention specifics rather than restating them.
Marketing ConsentPromotional contact preferences live in your account settings. This policy is the source-of-truth for how those toggles map to actual email and push behaviour.
Third-Party ProcessorsOur processor list — payment, hosting, analytics — is published as an annex to this policy and updated in the same revision cycle, so what you read here matches the live vendor set.
Complaint RoutesIf our handling falls short, the complaints page explains escalation to Indonesia's data authority. The contact paths here are the first step in that route.
QUICK SIGNAL

What This Policy Page Includes

A quick map of what's on this page so you can jump to the part you came for. Each block below is a section we keep visible and...

Scope Statement The opening clause names every layarslot surface this policy covers...
Data Categories A clean list of the data types we touch: identity...
Retention Table A simple table showing how long each data type stays...
Your Rights Panel A plain-language panel listing the rights you can exercise —...
Change Log Every revision is logged at the foot of the page...
Region Notes Short notes flagging where supported regions inside Indonesia have specific...

Privacy Policy Questions

We collect your name, contact details, date of birth, and the payment reference you use for DANA, OVO, GoPay or QRIS. Device and session data are captured automatically to keep your account secure.

Yes. Email our privacy inbox from your registered address and we'll compile an account export within the timeframe Indonesia data rules require, usually inside seven working days at no charge to you.

Standard account data clears within thirty days of closure. Transaction and identity records are held for the period financial and anti-money-laundering rules in supported regions require, then permanently deleted from our systems.

No. We do not sell or rent your data to outside marketers. We share data only with processors who run payments, hosting and fraud checks, and only the fields each one needs to do its job.

Payment references are tokenised before storage, so the raw wallet details never sit in our main database. Access to the token vault is restricted to the payment engineering team and logged for audit.

We notify you directly through your registered email inside the window Indonesia regulation sets, explain what data was involved, what we've already done, and the steps you can take on your side.

Most fields can be edited inside your account settings panel. For locked fields tied to identity verification, contact our privacy inbox with the correction request and supporting document, and we'll update the record promptly.