Reference

Privacy Policy for your draw taiwan account

The draw taiwan Privacy Policy gives you a clear account-data path before you open access to the lobby.

Phone verificationWallet recordsDevice securityYour privacy choices
draw taiwan Privacy Policy for your draw taiwan account
CONTACT ROUTES

Get help with a privacy request

A privacy question should not get lost beside a payment question, so we keep the contact route close to your account and cashier area. From your signed-in account, send the request with the phone number linked to your profile and describe the record you want checked. If a wallet status is involved, include the DANA, OVO, GoPay or QRIS reference without sending a password or full security code. We use the details supplied to locate the right account record.

Team online

Account request

Use the privacy contact path shown after account access. Tell us whether you want a copy, correction or deletion request, and include the phone number connected to your draw taiwan profile so we can identify the correct record.

Wallet query

For a payment-related privacy question, provide the transaction reference and name the rail used, such as DANA or QRIS. We can check our record without asking you to reveal a wallet password, card secret or one-time security code.

Access concern

If login or phone verification exposes a possible privacy issue, contact us through the account support route before trying repeated attempts. We may ask for account details that confirm ownership, while keeping sensitive credentials out of the request.

ACCOUNT SAFEGUARDS

Security choices beside your account

We treat the Privacy Policy as an operating process, not a label on the footer. Account access starts with phone verification, and device signals can help us notice unusual sign-in activity or…

Account data

We collect the details needed to create and maintain your account, including your phone number and verification state. The Privacy Policy explains why each category is used, so you can distinguish account access data from optional device or session details.

Device signals

When you sign in on a mobile browser or desktop, technical signals may be recorded to protect the session and investigate unusual access. These signals are handled for security purposes rather than treated as a replacement for your account details.

Cookies

Cookies can keep a requested session working and help remember selected settings. You can manage browser controls on your device, though removing necessary cookies may affect sign-in, phone verification or the path back to your account.

Payment references

We may retain a transaction reference, amount status and chosen rail when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to match status and resolve a cashier question without storing wallet secrets.

Retention

Records remain only for the periods explained in the current Privacy Policy, including any time needed for account security, dispute handling or a legal requirement. When you ask about deletion, we check which records can be removed and which must remain.

Policy changes

If our data practices change, we update this page and identify the revised wording. Check the Privacy Policy before a new account step or payment request, and contact us through the account route if a change is unclear.

Privacy Policy answers for Indonesia

These Privacy Policy answers address the searches we expect before an Indonesian account is opened. They cover the records created during verification, wallet status checks, device access and requests to see or change personal data. If your question is not listed, use the contact path inside your account and give us enough detail to locate the relevant record without sharing a password or security code.

It covers account details, phone verification, device and session data, cookies, payment references, retention and privacy requests. It also explains when information may be shared for security or legal reasons. Access eligibility depends on local law, including the Indonesian route where local law permits.

Phone verification helps connect an account to the person requesting access and reduces confusion when a login stalls. We record the verification result and related account details for access and security purposes. Do not send your one-time code through a privacy contact request.

Yes. The policy covers transaction references and status information connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. Wallet providers and banks keep their own records under their terms; we do not request your wallet password.

You can submit a copy request through the privacy contact path shown after account access. Include the phone number linked to your profile and describe the data category you need. We may ask for reasonable account confirmation before releasing information connected with your account.

Send the request through your account support route and state whether you need a correction or deletion. Tell us which detail is affected and provide the linked phone number. We assess the request against the current Privacy Policy and any record-keeping duty that applies.

Retention depends on the category and the reason it was collected. Account, security and payment references may need to remain for the periods described in the Privacy Policy, including dispute or legal handling. We explain the applicable period when responding to a specific request.

Stop sharing credentials and contact us through the account support path with a short description of what happened. Mention the device or sign-in step involved, but omit passwords and one-time codes. We can then check access records, phone verification activity and related wallet references.