Reference

Open yk1 Privacy Policy Before Account Access

yk1 Privacy Policy gives you a clear account-data path before you open an account: what we collect for phone verification, why wallet records matter, how cookies work on…

Account dataCookie choicesWallet recordsAccess requests

Explore Our Lobby Read FAQ

Check How Wallet Data Is Used

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

Our Privacy Policy explains the records needed to create and secure your account, including your contact details, phone verification result, login activity, device signals and payment status. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain transaction references and

1
receipt details so we can match a payment to your account and resolve a status question. We use this material for account access, fraud checks, support requests, legal duties and service security. We do not ask you to send a wallet PIN through support. Access to
2
yk1 and the handling of a request depends on local law. The policy applies to our website, account pages and mobile browser sessions, including visits from Jakarta. Read the full wording before opening an account, and contact our support path if a section does not match
3
your question.

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

REQUEST SUPPORT

Ask About Your Privacy Request Path

A privacy question should not require guesswork. Open the support link from your account area and include the email or phone detail attached to your profile, the subject of your request and any relevant receipt reference. We use those details to locate the correct record without asking for a wallet PIN. The same path helps when login access or payment status prevents you from reaching your account settings.

Team online

Account request

Use the support link inside your account to ask what personal records we hold, why a phone verification detail is needed, or how to correct an account field.

Wallet record

For DANA, OVO, GoPay or QRIS questions, provide the payment reference and date shown on your receipt; we can check the account match without requesting your wallet credentials.

Access concern

If a mobile login, cookie choice or account check blocks access, describe the device path and screen message through support so we can separate an access issue from a privacy request.

DATA PRACTICES

See How yk1 Protects Account Records

Privacy depends on practical handling, not vague promises. We limit account records to purposes described in the Privacy Policy, use access checks before discussing profile details and keep transaction references tied to…

Collection

We collect account details, phone verification results, login events, device signals and payment references when those records are needed to provide access or answer a support request.

Cookie use

Session cookies can keep your account path active between pages on mobile or desktop. Browser controls let you clear or restrict them, though a fresh login may be required.

Account security

Before discussing profile or wallet records, we may ask for an account identifier and verification detail. Never send a DANA, OVO, GoPay or bank PIN through support.

Retention

We keep records for the period needed for account security, payment matching, support history and legal duties. Retention can vary by record type and local requirements.

Policy changes

If our Privacy Policy changes, the updated wording will appear on this policy page. Check the page before using your account when a new notice is displayed.

Your request

You can ask to access, correct or remove eligible personal records through the account support path. Include a clear request and enough detail for us to locate it.

Browse yk1 Privacy Policy Questions

These Privacy Policy answers cover the searches we hear most often before account opening: collected details, wallet references, cookies, correction requests and access questions. We keep the route practical so you know which account step to take and what to include when contacting support. Where eligibility or access applies, it depends on local law.

The yk1 Privacy Policy covers account details, phone verification, login activity, device signals, cookies, payment references, retention, security and requests to access or correct eligible records.

We use phone verification to help confirm account access, reduce mistaken account matches and support security checks. We do not need your wallet PIN or banking password for this step.

Yes. It explains how DANA, OVO, GoPay and QRIS references, receipt details and payment status may be used to match a transaction with your account.

Open the support link from your account and ask for access to your eligible records. Include your account email or phone detail so we can complete the correct verification.

Yes. Send a correction request through support with the account field that needs changing and the accurate replacement detail. We may verify ownership before making an update.

Cookies can remember a session and browser choice on mobile or desktop. You can restrict them in your browser, but clearing cookies may sign you out or require another account check.

Retention depends on the record, account security needs, payment matching, support history and legal duties. The applicable period can vary, and you can ask support about an eligible request.

Open yk1 Privacy Policy Before Account Access

Ask About Your Privacy Request Path

Account request

Wallet record

Access concern

See How yk1 Protects Account Records

Collection

Cookie use

Account security

Retention

Policy changes

Your request

Browse yk1 Privacy Policy Questions

01 What does the yk1 Privacy Policy cover?

02 Why does yk1 need phone verification data?

03 Does the Privacy Policy cover DANA and QRIS payments?

04 How can I request a copy of my yk1 account data?

05 Can I ask yk1 to correct my personal data?

06 How do cookies affect my Privacy Policy choices?

07 How long does yk1 keep payment and account records?

Related Pages