Reference

Your mariaslot Privacy Policy, Clearly Set Out

Our mariaslot Privacy Policy explains what we collect when you open an account, verify your phone, and use DANA, OVO, GoPay or QRIS.

Account recordsWallet referencesCookie choicesAccess requests
Explore Our Lobby Read FAQ
mariaslot Your mariaslot Privacy Policy, Clearly Set Out
CONTACT PATHS

Get Privacy Help Beside Your Account

A clear contact path matters when a privacy question is tied to a login or wallet record. Start from the support route shown after you sign in, describe the account step involved, and include only the details needed to locate it. We can use the payment receipt or status reference for DANA, OVO, GoPay or QRIS without asking you to send a wallet PIN. For privacy requests, we may ask you to verify account ownership before changing or releasing personal records.

Team online

Account support

Use the support channel beside your account area when you need to ask what personal details are held, why a phone check is pending, or how to request a correction. Keep your message focused on one account and avoid sending passwords, wallet PINs or full payment credentials.

Payment references

If your question concerns DANA, OVO, GoPay or QRIS, share the receipt number, date and status shown in your account rather than private wallet access details. This gives us a practical way to locate the relevant record while reducing unnecessary personal data in your message.

Privacy requests

Ask through the same account support path for a copy, correction or deletion request where local law permits. We may compare your verified phone and account details before acting, then explain any records we must retain for security, dispute handling or legal duties.

DATA PRACTICES

What We Do With Your Personal Details

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account data

When you open an account, we handle the details needed to identify it and keep your profile connected to the correct phone verification step. We do not need your DANA, OVO, GoPay or QRIS PIN to match a payment status with your account record.

Device signals

Your mobile browser or desktop session may provide device and login signals used to recognise unusual access. These details help us protect the account when you move from the mobile login path to the lobby, without treating a device signal as your wallet password.

Cookies

Cookies can keep a signed-in session working, remember selected settings or show us how a page is used. You can manage cookies through your browser controls, although removing them may require another login or affect parts of the account privacy experience.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain reference numbers, timestamps, amounts and status details needed to reconcile an account action. Wallet credentials are not the purpose of these records, and you should never send them to support.

Security checks

A phone verification step, login event and account history can be compared when we investigate a sign-in or payment-status question. These checks may delay a change until ownership is clear, helping us avoid sending personal records or account changes to the wrong person.

Retention requests

We retain records only for the operational, security or legal reason connected to them, with timing depending on the record type. You can ask what remains, request a correction or seek deletion where local law permits through the account support channel.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a support request. They explain the practical difference between account data, device signals, cookies and payment references. If your situation is specific, use the signed-in support route and mention the exact account step, wallet reference or correction you need us to check.

It covers personal details connected with account creation, phone verification, login activity, device signals, cookies, support messages and payment references. It also explains why we use those records, how retention works and how you can request access or changes where local law permits.

Phone verification helps connect an account to the person requesting access and gives us a practical security check during account changes. If you ask about personal data or a DANA, OVO, GoPay or QRIS record, verification may be needed before we disclose or edit details.

No wallet PIN should be sent through support, and our payment records are used to match references, timestamps and status with an account action. For DANA, OVO, GoPay and QRIS questions, send the receipt or status reference shown in your account instead.

On a mobile browser, cookies may keep your session active, remember settings and help us understand page use. You can adjust them in your browser controls. Clearing cookies may sign you out or require another phone verification step when you return to the account.

Yes, send a request through the signed-in support path and identify the account using the verified phone details requested there. We may confirm ownership first. We then explain which records can be provided and whether any restriction applies under local law.

You can ask us to correct inaccurate account or contact details through support. Include the field that needs attention and the reason for the change, but do not include passwords or wallet PINs. We may check the phone verification record before updating the account.

You may request deletion where local law permits. Some records can need continued retention for account security, payment reconciliation, dispute handling or legal duties. Our support team can explain which data is affected, what remains, and why a retention period applies.

Related Pages

mariaslot Indonesia Account information Esports Dota 2 Barong Dance Slots mariaslot Casino