Reference

Privacy Policy for Your stadium4d Account

Your stadium4d Privacy Policy explains what we collect when you open an account, sign in from a phone, or choose DANA, OVO, GoPay, QRIS, bank transfer, or a…

Account dataWallet recordsDevice choicesCookie controls
stadium4d Privacy Policy for Your stadium4d Account
PRIVACY CONTACT

Get Help With a Privacy Request

A clear contact path helps when your account details or wallet record needs attention. Contact our support team through the account support route and include the phone number linked to your profile…

Account access If you cannot complete phone verification, tell us which account step stopped and which device you used. We can explain the data connected with that access event and help route a correction request without asking for your password.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the payment reference and date rather than private wallet credentials. We use the reference to locate the stored status and explain what may be retained.
Privacy requests Ask for a copy, correction, restriction, or deletion assessment through support. Include the phone number on your profile and the request in plain English; we may ask for an account check before releasing personal records.
DATA CARE DETAILS

What We Do With Your Personal Data

Privacy at stadium4d covers more than the form used to open an account. We describe how data moves through login, phone verification, wallet status checks, cookies, and account support.

Account creation

When you open an account, we use the details you submit to create your profile and send account messages. Phone verification confirms that the access step belongs to you; we do not ask you to place a password in a support message.

Security signals

Login time, browser type, device details, and approximate network signals can help us identify unusual access. These records support account protection and may be reviewed when a sign-in or wallet status check does not match your usual pattern.

Cookies

Cookies can remember a session, preserve selected settings, and help us understand which policy page you opened. You can manage browser cookie controls, though disabling necessary cookies may interrupt login or prevent a requested account step from working.

Payment references

A payment reference can connect a deposit or status check with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We use the reference to reconcile the account record and do not need your wallet PIN.

Retention choices

We keep personal data only for an operational, security, dispute, or legal purpose described in this policy. When that purpose ends, we remove, anonymise, or securely restrict the record according to the applicable retention process.

Change requests

You can contact support to request access to your stored data, correct an error, ask about deletion, or question a cookie setting. We verify the account request first so personal records are not disclosed to the wrong person.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before you continue from a phone or desktop browser. They cover the records behind login, payment references, cookies, security checks, retention, and contact requests. If your situation is not listed, contact support with the account phone number and a short description of the issue.

The stadium4d Privacy Policy covers personal data used for account creation, phone verification, login security, wallet status, payment references, cookies, support requests, and retention. It applies to your access from Indonesia where local law permits and explains how to ask about, correct, or remove eligible records.

We use your phone number to create and identify your account, complete the phone verification step, and help support find the correct profile. It can also help us investigate a stalled login or wallet status. Do not send your password or wallet PIN when requesting help.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account steps. We use those references to match an account event with a receipt or status check, while your private wallet PIN remains outside our support request.

We may store browser type, device details, login time, and approximate network signals linked to an account event. These details help us protect access when a phone verification or sign-in looks unusual. They also help explain why a mobile browser session may need to start again.

Contact support through the account support route and state whether you want a copy, correction, deletion assessment, or another policy request. Include the phone number linked to your profile and any payment reference if relevant. We may verify account ownership before discussing personal records.

We retain records for the operational, security, dispute, or legal purpose that requires them. Payment references may remain while a status or dispute needs resolution. When a purpose ends, we remove, anonymise, or restrict the record according to the applicable retention process and local requirements.

Yes. Ask support which cookie category your question concerns, or manage cookies through your browser controls. Necessary session cookies may be needed for account access, while disabling them can affect login, saved settings, or the return path from a mobile browser to the lobby.