Reference

Privacy Policy for Your w3school Account

w3school Privacy Policy explains what we collect when you open an account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact route
w3school Privacy Policy for Your w3school Account
CONTACT OPTIONS

Three Ways to Ask About Privacy

A clear contact route helps you act on the Privacy Policy instead of searching through account screens.

Support Chat Center Open Support Chat Center from the account help area when you need a Privacy Policy answer about login records, cookies or a data request. We may confirm your account email or phone number before discussing details, while wallet PINs and one-time codes should remain private.
Email request Send a written privacy request through the contact address shown on our site and include the subject, account identifier and action you want. This creates a clear record for correction, access or deletion questions without placing sensitive payment credentials inside the message.
Account help path If a privacy concern appears beside a cashier event, first open your account history and note the reference for DANA, QRIS, bank transfer or virtual account activity. Share only that reference with support so we can locate the relevant record safely.
DATA PRACTICES

How We Handle Policy Requests

Privacy controls work best when they match the way you actually use an account. We separate identity details from ordinary browsing signals where practical, restrict account access through verification checks and use…

Account data

We use details such as your name, phone number, email address and verification state to create and protect your account. When you request a change, we compare the request with the account record and may ask for a confirmation step before editing personal details.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and timestamp in our records. Bank transfer and virtual account events may carry similar settlement details. We use these references to match requests without asking for your wallet PIN.

Cookies

Cookies can keep a session active, remember a selected setting and help us identify unusual device behaviour. On mobile, you can manage cookie permissions through your browser settings; turning some cookies off may require you to verify the account again.

Security checks

We may record browser, device and IP signals to detect unusual login attempts or changes around account access. A phone verification step can be required before we discuss private records, change key details or restore access after a security alert.

Retention periods

We keep personal and transaction records only for as long as needed for the purpose described in the Privacy Policy, account security, dispute handling or applicable legal duties. When a record is no longer needed, our internal process addresses deletion or further restriction.

Your requests

You can ask what personal data we hold, request a correction, ask about processing, or seek deletion where the request is permitted. Contact us through Support Chat Center or the listed email route, and explain which account record your request concerns.

Privacy Policy Questions Answered

These Privacy Policy answers address the searches we hear most often from people considering a w3school account in Indonesia. They explain the data connected with account access, local wallet records, cookies, corrections and contact steps. If your situation involves a specific reference or security alert, include that detail when you contact us. Eligibility and access depend on local law.

It covers account details, verification records, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how long they may be kept and how to contact us.

We use your phone number to create or protect the account, send an account confirmation where required and complete a security check before discussing private records. If you ask us to change it, we may request an additional account step so another person cannot take over access.

Yes. The Privacy Policy covers operational references created when you use QRIS, DANA, OVO or GoPay, including status, timestamp and matching details. We use these records to identify a payment request or resolve a status question, but we do not need your wallet PIN in chat.

Contact us through Support Chat Center or the privacy email route listed on the site. State that you want an access request, add the account email or phone number and describe the records involved. We may verify your identity before releasing personal details connected with the account.

You can request a correction when an account detail is inaccurate or incomplete. Tell us which field needs attention and provide the account identifier used for verification. We will assess the request against security and legal requirements, then update or explain the result through the contact route.

Open your phone browser settings, find the site privacy or cookie controls and adjust permission for w3school.asia. Some account functions may then ask you to sign in or verify again. Our Privacy Policy describes the purposes of cookies, while your browser provides the device-level control.

You may ask about deletion through Support Chat Center or the listed email address. We assess which records can be removed and which must remain for account security, dispute handling or legal duties. The response will explain any restriction, and access remains subject to local law.