Reference

pengeluaran bullseye Privacy Policy

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or check DANA and QRIS payment status.

Account dataWallet recordsCookie choicesSupport requests
pengeluaranbullseye.club page image
HELP WITH YOUR DATA

Contact Routes for Privacy Questions

A clear contact path matters when a wallet record or sign-in detail looks unfamiliar. Start from your account help route and describe the Privacy Policy question in plain English, including the relevant date or transaction reference. If you are in Medan or elsewhere in Indonesia, we use the same request process for access, correction, deletion, and cookie questions.

Team online

Account access

If you cannot reach your account, tell our support team which sign-in step stopped and the device path you used. We may ask for account details before discussing personal records.

Wallet records

For a DANA, OVO, GoPay, or QRIS record, send the payment reference and date through the account help route. We use those details to locate the correct entry.

Privacy requests

Ask for a copy, correction, or deletion review through support. We confirm the request belongs to you before changing account data or sharing records connected with your account.

OUR DATA PRACTICES

What We Do With Account Records

We keep this policy practical by linking each data practice to a real account step. A sign-in check, wallet reference, cookie choice, or support request has a defined purpose, and we do…

Collection

When you open an account, we collect contact and verification details needed to create access. During sign-in, we may record device and session signals to identify unusual attempts.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records help us match a payment status. We use the reference and result rather than requesting your wallet password.

Cookies

Cookies keep your session active, remember selected security settings, and help us measure visits to the Privacy Policy. You can manage browser cookie controls, though some account steps may then need repeating.

Account security

We use sign-in checks, verification steps, session controls, and restricted staff access to reduce unauthorised handling. Never send a password or wallet PIN when contacting us about personal data.

Retention

We retain records for account operation, payment matching, dispute handling, security checks, or legal duties. When a purpose ends, we remove, anonymise, or securely restrict the record.

Changing details

To correct a name, contact detail, or account record, contact support from the account help route. We may request verification before applying a change to protect your account.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a data request is sent. They explain the records connected with payment references, mobile access, cookies, account verification, and contact steps for Indonesian customers.

It covers account details, sign-in and device records, cookies, payment references, support messages, retention, security controls, and requests to access, correct, or delete personal data.

No. We may receive a DANA or QRIS transaction reference and status to match payment activity, but your wallet password and PIN remain with the payment provider.

Use the account help route and ask for a personal data copy. Include your account contact detail and the records you want. We verify your identity before sending account-linked data.

Yes. Send a correction request through support with the affected field and the accurate replacement. We may ask for an account verification step before changing contact or identity details.

We keep records while needed for account operation, payment matching, security, disputes, or legal duties. After that purpose ends, we remove, anonymise, or restrict the relevant records.

Cookies can keep a mobile browser session active and remember security choices. If you block them, the lobby or account path may ask you to sign in or confirm settings again.

Contact support from the account help route with the date, record type, and any payment reference. Do not send a password or wallet PIN. Access depends on local law and identity checks.