Reference

Open 3utool Privacy Policy With Clarity

3utool Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPhone verification
3utool Open 3utool Privacy Policy With Clarity
CONTACT ROUTES

Ask Support About Privacy Policy

A clear contact route helps when you want to ask about a data record, cookie choice or account detail.

Account help Use the account help path for a Privacy Policy question linked to your profile. Share the relevant account identifier and describe the requested change; we can check whether the request concerns phone verification, device records, wallet status or a support message.
Payment record If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the payment reference and date. We use those details to locate the correct transaction record while avoiding requests for your wallet password or one-time code.
Access question For a request about account access, send the contact detail attached to your profile and explain the issue in plain English. We may need an account step to confirm ownership before discussing personal data or applying a permitted correction.
DATA CONTROLS

Check How We Handle Your Details

Privacy choices work best when each control has a clear purpose. We separate account operation from cookie preferences, keep security checks around phone verification, and use payment references to trace a receipt…

Data collection

We collect details needed for account creation, phone verification, access checks, support handling and payment reconciliation. Device and connection signals can help us identify unusual activity. We do not ask you to place a wallet password or one-time code inside a support message.

Cookie settings

Cookies and similar device storage can remember a session, preserve a selected setting or help us understand account access. Your browser controls can restrict them, although some account functions may not work as intended after those changes.

Account security

Phone verification is an account step before access, and security checks may compare sign-in context with previous activity. Keep your login details private, sign out on shared devices, and contact account help if a device or session looks unfamiliar.

Data retention

We retain records for the period needed to operate the account, resolve disputes, trace payment references and meet applicable legal duties. When a record is no longer needed for those purposes, our processes address deletion, restriction or secure disposal.

Request changes

You can ask us to correct an inaccurate account detail, explain a data use or address a permitted deletion request. Include the contact detail on your profile and the specific record involved; ownership checks may apply before we change it.

Policy updates

When our data practices change, we update this Privacy Policy and identify the relevant section on the page. Check the policy before using a newly changed account or wallet step, especially when access depends on local law.

Browse Privacy Policy Questions

These Privacy Policy answers focus on the account steps you are most likely to check before opening access. We cover collected data, wallet records, cookies, corrections, deletion requests and contact handling, with examples from DANA, QRIS and phone verification. If your situation is different, use account help and describe the exact record or action you want us to examine.

The 3utool Privacy Policy covers account details, phone verification, device and connection signals, cookies, support messages and payment references. It explains why we use those records for account access, security, payment reconciliation and legal duties, where local law permits.

Phone verification helps connect account access to the contact detail you provide and supports security checks when a sign-in looks unusual. We may use the result to protect the profile, but you should never send a verification code through an informal message.

Yes. The Privacy Policy includes operational payment references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. These records can help us match a receipt or check wallet status without requesting your wallet password or one-time code.

You can contact account help with the profile contact detail and identify the field you believe is inaccurate. We may confirm ownership before making a change, then assess the request against account operation, payment records and duties that apply where local law permits.

Send a specific deletion request through the account help path, naming the account detail or record involved. We assess whether removal is permitted because some records may need to remain for security, dispute handling, payment tracing or legal duties.

You can adjust cookie or browser storage controls through your device and browser settings. Some session or account functions may be affected after restriction. The Privacy Policy explains the purposes connected with remembering settings, supporting access and understanding account activity.

Use the account help route and provide the profile contact detail, your request and any relevant payment reference. For DANA or QRIS questions, include the receipt date or reference, but never include a wallet password or one-time code.