Rujukan Laman

How qr44 handles your data

This page explains how we collect and use the details you give us when you open an account, contact support, or move money through your wallet.

Account dataCookiesSupport recordsLocal law
qr44 How qr44 handles your data
REQUEST CHANNELS

Where to send privacy requests

If you want to ask about the data tied to your account, our support routes are set up to handle privacy requests without delay.

Account Chat Send a privacy question from inside your account and we can match it to…
Email Request Use email when you want a written trail or need to attach files.
Help Form The form is useful when you need to ask for deletion, restriction, or a…
HANDLING STANDARDS

Security, storage, and access

We keep only the data needed to run your account, confirm requests, and meet legal retention periods.

Data Collection

We record the details you enter at signup, the messages you send, and the device and browser signals that help us keep your account tied to the right person and session.

Cookie Use

Cookies store session state, language choice, and basic site preferences. They also help us spot unusual access and keep the page working properly. You can clear them in your browser, though some settings may not stay saved.

Account Security

We may ask for one-time checks before changing email, wallet details, or withdrawal settings. That step helps us stop the wrong person from editing your record and keeps request handling linked to your account.

Retention

We keep payment logs, dispute history, and support messages only as long as they are needed for service, audit, tax, or other legal duties. Other data is deleted or masked when that purpose ends.

Change Requests

If you want a correction, copy, or deletion request, use the contact route from your account and tell us exactly what should change. We will tell you if law limits the request.

Who to Contact

For privacy questions, send the request through account chat or the help form first. That lets us match the request to the right record and respond with the next step.

Privacy questions from your account

If you are checking how your data is handled, these answers cover the most common requests we receive. They explain what we collect, why cookies appear, how long records stay, and how you can ask for a correction or copy. Where a request depends on local law, we will say so clearly before we act on it, and we may ask you to confirm the account first.

We collect the details you submit, the contact route you use, device and browser signals, and account activity tied to your session. We keep only what we need for service, security, and legal duties.

Cookies remember your login state, language choice, and basic preferences. They also help us notice unusual sign-ins and keep the page stable. You can clear them in your browser, though some settings may reset.

Yes. Send the request from account chat or the help form, and we will confirm your identity before we share what we can. Local law and required retention periods may limit some parts.

We keep records only as long as they are needed for support, dispute handling, tax, accounting, or other legal duties. After that, we delete, archive, or mask them under our standard process.

Yes. If you spot a mistake in contact details or other stored fields, tell us what to change. We may ask for proof first so the right record is updated.

Use account chat for quick questions, email for a written trail, or the help form when you need attachments. We route the request to the team that handles personal data.

Yes. Access, correction, and deletion requests are handled where local law permits. If a request cannot be completed, we explain which rule or retention duty stops the change.