Reference

drawsgp Privacy Policy For Your Account

Your drawsgp Privacy Policy explains what we collect when you open an account, sign in from a phone, or check wallet status through DANA and QRIS.

Account dataWallet activityDevice accessPolicy access
drawsgp drawsgp Privacy Policy For Your Account
PRIVACY SUPPORT

Where To Ask About Your Personal Data

A direct support route helps you raise a privacy question without explaining it across several teams. Include the account email or phone detail used for sign-in, the type of request and any relevant date; leave out wallet passwords and full payment credentials. We can then check the correct account record and explain the next step.

Team online

Account access

If your phone verification or sign-in record is unclear, contact our support channel with the account detail you used. We can explain which identity check is needed before discussing account data, without asking you to disclose a password.

Wallet reference

For a privacy question linked to DANA, OVO, GoPay or QRIS, share the date, amount reference and wallet name only. Do not send a wallet PIN. We use the reference to locate the related account event.

Data request

To request a correction, access copy or deletion assessment, state the request clearly and include your sign-in contact. We may ask for an account check so private records are not released to the wrong person.

DATA HANDLING

What We Keep Clear About Privacy

Privacy decisions should be understandable before you use an account, so we describe the handling points that affect your daily access.

Account records

We may hold the contact details and verification results needed to create, protect and restore your account. The account step comes before access to account-linked records, so a request is connected with the correct person rather than a similar sign-in.

Wallet references

A DANA, OVO, GoPay or QRIS transaction reference can appear in our records when you check a wallet status. We use that reference to reconcile an account event, not to request your wallet PIN or full secret credentials.

Device signals

When you sign in from a phone or desktop browser, technical signals such as session time and device type may be recorded. These signals help us identify an unusual access attempt and explain why a verification step appeared.

Cookies

Cookies and similar browser storage can keep a session active, remember a selected setting or help us understand an access error. You can manage browser permissions, though changing them may remove saved session details or require another sign-in.

Retention period

We retain each category only for the period needed for the stated account, security, payment reconciliation or legal purpose. The applicable period can differ by record type, and you may ask support which retention rule applies to your request.

Policy changes

If this Privacy Policy changes, we will publish the revised wording on this page and show the effective date. Reading the current page before opening an account lets you see how the latest terms apply to your details.

Privacy Policy Answers For drawsgp

These Privacy Policy answers focus on the searches people make before opening an account or asking us to change a record. Each answer points you toward a practical account, device or wallet step, so you know what to include when contacting support.

It covers account details, sign-in and phone verification records, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains use, retention, requests and policy changes.

We collect the details needed to create and protect your account, recognise a sign-in session and investigate access problems. A phone or desktop device signal can help us spot an unusual attempt before we discuss account-linked records with you.

Yes. The Privacy Policy covers payment references attached to account activity through DANA, OVO, GoPay, QRIS, bank transfer and virtual account. Send only the date, wallet name and reference when asking us to check a status; never send a PIN.

Contact our support channel and state that you want a data correction. Include the sign-in email or phone detail, the field you believe is wrong and any supporting date. We may complete an account check before changing or discussing the record.

You can ask us to assess a deletion request through support. We review the record type and any continuing account, security, payment reconciliation or legal reason for keeping it, then explain what can be removed and what must remain.

There is no single period for every record. Account, security, wallet reference and legal records can follow different retention rules. Ask support about the category involved, and include your account contact so we can address the correct data set.

The current Privacy Policy is available on this page at drawsgp.bet/privacy-policy/. Check it before opening an account or after a policy notice. Where access or eligibility is discussed, it depends on local law and the current terms shown here.