Reference

nota4d Privacy Policy For Your Account

Our Privacy Policy shows how nota4d handles the data connected with your account, device, wallet status and support requests.

Account dataWallet recordsCookie choicesAccess requests
nota4d nota4d Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact path helps you act on this Privacy Policy without guessing which team to reach. Start from the support link attached to your signed-in account and include the email or phone detail used during verification. If you cannot sign in, use the public contact route on nota4d.club and describe the issue without sending a password or wallet PIN.

Team online

Account data request

Use the account support path to ask what personal data is linked to your login. We may request phone verification before discussing records or changing account details.

Wallet record question

For DANA, OVO, GoPay or QRIS status records, share the transaction reference and date through support. We use those details to locate the correct account entry.

Cookie preference help

If cookies behave differently on your phone or desktop browser, tell us the device path and browser setting. We can explain which policy choice affects that session.

DATA PRACTICES

What We Handle And Why

We keep this policy practical by tying each data category to an account action you recognise. Sign-in, phone verification, wallet status and support conversations create different records, so we describe their uses…

Account creation

When you open an account, we use the details you submit to create access and maintain the correct profile. Phone verification helps us connect that account request to you.

Device and cookies

Cookies and device signals can remember a session, language choice or security event. You can manage browser settings, although changing them may affect sign-in or policy access.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a wallet status to the right account record. We use the reference for checking, not for unrelated account activity.

Account security

We may record sign-in time, device path and verification events to detect unusual access. Never send your password, one-time code or wallet PIN through a support message.

Retention approach

We retain each category only while it supports account access, dispute handling, security or a legal requirement. When the reason ends, the record is reviewed for deletion or removal of identifiers.

Changes and contact

You can ask us to correct account data, explain a processing purpose or address a privacy concern. Include your account contact and request type so we can route it accurately.

Privacy Policy Answers For nota4d

These Privacy Policy answers focus on the account actions that usually create questions for an Indonesian customer. They cover what we collect, how wallet records are used, how to request changes and what happens when you browse from a phone. If your situation is not listed, use the support route described above and avoid sending secret credentials.

It covers account details, phone verification, cookies, device signals, support messages and wallet-status records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to the correct person, protect sign-in and respond to account requests. We may use verification events when investigating unusual access.

Yes. The Privacy Policy explains how payment rail, reference, amount status and timing may be used to match a DANA, OVO, GoPay or QRIS record with your account.

Contact support through your signed-in account or the public route on nota4d.club. State the field to correct and use your verified account contact so we can confirm the request.

You can request a description of data linked to your account, including relevant access and wallet records. We may verify your identity before disclosing or changing account data.

Cookies can maintain a session and remember selected settings on your phone browser. If you block them, sign-in or policy access may require extra steps on that device.

Retention depends on the record’s purpose, such as account access, security, dispute handling or a legal requirement. The Privacy Policy explains that records are reviewed when that purpose ends.