Reference

What This Policy Means for You

We keep the policy in the footer and in Account > Help > Legal, so you can read it before you open an account.

Local-law accessAccount > Help > LegalMobile and desktopData and cookies

What We Keep and Why

mataslot77 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use this page to set the rules for account records, cookie use, and change requests. Identity details, device logs, and support history help us confirm who asked for a change, keep duplicate sign-ins out of the record, and answer questions about the account trail. If

1
local law where you are does not allow access or keeps certain actions restricted, those actions stay unavailable. Payment context from DANA, OVO, GoPay, and QRIS only appears in your own transaction history and only when you choose those rails. We do not use this page
2
to promise access beyond the law; we use it to show what we store, why we store it, and how you can ask for correction. You can submit a request from the help form or the account menu, then our team checks it against the registered
3
details.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP CHANNELS

Where Policy Requests Go

When you need a change or a question about this page, we route it through live chat, the help form, and the account inbox. Our team replies daily from 08:00-24:00 WIB, and the same thread stays attached to your request so you do not need to repeat the details. On phone or desktop, you can open the footer link, choose Legal, and send the issue from there.

Team online

Live chat

Open the chat bubble in the footer or inside your account. We use it for quick policy questions, then attach the conversation to your request so the history stays in one place.

Help form

Use the form under Account > Help > Legal when you need correction or access changes. It asks for your registered name, the issue, and the date so we can match the record.

Account inbox

If chat is closed, send the message through your account inbox and we will answer in the next support window. This keeps your request tied to the same login and device record.

DATA CARE

How We Handle Requests

We keep this policy tied to account security, not promotion. Data, cookies, and request logs are handled together so we can verify your identity, avoid accidental edits, and answer the same question…

Data handling

We use account data only for login checks, request handling, and record keeping. We do not mix policy requests with unrelated account actions, and we only share the minimum needed inside the support team.

Cookies

Cookies keep your language, session, and device state stable while you read the page. They do not replace your account password, and they do not store your DANA, OVO, GoPay, or QRIS balance.

Account security

Your login should stay private. If you open the page on a shared phone, sign out after the request so the next person cannot view your account trail or message history.

Retention

We keep request logs long enough to resolve the case and meet the rules that apply to your account. After that, the record stays only where the law or internal audit need it.

Change requests

To correct a detail, send the exact field name, the current value, and the value you want changed. We compare it with the registered record before we update anything.

Contact path

For access, correction, or deletion questions, open the help form or live chat from the footer. If the matter needs a second check, we continue it by the same channel until it is closed.

Questions About This Policy

These are the questions we hear when you want to check access, correction, and record handling before you open an account. The answers stay plain: who can read the page, what we store, how long we keep it, and where you send a request. If your situation changes because of local law, the same contact path applies and we update the record when the law allows it.

Yes. The page is public, and you can open it from the footer or Account > Help > Legal on phone or desktop. It explains what we store, why we store it, and how to send a request.

Yes. Access depends on local law and is available only where local law permits. If a rule blocks a specific action in your location, we keep that action unavailable and show the same policy path.

Send the field name, the current value, and the value you want updated through live chat or the help form. We match it to your registered details before any change is made.

We keep request records only as long as needed to resolve the case, maintain account history, and meet the law that applies to your account. After that, retention follows the same rule set.

No. Cookies keep session and language settings, not your payment balance or card data. DANA, OVO, GoPay, and QRIS appear only in your own transaction record when you choose those rails.

Use the same channel you started with, or send a fresh request from the footer link. Our team keeps the thread attached so you can follow the case without repeating the full history.

What This Policy Means for You

Where Policy Requests Go

Live chat

Help form

Account inbox

How We Handle Requests

Data handling

Cookies

Account security

Retention

Change requests

Contact path

Questions About This Policy

01 Can I read this page before I open an account?

02 Does local law change whether I can use the account?

03 How do I ask for a correction to my data?

04 How long do you keep request records?

05 Do cookies store payment details from DANA or OVO?

06 Who do I contact if I want the record checked again?

Related Pages