Reference

Privacy Policy for sema4d Account Data

sema4d keeps your account, wallet, device and support records connected to one clear Privacy Policy, so you can understand what we use and why before opening an account.

Clear data purposesWallet record contextAccount access choicesCookie controls
Explore Our Lobby Read FAQ
sema4d Privacy Policy for sema4d Account Data
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route helps when a Privacy Policy question appears beside an account or wallet event. Use the support path linked near the cashier area and include the phone number or account detail you used at sign-in, without sending your password or wallet PIN. We can then match your request with the relevant account, device session or payment reference and explain the next step.

Team online

Account data request

Ask us to confirm the personal data connected with your account after phone verification, and we will explain the request path without asking for your password.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, share the visible transaction detail through our support route so we can locate the matching policy record.

Access concern

If a mobile or desktop session looks unfamiliar, contact us through the cashier-linked support path and mention the device behaviour you noticed.

DATA PRACTICE

Six Checks Behind Your Privacy Policy

We keep this policy practical by describing the handling steps you can actually recognise while using your account.

Account creation

When you open an account, we collect the details needed for phone verification and access. We use those details to connect your requests to the correct account, not to ask for a wallet PIN.

Mobile and desktop sessions

A mobile browser and a desktop browser may create different session records. Device and browser signals help us identify a sign-in concern while keeping your account activity connected to the right session.

Cookie choices

Cookies can remember a selected setting and support account security. You can review cookie controls in your browser, while disabling some cookies may affect sign-in or the way policy choices are saved.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include a reference, status and time. We use these details to match a payment event without requesting your private wallet credential.

Retention checks

We keep personal records while they serve account support, security, transaction matching or legal needs. When a record no longer serves one of those purposes, we remove it or restrict further use.

Changes and questions

You can ask what data we hold, request a correction or question a processing purpose through support. Include the account contact used for phone verification so we can protect your request from unauthorised changes.

Privacy Policy Questions For sema4d

These Privacy Policy answers cover the searches we hear most often before account access: what we collect, how wallet records are matched, what cookies do and how to request a change. If your question concerns a particular device session or payment reference, use the support path beside the cashier and include only the details needed to locate it.

The sema4d Privacy Policy covers account details, phone verification, device and browser sessions, cookie choices, support messages and payment references. It explains why we use each category, how long it remains useful and how you can ask us to correct or restrict a record.

We collect the details needed to create and protect your account, including contact information used for phone verification and sign-in records. We may also keep support messages and security events so we can connect a request with the correct account.

Yes. The Privacy Policy covers transaction references and status details from DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account steps. We use those records to match activity, while your wallet PIN or private credential should not be sent to us.

We use device and browser signals to maintain a session, support sign-in security and investigate an unfamiliar access event. A mobile browser and desktop browser can produce separate session details, but neither replaces your account credentials or phone verification.

You can contact us through the support route near the cashier and request access to, or correction of, personal data linked with your account. Include the verified account contact and describe the change; do not include your password or wallet PIN.

We keep records while they support account access, security checks, transaction matching, support or legal needs. When a record no longer serves one of those purposes, we remove it or limit further use according to the applicable local requirements.

Where local law permits, you can ask us about cookie choices, processing purposes or removal of eligible personal data. Browser controls can manage some cookies, and our support route can explain which records must remain for security or legal reasons.

Related Pages

sema4d Indonesia Account information Esports Betting Hub About Us Lightning Roulette Room