Reference

Privacy Policy for Your manet4d Account

manet4d Privacy Policy shows what account, device and wallet details we collect when you open access from Indonesia.

Account clarityWallet recordsCookie choicesRequest access
manet4d Privacy Policy for Your manet4d Account
REQUEST ROUTES

Ask About Privacy From Your Account

A clear request path matters when you want to see, correct or remove personal data. Start from your signed-in account and describe the Privacy Policy question in plain English, including the email…

Data access request Ask us for the personal data connected with your account, including account fields, login records and wallet references. We may ask you to complete the account verification step before sending a copy, so the request does not expose your details to another person.
Correction request If your phone, email or account detail is wrong, send the change through the signed-in support path. Include the old and new value, then complete any identity check we request before we amend the record used for account access.
Wallet record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, tell us which record looks incorrect. We use the transaction reference and your account step to check status without requesting your wallet password or private security code.
DATA PRACTICES

What Our Privacy Process Covers

Privacy work reaches beyond a single form: it includes how we handle device sessions, cookies, account checks and stored payment references.

Collected details

We may receive account contact details, verification responses, device identifiers, session timestamps and references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We collect these categories when they are needed for access checks, account support or record matching.

Cookie controls

Cookies and similar browser storage help keep a signed-in session connected to the right account and remember selected settings. You can clear them in your browser, though doing so may require you to complete the account access step again.

Account protection

We use phone verification before account access and may compare a new device or unusual login with existing security details. Never send us a wallet password or security code; our Privacy Policy does not require either item in a support request.

Retention timing

We retain account and transaction records for the period needed to operate access, resolve a dispute, protect accounts or meet a legal duty. When a record is no longer needed, our process removes it or changes it so it no longer identifies you.

Data sharing

We disclose data only when needed for an account service, a security check, a payment record investigation or a legal request. A DANA or QRIS reference is used for matching the relevant event, not as permission to inspect unrelated wallet activity.

Change requests

To request access, correction or deletion, contact us from the signed-in account path and identify the record in question. We may verify account ownership first, explain any local-law restriction, and confirm what action was taken on your request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the data connected with a manet4d account, how wallet references and device activity are handled, and where to send a request. If your case involves a specific DANA, QRIS or login record, use the signed-in support route so we can check the correct entry.

It covers account details, phone verification, device and session records, cookies, support messages and references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access requests, corrections, deletion and restrictions that depend on local law.

Phone verification helps connect an account request to the person making it and helps us respond to data requests safely. We may repeat an ownership check before changing account details or releasing records. Do not send a wallet password or private security code.

Yes. The policy includes references needed to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity with the correct account event. We use those references for status checks, support and reconciliation, rather than collecting unrelated wallet details.

Sign in to the account connected with the request and use the support path to ask for your records. State the email or phone detail attached to the account and identify any relevant wallet reference. We may verify ownership before preparing a response.

You can ask us to correct inaccurate account details or request deletion through the signed-in support route. We first check ownership and explain whether a record must remain for account safety, dispute handling or a legal duty. The result depends on local law.

It describes device identifiers, browser storage, session times and login signals used to connect activity with your account and identify unusual access. A phone can open the lobby through its browser, while clearing cookies may require phone verification again at the next sign-in.

Use the account support path and label your message as a Privacy Policy request. Include the account contact detail and, when relevant, a DANA, OVO, GoPay, QRIS or bank reference. We will use the details supplied to locate the record and explain the next step.