Reference

filter303 Privacy Policy for Your Account

The filter303 Privacy Policy explains what we collect when you open an account, use the mobile browser lobby, or select DANA and QRIS at the cashier.

Account data clarityWallet record contextCookie choicesPrivacy contact path
filter303 filter303 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Policy Help for Account Access

A clear contact path helps when a privacy request and an account issue arrive together. We ask you to start from the signed-in account area, where your phone verification status and wallet activity can identify the correct record. If you cannot sign in, use the support route linked on the site and include only the details needed to locate your request. We handle privacy questions separately from game or wallet troubleshooting.

Team online

Account privacy request

Open the account support path and state whether you want access, correction or removal of personal data. We may ask for phone verification before discussing account records.

Wallet record question

For DANA, OVO, GoPay or QRIS records, include the transaction reference and date rather than a wallet password. This helps us match the receipt without exposing extra credentials.

Sign-in privacy issue

If a mobile browser session will not open, tell us the device type, approximate time and account phone number through the listed support channel. We use those details for a focused security check.

DATA PRACTICES

How We Handle Your Account Data

We keep the Privacy Policy practical by connecting each data use to an account action: phone verification supports access, payment references support reconciliation, and session records support security checks.

Account details

We collect information such as your phone number and verification state when you create or secure an account. These details help us distinguish your account from another wallet or browser session.

Cookie behaviour

Cookies can keep a signed-in session active, remember selected settings and help us detect repeated access attempts. You can manage browser cookie controls, though some account steps may then require another sign-in.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce references, timestamps and status information. We use those records to trace a request and respond to a data query.

Account security

Phone verification and device-session checks help protect your account from an unfamiliar sign-in. Never send a wallet PIN or password in a privacy request; our process does not require those secrets.

Retention approach

We retain account and transaction records only as needed for the stated service, security checks, dispute handling and applicable legal duties. The policy contact path can explain whether a record remains necessary.

Change requests

Ask us to correct account data or explain its use through the support route. Include your account phone number and request type, then complete any identity check needed before changes are made.

Privacy Policy Questions About Your Data

These Privacy Policy answers cover the searches we hear most often before account creation. You can read the full policy from the site footer or account menu, then contact us when your question concerns a specific phone record, cookie, device session or payment reference.

It covers account details, phone verification, cookies, device sessions, wallet references, support requests, retention and your choices about access or correction. It also explains when local law affects a request.

We use your phone number to create and verify the account, connect you with the correct support record and help protect sign-in activity. Phone verification may be required before account details are discussed.

Yes. The policy covers transaction references, dates and status information connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. Wallet passwords and PINs are not requested.

Use the privacy contact path linked from the account area or site footer. State that you want an access request, provide your account phone number and complete the identity check we specify.

Yes. Send a correction request through the listed support route and identify the inaccurate field without sharing a password. We may verify your phone before changing account or payment-related records.

Cookies can retain a session, remember settings and help identify unusual access. You can adjust browser controls on your phone, but turning cookies off may require repeated sign-in or limit policy-page functions.

Contact us through the support route shown on the site and mention the account phone number, device type and request date. Where local law permits, we will check the record and explain the next step.