Reference

name303 Privacy Policy For Your Account

The name303 Privacy Policy explains how we collect, use and protect details connected with your account, mobile access and local wallet activity.

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

Get Privacy Help Beside Account Support

A clear contact route matters when your name, phone number or wallet reference needs attention. We direct privacy questions through the account support path connected with your name303 account, so we can identify the correct record without asking you to post personal details in a public message. You can ask about access, correction, deletion, cookie choices or the reason a security check was applied. If a DANA, OVO, GoPay or QRIS reference appears in your request, include only the relevant reference and leave out passwords or one-time codes.

Team online

Account privacy request

Use the account support path to ask what personal data we hold for your name303 account. We may ask you to confirm your phone number or another account detail before discussing the record, which helps prevent another person from receiving private account information.

Wallet record question

When your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, send the payment reference shown in your account rather than a password or one-time code. We use that narrow reference to locate the relevant activity and answer the privacy question.

Security access concern

If you see an unfamiliar sign-in or cannot reach your account after phone verification, contact us through the same account support route. Tell us the device path, such as mobile browser or desktop, and we can separate an access issue from a personal-data request.

DATA PRACTICES

What We Do With Your Personal Data

We handle privacy as an account process rather than a broad promise. Each request is tied to the data involved, the device path used and the reason access is needed.

Account details

We may collect details needed to create and maintain your account, including your contact information and phone-verification status. We use these details to connect your sign-in with the correct account and to respond when you ask for a copy, correction or explanation of related data.

Payment references

DANA, OVO, GoPay and QRIS activity can create references linked to your account, while bank transfer and virtual account records may identify a deposit or account check. We use those references for reconciliation, security and your privacy questions, not as a reason to collect unrelated wallet content.

Cookies and browser use

Cookies or similar browser storage can help remember a sign-in state, protect an account session and retain a setting you choose. When you move between a mobile browser and desktop, some preferences may need to be set again. You can ask us about the cookie categories used.

Account security

Phone verification before account access helps us check that the person requesting entry is connected with the account record. We also review unusual sign-in details, device paths and session activity. Never send us your password or one-time code when requesting privacy assistance.

Retention decisions

We retain personal data only for as long as it supports the stated account, security, payment-record or legal purpose, subject to local requirements. When a retention reason ends, we assess whether the record can be deleted, anonymised or kept in a restricted form.

Changes and requests

You can contact us to request access, correction, deletion, restriction or clarification about your personal data. We may verify your identity before making a change, and some records may remain where local law permits or requires security and payment-account records to be preserved.

Privacy Policy Answers For name303

These Privacy Policy answers address the account questions we expect you to have before opening or using name303 from Indonesia. They explain the practical route for data access, wallet references, cookies, device changes and account security. If your situation is not covered, use the account support path and describe the specific record you want us to check.

The name303 Privacy Policy covers account details, phone verification, browser cookies, sign-in security, payment references and privacy requests. It applies when you use the website from Indonesia, including mobile-browser and desktop access. Account eligibility depends on local law and applies where local law permits access.

We use phone-verification details to connect an account request with the correct person and reduce unauthorised access. The status can also help us investigate a locked sign-in. We do not need your password or one-time code to review a Privacy Policy request.

Payment activity can create account-linked references when you use DANA, OVO, GoPay or QRIS. We use those references to reconcile account activity, protect access and answer your request about stored data. Send only the relevant reference when contacting us, never your wallet password.

Yes. Use the account support path and state whether you want access to a record, correction of a detail, deletion or clarification. We may verify your identity before responding. Some security or payment records may remain where local law permits or requires retention.

Yes. The Privacy Policy covers cookies and similar browser storage used for session continuity, account security and selected settings. A mobile browser may store or clear these items differently from desktop access. Contact us if you want the cookie categories or purpose explained.

Contact us through the account support route and mention the device path, approximate sign-in time and whether you used mobile browser or desktop. Do not include a password or one-time code. We can review the security event and explain which account data is involved.

We assess deletion requests against the purpose for holding each record. Data no longer needed may be removed or anonymised, while security, payment or legal records may need restricted retention where local law permits. We explain the outcome through the account support path.