Reference

ford4d Privacy Policy for Your Account

The ford4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse Super Sic Bo or check a wallet status.

Account clarityWallet recordsCookie choicesSecure access

Explore Our Lobby Read FAQ

How Payment Data Enters Our Policy

ford4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

When you create an account, we may record your name or contact detail, verification information, sign-in events, device signals and messages sent to support. A payment record can include the selected rail, amount, reference, status and time; we do not need your wallet password to confirm

1
a DANA, OVO, GoPay or QRIS event. Bank transfer and virtual account records may also be matched to your account so we can investigate a pending status. We use this material for account access, fraud checks, payment reconciliation, support and legal duties where local law permits.
2
If you browse from Jakarta or another Indonesian location, the same policy applies to the data route available for your account. Eligibility depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT OUR TEAM

Privacy Help Beside Your Account Path

You can ask us about a Privacy Policy issue without explaining your whole account history in public. Use the account help route when a sign-in detail, cookie choice or wallet record needs attention. Include the contact detail on your account and a short description of the request; we will use those details to locate the correct record and avoid asking you to repeat private payment data.

Team online

Account help

For a question about the ford4d Privacy Policy, open the account help route and include your registered contact detail. We can then identify the relevant account record without requesting your DANA, OVO or GoPay password.

Payment status

If a QRIS, bank transfer or virtual account reference appears incorrectly, send the reference and approximate time through the cashier support path. We use the payment status record to check the issue rather than asking for unnecessary wallet credentials.

Data request

To request a copy, correction or removal of eligible personal data, describe the change clearly and confirm the account contact detail. We may ask for an account step that helps us verify the request belongs to you.

DATA HANDLING

Six Practical Controls Inside ford4d

Our Privacy Policy is tied to the way your account actually works, from the first phone verification to a return visit on mobile or desktop.

Account records

We collect details needed to create and maintain your account, including contact information, verification events and login activity. If you stop at the phone verification step, we retain only what is needed for the account process and applicable legal duties.

Device signals

A mobile or desktop visit can produce device, browser and session signals used to keep sign-in consistent and identify unusual access. These signals help us connect your return to the correct account without reading unrelated files on your device.

Cookies

Cookies can remember a session, preserve language or keep a page choice available while you move from login to the lobby. You can manage cookie permissions in your browser; changing them may affect account access and saved preferences.

Payment separation

For DANA, OVO, GoPay and QRIS activity, we record the transaction reference and status needed for reconciliation. We do not ask for a wallet password. Bank transfer records may remain linked to the account while a payment question is being checked.

Security steps

Phone verification, sign-in checks and account details help us distinguish your request from an unrelated request. Keep your contact channel private, and tell us promptly if a login event or account detail does not match your activity.

Retention requests

We keep personal data only for the operational, dispute-handling and legal purposes that apply to the record. Ask us to correct, access or remove eligible data through account help; we will explain any record that must remain.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. We keep the wording practical: what is collected, why a payment reference appears, how your mobile session is handled and where to send a request. If a question depends on your location or eligibility, that position depends on local law.

It covers account details, phone verification, login activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your choices and how to request access or correction.

Phone verification helps connect account access to the contact detail you provide and helps us identify a genuine account request. We may use the verification event for sign-in security and support checks, while eligibility and access depend on local law.

No. We use payment references, selected rail, status and timing to reconcile activity, not your wallet password. The same approach applies to GoPay and QRIS records. Never send a wallet password in an account help message.

Cookies can keep your session, language choice and page settings available as you move from login to a mobile lobby. Browser controls let you change cookie permissions. Some account functions may behave differently when required cookies are blocked.

Use the account help path and state whether you want access, correction or removal of eligible data. Include your registered contact detail and the specific record, such as a QRIS reference or device event, so we can verify and route the request.

The retention period depends on why the record exists, such as account access, payment reconciliation, dispute handling, security or a legal duty. We remove or restrict data when the applicable purpose ends, unless local law requires the record to remain.

Yes. Send the request through account help and ask for the privacy contact route. We can explain how the request is handled, what verification is needed and whether a record must remain because of payment checking or a legal requirement.

ford4d Privacy Policy for Your Account

Privacy Help Beside Your Account Path

Account help

Payment status

Data request

Six Practical Controls Inside ford4d

Account records

Device signals

Cookies

Payment separation

Security steps

Retention requests

Privacy Policy Answers for Indonesia

01 What does the ford4d Privacy Policy cover?

02 Why does ford4d need my phone verification?

03 Does the policy store my DANA or OVO password?

04 How are cookies used on my mobile device?

05 How do I request a copy or correction of my data?

06 How long does ford4d keep account information?

07 Can I ask who handles my Privacy Policy request?

Related Pages