Reference

sirkus4d Privacy Policy for Your Account

sirkus4d explains how we collect, use, protect and retain the details connected with your account, device and wallet activity.

Account dataDevice activityWallet referencesCookie choices
sirkus4d sirkus4d Privacy Policy for Your Account
CONTACT PATHS

Help With Privacy Questions

A clear contact path helps when you need to understand a data entry, correct an account detail or ask why a wallet reference appears in your record.

Account data request Ask us to explain the account details connected with your phone verification or login record. Include the relevant date and phone number so we can locate the correct account without requesting your password.
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, provide the receipt date and reference shown in your account. We can check the payment status without asking for your wallet PIN.
Access correction For a wrong name, phone detail, device record or cookie choice, tell us which entry needs attention. We may verify account ownership before changing or discussing personal data.
HANDLING DETAILS

How We Handle Your Data

Our privacy process follows the account actions you take rather than treating every visit alike. A phone verification, mobile login, lobby search and payment-status check can create different records, each used for…

Account data

When you open an account, we use the details needed to create access and complete phone verification. A correct phone number helps us match your request with the right account when you ask for a data change.

Device sessions

A mobile or desktop session may record sign-in time, browser or device signals and pages opened, including a lobby search for Fish Hunter. These signals help identify unusual access and protect your account.

Cookies

Cookies can keep your session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookie controls through your browser, although some account functions may then need another sign-in.

Payment references

We may retain a rail name, amount reference, receipt detail and status for DANA, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN to check whether a receipt matches.

Retention period

We retain account, security and transaction records only for the period needed for account operation, dispute checks, fraud prevention or legal requirements. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to access, correct or clarify personal data linked to your account. Send the specific field or record concerned; we may first confirm ownership before supplying details or applying a change.

Privacy Policy Questions for sirkus4d

These answers address the searches we hear most often about the sirkus4d Privacy Policy. They explain what may be collected during account access, how payment references are handled, and what you can request when a record needs clarification. If your question is account-specific, use the privacy contact path above and avoid sending secret credentials.

The Privacy Policy covers account creation, phone verification, device sessions, cookies, lobby activity, payment references and requests to access or correct personal data. It applies where access depends on local law.

We may collect the details needed for account creation, phone verification, sign-in security and payment-status checks. Device signals and session times can also be recorded to help protect account access.

Yes. The Privacy Policy explains how we handle payment references for DANA, OVO, GoPay, QRIS, virtual account and bank transfer, including receipt details and transaction status used for account support.

Send a privacy request that names the account field or record you want to access or correct. We may confirm ownership using your account phone detail before discussing or changing personal data.

Do not send a wallet PIN or password in a privacy request. Our payment checks use references, receipt details and status data rather than asking you to disclose secret credentials.

We keep records for the period needed for account operation, security checks, transaction questions, dispute handling or legal requirements. Records no longer needed are removed or de-identified through our process.

Yes. You can ask which cookie or mobile-session detail concerns you and request clarification. Browser cookie controls can limit storage, though some account functions may require another sign-in.