Reference

matrice 4d Privacy Policy for Your Account

matrice 4d Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact account support.

Clear data purposesWallet record contextDirect policy contact
matrice 4d matrice 4d Privacy Policy for Your Account
CONTACT WHEN NEEDED

Privacy Policy Help Beside Account Support

Questions about our Privacy Policy should reach the same support route used for account or wallet status concerns. Open the support link beside the cashier path, include your account phone number and describe the data request in plain English. We use those details to locate the right record without asking you to send a wallet password or full payment credentials. If you are in Medan and a QRIS receipt does not match your account, mention the reference and date so we can separate a privacy question from a payment-status check.

Team online

Policy questions

Use the account support link to ask how we collect, use or retain your data. Include the phone number attached to your account and the specific Privacy Policy section you want clarified.

Data requests

Ask us to access, correct or remove eligible account details through the same support route. We may ask for a verification step before discussing records linked to your phone number.

Wallet records

For DANA, OVO, GoPay or QRIS records, send the transaction reference and date rather than a password. We can check the account link and explain which payment details remain stored.

DATA HANDLING DETAILS

Inside Our matrice 4d Privacy Controls

We keep the Privacy Policy practical by connecting each data purpose to an account action. Phone verification helps us confirm account access, while device and sign-in records help identify unusual attempts.

Account creation

We use the phone number and verification details you submit to create and protect your account. A clear verification step comes before account access, and we use the result to handle sign-in requests.

Security signals

Browser type, device identifiers, connection details and sign-in times can help us spot unusual access. These signals support account security and are not a request for your DANA, OVO or GoPay password.

Cookie choices

Cookies or similar browser storage can keep a session active and remember selected settings. You can change browser permissions, but turning storage off may require another verification step when you return.

Game records

When you open titles such as Esports Free Fire or Fishing War Quick Arena, we may record account activity needed for session operation and support. The Privacy Policy explains the purpose rather than treating every title as a separate profile.

Retention checks

We retain account, security and payment references only for the period needed for service operation, dispute handling, fraud checks or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

You can ask us to correct account details, explain a data use, provide eligible access or remove information where permitted. We verify the request first, then tell you what action is possible under local requirements.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the account questions we expect before you open an account or connect a local wallet. They cover data access, payment references, cookies, retention and contact steps without changing the policy terms. If your situation is specific, send the request through account support and include only the details needed to identify your record.

It covers account details, phone verification, sign-in and device signals, cookies, game-session records, payment references and support messages. It also explains why we use each category, how long records may remain and how you can request access or correction where local law permits.

No. Our Privacy Policy describes payment references such as a DANA or QRIS transaction number, date, amount and status. We use those details to match an account event and check a receipt; we do not ask you to send a wallet password.

Phone verification helps us confirm that an account request comes from the person controlling the registered number. It supports sign-in security and account recovery. We may use the verification result with device and session signals when checking an unusual access attempt.

Yes, you can send an access request through the account support link. Tell us which record you need, such as profile details, sign-in history or payment references. We verify your identity first and respond according to applicable requirements and the Privacy Policy.

Send a correction request through support and identify the field that needs changing, such as your phone number or account detail. We may request verification before editing it, and some payment or security records may need to remain for legal or dispute purposes.

You may ask us to remove eligible personal data through the policy contact route. We assess the request against account security, unresolved payment checks, dispute handling and legal duties. If a record must remain, we explain the reason and the applicable handling.

Cookies and browser storage can keep your session settings and help the account path work as intended. If you block them, you may need to repeat sign-in or phone verification. Your browser controls the choice, while our Privacy Policy explains the related data use.