Reference

Open our note666 Privacy Policy

Our Privacy Policy explains what account, device and wallet details we collect when you use note666, why each detail is needed, and how you can ask us to…

Account dataWallet recordsCookie choicesRequest access
note666 Open our note666 Privacy Policy
REQUEST PATH

Contact us about Privacy Policy requests

A clear contact route helps when you want to ask about your Privacy Policy rights, an account record or a wallet reference.

Access request Ask us for the account details connected with your note666 profile, such as phone…
Correction request If your contact detail or account record is incorrect, tell us which field needs…
Privacy concern For a question about cookies, device signals, wallet status or a suspected account access…
DATA PRACTICE

Protect account data through clear controls

We keep the Privacy Policy practical by linking each data use to an account action: opening access, checking a phone, matching DANA or bank transfer status, or answering a support request.

Data collected

We may receive contact details, account credentials in protected form, phone verification results, device identifiers, sign-in events and transaction references. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use the reference needed to match status and investigate a support request.

Cookie controls

Cookies can keep a session connected, remember a selected setting and help us detect abnormal access. Your browser can restrict or clear them, although some account steps may then need to be repeated. Our Privacy Policy explains why a cookie is used before it supports that function.

Account security

Phone verification and sign-in checks help us distinguish your account activity from an unfamiliar device. Never send a password or wallet PIN through a support request. If access looks unusual, tell us through the site contact path so we can examine the relevant event.

Retention periods

We retain records only for the period needed for the stated account, payment, security or legal purpose. A wallet reference may remain after a session ends because it can support reconciliation. Ask us which category applies to your record and why continued retention is required.

Your requests

You may ask for access, correction, deletion, restriction or an explanation of certain processing, subject to identity checks and applicable law. Include the account contact detail and a precise request. Where local law permits, we will explain any reason a request cannot be completed.

Contact ownership

Our support contact path is the starting point for Privacy Policy questions, including data linked to a mobile login or payment status. We may request verification before discussing your record. This protects you in the same way as the account step that confirms phone ownership.

Find Privacy Policy answers for note666

These Privacy Policy answers address the questions we expect before an Indonesian account is opened. They cover the records created by login, phone verification, cookies and local wallet activity, as well as the route for asking us to act. If your case involves a specific transaction or device, include that context in your request so we can check the correct account record.

It covers account and contact details, phone verification, sign-in activity, device signals, cookies, payment references and support records. It also explains our purposes, retention approach, security steps and your request rights. The policy applies to supported Indonesia access where local law permits.

Yes. The Privacy Policy covers transaction references and status records connected with DANA, OVO, GoPay and QRIS. We use them to match a wallet event to your account, investigate a payment question and respond to support. We do not need your wallet PIN for these checks.

We may collect your contact detail, phone verification result, protected login record, device signals, sign-in events and payment references. The exact fields depend on the account step you complete. We connect each field to access, security, reconciliation, support or a stated legal need.

Yes. Send a correction request through the site support contact path and identify the field that appears wrong. We may verify ownership using your account contact detail before making a change. Where local law permits, we will confirm the action or explain why a limit applies.

Cookies can maintain a session, remember a setting and help identify unusual access. You can clear or restrict them through your browser, but a later login or phone verification step may be required. Our Privacy Policy describes the purpose of cookies used around account access.

There is no single period for every record. We retain a DANA, QRIS, bank transfer or virtual account reference for the account, reconciliation, security or legal purpose that requires it. You can ask us which retention category applies to a particular transaction.

Use the support contact route shown on our site and state that you want an access request. Include the account email or phone detail and the record category, such as device activity or wallet status. We verify ownership first, then respond according to applicable law.