Reference

bullseye Privacy Policy For Your Account

We wrote this page to spell out what happens to your account data, device data, and payment references when you use bullseye.

Account dataDevice logsCookie useSupport requests
bullseye bullseye Privacy Policy For Your Account
REQUEST PATHS

Ways To Reach Our Privacy Team

If you want a copy of your data, a correction, or a question about retention, open our support chat from desktop or mobile, or send an…

Live chat Open chat from the account menu on desktop or mobile.
Email Send the same request from the address on your profile page.
Account form Use the privacy form after login if you want a copy or a deletion…
TRUST LAYERS

How We Handle Your Data

We built the process around three things: minimum collection, access control, and a paper trail when we touch sensitive records.

Cookies

We use cookies to remember language, keep you logged in, and stop repeated prompts on the same browser. You can clear them in Chrome, Safari, or Firefox, but some settings may need to be set again.

Login checks

When you enter the account on Android, iPhone, or desktop, we record IP address, device model, and session time. That helps us spot a login from a device you do not usually use.

Payment references

DANA, OVO, GoPay, and QRIS records stay attached to the transaction trail, not to unrelated browsing. We keep the minimum detail needed to match the payment and answer a support question later.

Retention

We keep data only as long as the purpose or local law requires. Older support tickets and logs are removed or anonymised when they are no longer needed for accounting, dispute handling, or account safety.

Change requests

If you want a copy, correction, or removal check, open chat or email the address on your profile. We confirm the request against your account before we touch the record.

Device signals

We read basic device signals so a new phone, tablet, or browser does not break your session without reason. This also helps us close a stale login when you sign out.

Privacy Questions You Ask Us

These questions cover the data we keep, why cookies matter, what happens after a login from a new device, and how you can ask for changes. If you are in Indonesia and local law allows your request, we answer through the account channel you used to contact us, and we verify the request before any record moves.

We keep the details you enter for login, contact, and request handling, plus basic device signals and session timestamps. If you send a support message, that thread stays with your account record so we can answer it later.

Cookies help us remember language, keep you signed in, and stop repeated prompts when you return on the same browser. If you clear them in Chrome, Safari, or Firefox, some settings may need to be set again.

We keep records only for the period needed to serve the account, settle a dispute, or meet local law. Old logs and tickets are removed or anonymised once they no longer have a purpose.

Yes. Open chat or email the address on your profile, and we will compare the request with your account before we act. Where local law allows, we can correct details or remove data we no longer need.

We keep payment references with the transaction trail, not as a separate profile you can browse. That lets us match the right receipt, handle a dispute, and avoid using payment data for unrelated purposes.

A new phone, tablet, or browser may trigger a fresh device check. We use that signal to protect the account and to close an old session after sign-out, while keeping access working for you.

Use the support chat in the lobby, send email, or submit the privacy form after login. We verify the request against your account first, and we reply in the same thread whenever we can.