Reference

fitri4d Privacy Policy, Clearly Explained

Our fitri4d Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
Browse Our Lobby Read FAQ
fitri4d fitri4d Privacy Policy, Clearly Explained
HELP WITH PRIVACY

Where To Send A Privacy Request

A clear request path helps us respond without exposing your account to the wrong person. Start from the account support area and describe whether you need a copy, correction, deletion request or…

Account support Open the support path beside your account settings and identify the email or phone detail connected to your profile. We use that step to confirm the request belongs to you before discussing stored data.
Wallet status For a DANA, OVO, GoPay or QRIS record, share the visible reference, date and status from your account. We can then separate a privacy question from a payment-status question without requesting secret credentials.
Policy changes Ask us to correct a detail, explain a cookie choice or stop a permitted data use through the same support route. We record the request, check account ownership and reply with the next step.
HANDLING YOUR DATA

How fitri4d Applies This Privacy Policy

Privacy work is tied to real account actions rather than a separate page that sits unused. We check identity before releasing account details, separate wallet references from secret credentials, and use device…

Account details

We collect the phone or contact detail you enter for account access and use it to connect verification, sign-in events and support requests. Please keep it current so a privacy response reaches the right account holder.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference, amount status and time. We use these fields to reconcile activity, not to request your wallet password or security code.

Device signals

Browser type, operating system, connection details and login timing can be recorded when you access the mobile lobby. These signals help us examine unusual sessions without treating them as your account password.

Cookies

Cookies and local storage can keep sign-in flow, language choices and page preferences available between visits. You can adjust browser controls, although removing some storage may require another account verification step.

Retention

We keep a record only while its account, payment, security, dispute or legal purpose remains active. When that purpose ends, we remove it or separate identifying details under our internal retention process.

Security requests

To ask for access, correction, deletion or a use explanation, contact support from the account path. We may ask for matching account details before changing or disclosing personal data.

Privacy Policy Questions Before Account Access

These answers address the Privacy Policy questions you may have before creating an account or checking a wallet record. We keep the examples close to the actual account path, including phone verification, mobile sign-in, cookies and local payment references. If your situation is not listed, use the support route described above and include only the details needed to locate your request.

The fitri4d Privacy Policy covers contact details, verification records, sign-in events, device signals, support messages and payment references connected to your account. We use them for access, security, reconciliation and policy requests.

Phone verification connects the person opening an account with the contact detail supplied during registration. It also helps us confirm ownership before discussing personal data or changing account records through support.

Yes. The Privacy Policy covers references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match account activity and investigate unclear statuses.

We may record browser type, operating system, connection details and login timing when you use a phone or desktop. These signals help us assess unusual access and maintain the account session.

Use the account support path and state whether you want access, correction, deletion or an explanation of use. Include the contact detail linked to your account, but do not send a password or security code.

Retention depends on the reason for collection, such as account access, payment reconciliation, security, disputes or legal needs. When that reason ends, we remove the record or separate identifying details.

You can adjust cookie or local-storage choices through your browser and any available account setting. Removing storage may affect sign-in continuity and can lead to another phone verification step.

Related Pages

fitri4d Indonesia About Us Access guide Tennis Betting Account information