Reference

maniatoto Privacy Policy Explained

maniatoto Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support chat.

Account recordsWallet checksCookie choicesPrivacy requests
maniatoto maniatoto Privacy Policy Explained
PRIVACY HELP DESK

Get Help With A Privacy Request

A clear contact path helps you handle a privacy question without sending sensitive details into the wrong channel.

Policy request Start in the on-site support chat and state whether you want access, correction, deletion…
Wallet reference For a DANA, OVO, GoPay, or QRIS question, share the transaction reference rather than…
Account security If you see an unfamiliar sign-in or device session, tell us through support chat…
DATA CONTROL POINTS

What We Do With Your Personal Data

Privacy at maniatoto is handled through practical account controls rather than broad promises. We separate identity details from payment status where our systems allow, limit staff access by operational need, and record…

Account creation

When you open an account, we collect the contact and verification details needed to create your profile and confirm account ownership. We do not ask for a wallet password, and you should not place secret credentials in a support message.

Payment references

DANA, OVO, GoPay and QRIS can return a reference, amount, status, and time for matching. Bank transfer and virtual account records may carry similar reconciliation fields. These details help resolve a receipt without exposing your banking sign-in.

Cookies and device data

Cookies can keep a sign-in session working and help us detect unusual device behaviour. Your browser settings let you remove or block cookies, although some account functions may require a session cookie to operate correctly.

Security checks

Before account access or a sensitive change, we may compare sign-in details, device signals, and phone verification status. This step helps stop a person with only a payment reference from reaching your private account records.

Retention choices

We keep personal data only while it supports account operation, security checks, dispute handling, or a legal requirement. When a purpose ends, we delete or anonymise the record where practical, subject to lawful retention needs.

Requesting changes

You can ask us to access, correct, or remove eligible personal data through the on-site support chat. Include your account contact and the request type; we may verify you before sending records or making a change.

Privacy Policy Questions You May Have

These Privacy Policy answers focus on the account and wallet questions that matter before you open an account. We explain what is collected, how access requests work, why a device check may appear, and how local eligibility affects processing. If your question is not covered, use support chat with only the account details needed to locate your record.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, security checks, service providers, and your route for requesting access or correction.

No. Our Privacy Policy distinguishes a wallet transaction reference and status from your private wallet credentials. When a DANA or OVO action is matched, we use the returned reference, amount, and status where supplied. Do not send a wallet password in chat or account fields.

Use the on-site support chat while signed in when possible, identify the account contact, and ask for a data copy or access request. We may complete an ownership check before releasing records. Access depends on local law and may be limited where another person’s data is included.

Yes, you can ask for a correction through support chat and describe the field that is inaccurate. We may ask for phone verification or another account step before changing contact or identity details. Payment references normally remain unchanged because they must match the original transaction record.

Cookies help maintain a signed-in session, while device and browser signals help us identify unusual account access. You can clear or block cookies in your browser, but doing so may interrupt account functions. We use these signals for security and session handling, not as wallet passwords.

We retain records while they are needed for account operation, security investigations, payment reconciliation, dispute handling, or a legal obligation. After that purpose ends, we aim to delete or anonymise them where practical. Some transaction or security records may remain longer when local law permits or requires it.

Open the on-site support chat and provide the account contact plus the QRIS or GoPay transaction reference. Do not share a PIN, password, or full banking login. We can explain the data linked to that reference after confirming that you control the relevant account.