Reference

Open mazoslot with clear Legal terms

mazoslot sets out its Legal position before you open an account, including access conditions, account checks, privacy handling and payment records.

Policy accessAccount checksIndonesia termsLocal-law wording
mazoslot Open mazoslot with clear Legal terms
CONTACT ROUTES

Choose a direct Legal contact path

A clear contact route helps when you need a policy answer rather than a lobby explanation. Tell us whether your question concerns account access, personal data, cookies, payment records or a request to change stored details. Include the email or phone number attached to your account, but do not send a password, wallet PIN or full payment credential. Our team can then match the request to the correct account step and explain what can be changed, what must be retained, and why a local-law condition may apply.

Team online

Account access

If phone verification prevents access, contact support through the account help route and describe the screen you reached. We use the account identifier and verification status to locate the issue, then explain whether an extra check is required before you can continue where local law permits.

Privacy requests

For a copy, correction or removal request involving your personal data, send the account email and the specific records concerned through our support channel. We confirm ownership first and explain any Legal reason that transaction, security or dispute records must remain stored.

Payment records

When a DANA, OVO, GoPay or QRIS receipt does not match your account history, share the reference, date and amount shown in your wallet. Never send a wallet PIN. We compare the receipt with the account ledger and tell you the next policy step.

DATA PRACTICES

Understand our Legal handling steps

Legal handling is practical: we separate account access data, payment records and security events so a request reaches the right process.

Account identity

Before changing account contact details, we compare your request with the phone verification already attached to the account. This reduces the chance that another person redirects access. If the details do not match, we explain the additional evidence needed instead of changing the record immediately.

Cookie choices

Our site may use necessary cookies to keep a session active and remember basic page settings. Optional browser controls can restrict other cookies. If a restriction interrupts login or the Legal page, clear the affected site data and contact support with your device and browser details.

Payment retention

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account record may be retained for reconciliation and dispute handling. The record can show a reference, status and timestamp, but it does not give our team your wallet PIN or banking password.

Security events

We may record sign-in attempts, verification changes and account recovery actions to investigate access problems. If you see an unfamiliar session, change your account password through the available account path and contact us promptly so the event can be checked against those records.

Record changes

You can ask us to correct inaccurate personal details or clarify how a record is used. State the exact field or transaction you mean, such as a phone number or QRIS reference. We verify ownership, assess the request, and explain the result in a direct reply.

Who to contact

Use the support route for Legal questions about access, data, cookies, account security or retention. Include your account email, the relevant date and a short description. We do not need your password, one-time code, wallet PIN or complete bank credentials to begin checking.

Check common mazoslot Legal answers

These Legal answers cover the account and data questions you are most likely to have before opening an account or asking for a change. They explain the local-law wording, verification path, payment records, cookies, access requests and contact method without treating a general lobby question as a policy answer. If your situation is different, send the precise account or record detail to support so we can respond to the actual case.

Access depends on local law. Where local law permits, you can continue through the account path after supplying accurate details and completing any requested phone verification. We may restrict access when eligibility cannot be confirmed or when a local requirement prevents the service from being provided.

Phone verification connects account access to a contact method you control and helps us handle recovery or unusual sign-in activity. The check can also be relevant when you request a change to personal details. If verification fails, contact support without sending your one-time code.

DANA and QRIS activity is linked to the account reference, status and timestamp supplied by the payment process. We use those details to reconcile a receipt or investigate a mismatch. We do not ask for your wallet PIN, and retention can apply when a payment or dispute needs an audit trail.

Yes. Send a correction request through support and identify the field, such as your phone number or account email. We verify that you control the account, check the requested change against existing records, and tell you whether the update can be made under the applicable Legal requirements.

You can ask about deletion for a specific record or account detail. Some data may need to remain stored for payment reconciliation, account security or dispute handling. We review the request, confirm ownership and explain which information can be removed and which retention rule applies.

Necessary cookies can keep your session active and preserve basic page settings, including the path back to the Legal area. Browser controls may restrict optional cookies, but blocking necessary cookies can interrupt sign-in. If that happens, clear site data and contact support with your browser details.

Use the account support route and state whether your concern involves access, privacy, cookies, security, retention or a payment record. Include your account email, phone verification status and relevant date when useful. Do not include passwords, one-time codes, wallet PINs or full bank credentials.