Reference

Legal details for your maskot33 account

maskot33 Legal sets out how we handle account access, wallet records, policy requests and location-based eligibility for Indonesia.

Indonesia account rulesPhone verificationPolicy contact pathLocation-based access
maskot33 Legal details for your maskot33 account
CONTACT ROUTES

Get help with a Legal question

A clear contact route helps when you need a policy answer rather than a lobby answer.

Account policy request Use the support path attached to your signed-in account when you need clarification about account terms, phone verification or an access decision. Include the policy heading and your registered contact detail so we can identify the correct account record without asking you to send a password.
Wallet record question For a Legal question connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, attach the transaction reference and date shown in your account. We use those details to check the record while keeping the request separate from your private wallet password or PIN.
Data rights contact Ask through the account contact route if you want to request a copy, correction or removal of personal details where the applicable rules allow it. Tell us exactly which record you mean and how we should reply; we may first verify account ownership before changing or releasing data.
DATA PRACTICE

How we handle Legal requests

We handle policy requests through account-linked records rather than informal messages that cannot be matched safely.

Data handling

We use personal details to maintain the account, verify ownership, review policy requests and connect a payment reference with the correct account. We do not need your password, wallet PIN or one-time code in a support message. Send only the details needed for the specific Legal request.

Cookies and sessions

Cookies can help keep a signed-in session working and remember choices made on the site. If Legal content behaves differently after you clear cookies, tell us your device type and browser path. We can then distinguish a session setting from an account access decision.

Account security

Phone verification is part of the account access path, and we may ask for additional ownership checks before discussing private records. Never place a password, wallet PIN or one-time code in a request. If your contact number changes, update the account details before asking us to discuss sensitive data.

Record retention

We keep account, transaction and policy-request records for the time needed to operate the service, resolve disputes, protect against misuse or meet a legal obligation. A retention request must identify the record or account involved, because different records can have different required handling periods.

Correction request

You can ask us to correct an inaccurate name, phone number or account detail through the signed-in support route. State the current value and the replacement value, then complete any ownership check we request. We will explain if a record cannot be changed because it must remain accurate for a legal or transaction purpose.

Access restriction

If access is paused, the notice attached to your account is the starting point for clarification. We may need to check location, phone verification, account consistency or a payment reference. Where local law permits, we will tell you which next step or document is relevant without exposing internal security controls.

Answers about maskot33 Legal

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They explain the practical route for account data, payment records, cookies, access and contact details without treating a general lobby question as a Legal matter. If your situation is not covered, use the account-linked support path and quote the relevant policy heading.

maskot33 Legal covers account terms, phone verification, personal data handling, cookies, payment records, access decisions and requests to correct or remove data. Eligibility depends on local law. Check the current notice before opening an account, because the applicable conditions can vary with your location and account status.

Yes. Access depends on local law, and we may show different services or request additional checks when your location or account details require it. If an account is paused, use the signed-in support route and ask which policy heading applies. We will not ask you to bypass a legal restriction.

Send a data request through the account support path and identify the records you want, such as profile details, phone verification history or a payment reference. We may verify ownership before replying. Do not include your password, wallet PIN or one-time code in the request.

You can ask for a correction through the signed-in account route. Provide the detail currently shown, the correct replacement and a contact method linked to the account. We may check ownership first. A transaction or legal record may need to remain unchanged when accuracy rules require its preservation.

We use the payment reference, date and account details to match DANA, OVO, GoPay or QRIS activity with the correct request. For bank transfer or virtual account records, include the reference shown in your account. We do not need your wallet PIN or banking password to check a status.

Read the notice attached to your account, then contact us through the signed-in support path with the policy heading and your registered contact detail. Access is available where local law permits. We may request phone verification or another ownership check before explaining the next permitted step.

Tell us which device and browser path you used, what changed after cookies were cleared, and which Legal page was affected. Cookies can support a signed-in session, but they do not replace account verification. We can review the session issue without asking for your password or one-time code.