Reference

medusa888 Privacy Policy For Your Account

medusa888 Privacy Policy sets out what we collect when you open an account, sign in, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet-linked account stepsAccess request pathCookie choices
Explore Our Lobby Read FAQ
medusa888 medusa888 Privacy Policy For Your Account
HELP WITH DATA

Three Ways To Ask About Privacy

A clear contact route matters when a name, phone number or wallet reference looks wrong. Our support path starts from the signed-in account area, where you can raise a question about the Privacy Policy or ask us to check a record connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer. Include the account detail involved and the change you want, but never send a password or one-time verification code. We use the account and payment context to route the request to the right check.

Team online

Account request

Use the support route linked to your signed-in account when you want to ask what personal data we hold or why a phone verification step is required. We may ask you to confirm account ownership before discussing details, so another person cannot access your record.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell us which transaction label needs checking and when it appeared. For virtual account or bank transfer records, include the visible reference only; keep passwords, PINs and one-time codes private.

Policy question

For a question about cookies, retention, deletion or access rights, send the request through our account support path with a short description. We will use the details supplied to identify the relevant policy point and may request an ownership check before making a change.

DATA CONTROLS

How We Handle Six Privacy Areas

Privacy work follows the same account flow you use for the lobby: we collect a defined detail, apply it to a defined purpose, and restrict access to the people or systems that…

Account data

When you open an account, we use the details you provide to create your profile and complete the clear phone verification step before access. Keeping your phone detail current helps us identify the correct account when you request a correction or ask about stored data.

Payment references

DANA, OVO, GoPay and QRIS can return a transaction reference or status connected with your account. Virtual account and bank transfer records may contain a bank-side reference. We use these details to reconcile activity, resolve a status question and protect the account from mismatched records.

Device signals

Your phone or desktop browser may share technical signals such as browser type, session details and security events. We use these signals to recognise unusual sign-in behaviour and keep the account path safer. They are not a substitute for your password or phone verification.

Cookies

Cookies can keep a session working, remember selected settings and help us detect repeated security errors. You can manage cookies through your browser controls, although disabling some types may interrupt sign-in or make the account path ask for checks again.

Retention

We keep account, support and payment records for as long as needed for account operation, security checks, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers where practical.

Change requests

You can ask us to access, correct or delete eligible personal data through the signed-in support route. We first confirm that the request comes from the account holder, then explain any record that must remain for security, dispute or legal reasons under the rules that apply.

Privacy Policy Answers For medusa888

These Privacy Policy answers address the searches you may make before opening an account or linking a local wallet. We keep each response tied to the actual account journey: phone verification, sign-in, device access, payment references, cookies and support requests. If your question concerns a specific record, use the signed-in support path and identify the data category without sending secret credentials.

The medusa888 Privacy Policy explains the account, phone verification, device, cookie, support and payment-reference data we may handle. It also describes our purposes, retention approach, security checks and the route you can use to request access, correction or deletion where local law permits.

We use your phone number to create and identify your account and to complete phone verification before account access. It also helps us match a privacy request to the correct account. Do not place verification codes or passwords in support messages.

Yes. The Privacy Policy covers payment references and status details linked with DANA, OVO, GoPay and QRIS, as well as virtual account and bank transfer references. We use them to reconcile account activity, address payment questions and detect mismatched or unusual records.

When you sign in from a phone or desktop browser, we may receive technical signals such as browser type, session details and security events. We use them to identify unusual access and protect your account. These signals do not replace your password or phone verification.

Use the support route inside your signed-in account and state whether you want access to a record or a correction. Tell us the relevant category, such as profile, device, cookie, support or wallet reference. We may confirm account ownership before responding.

You can submit a deletion request through the signed-in support path where local law permits. We assess the request against records needed for account security, payment reconciliation, disputes or legal duties. If some data must remain, we explain the reason and applicable limitation.

The Privacy Policy describes our handling of data for the account journey in Indonesia, including local wallet references and browser access. Account access depends on local law. If a local rule changes what we can provide or retain, that rule applies to your request.

Related Pages

medusa888 Indonesia royalpkr99 medusa888 Casino FAQ About Us