Reference

Open yok4d Privacy Policy Before Account Access

yok4d sets out how we handle the account, device and wallet details connected with your access to Live Baccarat Gold and QRIS transactions.

Account dataWallet recordsCookie choicesAccess requests
yok4d Open yok4d Privacy Policy Before Account Access
REQUEST HELP

Reach Us About Privacy Policy Requests

A clear contact route helps you ask what data we hold, why a record appears, or how to correct an account detail. Use the support path connected to your account and describe the request without sending a password or wallet PIN. We may ask for account identifiers and phone verification before discussing personal data. This protects your records while giving you a practical route for questions about the Privacy Policy.

Team online

Account data request

Ask us to locate, access or explain account records linked to your phone verification. Include the account identifier shown after login, but never include your password, wallet PIN or full payment credentials in the message.

Correction request

If your contact detail or account record is inaccurate, tell us which field needs attention and why. We may compare the request with Secure Account Access checks before changing data, so another person cannot alter your profile.

Wallet record query

For a DANA, OVO, GoPay, QRIS or bank transfer reference, send the date, amount shown in your account and reference code. We use those details to trace status without asking you to reveal a wallet password.

DATA CONTROLS

Explore Secure Account Access Data Controls

We treat privacy as an operating task across login, wallet matching and account support rather than as a single page to read once.

Account records

We may hold your registration details, phone verification result, login history and support messages. These records help us identify the correct account when you move from a mobile browser to desktop or ask about Secure Account Access.

Payment references

We store references needed to match DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity with your account. We do not ask support messages to contain your wallet PIN, password or complete banking credentials.

Cookies and devices

Cookies and device signals can keep login steps consistent, remember selected settings and help detect unusual access. You can clear browser cookies through your device settings, although doing so may require phone verification again.

Security checks

We use phone verification, login records and account signals to reduce unauthorised access. If a sign-in or wallet change looks unusual, we may pause the request and ask for account confirmation before discussing related records.

Retention periods

We keep personal data only while it supports account access, payment reconciliation, security review or a required legal purpose. When a record is no longer needed, we remove it, anonymise it or restrict access where appropriate.

Your contact route

You can use the account support path to ask about access, correction, deletion or a processing concern. Tell us the specific record involved; we may verify your identity before releasing data or completing a change.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the points you are most likely to search before opening an account: what we collect, how wallet references are handled, how cookies affect a device and how to request a change. Read the relevant answer first, then use the account support path if your question involves a particular record.

The yok4d Privacy Policy covers account details, phone verification, device signals, cookies, login records, support messages and payment references. It explains why we use each type of data for access, security, reconciliation or legal duties, and how you can ask about a record.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. We use the reference, date and account match to check status; support does not need your wallet PIN or complete banking credentials.

We may collect registration details, phone verification results, login history, device signals and messages you send through support. A payment reference may also be recorded when you check a wallet or transfer status. We use these details for stated account and security purposes.

Use the account support path and describe whether you want access to a record or correction of a specific field. Include your account identifier, not a password or PIN. We may complete phone verification before responding, where local law permits.

Cookies can retain selected settings, support consistent login steps and help identify unusual access. You can clear them in your browser or device settings. After clearing them, the next sign-in may ask for phone verification and selected preferences may reset.

We retain data while it supports account access, payment reconciliation, security checks, support handling or a required legal purpose. Once it is no longer needed, we remove, anonymise or restrict it where appropriate, subject to applicable retention duties.

You can send a deletion request through the account support path and identify the records involved. We will assess the request under applicable rules, explain any data that must remain for legal or transaction purposes, and remove or restrict other records where local law permits.