Reference

jackwin77 Privacy Policy

The jackwin77 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact support.

Clear data purposesWallet record handlingAccount access controlsCookie choices
jackwin77 jackwin77 Privacy Policy
CONTACT ROUTES

Privacy Help Beside Your Account

A direct account route makes privacy questions easier to resolve. Sign in when you can, include the phone number or receipt reference connected with your request, and avoid sending a password or full wallet credentials. Our support path is available from the account and cashier areas, so you can ask about stored details, a wallet record or an access issue without placing sensitive data in an open message.

Team online

Account privacy request

Use the support link inside your account to ask what personal details are associated with your profile. Include your registered phone number and the exact change you want, while keeping your password and wallet PIN private.

Payment record question

For a DANA, OVO, GoPay or QRIS privacy question, attach only the relevant receipt reference and date. We can trace the payment status without asking you to disclose a wallet PIN, one-time code or complete banking credentials.

Access and deletion contact

If you want to request access, correction or removal of eligible account data, start through the support route beside the cashier. We may ask for account verification before acting, because privacy changes must reach the correct account holder.

DATA CONTROL

What We Do With Your Details

We keep the policy practical by separating account operations from optional device features. Phone verification helps us identify the account holder, while device and sign-in records help detect unusual access.

Account records

We use your account details to create access, complete phone verification and associate requests with the right profile. If you ask us to correct a phone number or other detail, we may require a confirmation step before changing the record.

Wallet references

DANA, OVO, GoPay and QRIS activity can create reference numbers, timestamps and status information in the cashier record. We use those details to investigate a receipt or pending status, while secret wallet credentials remain outside our request.

Cookies and devices

A mobile browser may store a session cookie so your account does not lose its place while you move from login toward the lobby. Browser settings let you clear or restrict cookies, although doing so may require another sign-in.

Security checks

We compare sign-in details and device signals with account activity to identify access that does not look familiar. If a check interrupts entry, use the account support route and provide the requested verification rather than sharing a password.

Retention approach

We keep personal and transaction records only for the period needed for account operation, security checks, dispute handling and applicable legal duties. A retention request should identify the account and record involved so we can assess what may be removed.

Policy changes

When this Privacy Policy changes, we will place the updated wording in the policy area and show the effective date there. You should check this page after a significant account or payment-flow change to understand how new processing is described.

Privacy Policy Answers for Indonesia

These answers address the account and payment questions we expect before registration. They explain the practical route for checking data, changing details and asking for help, without turning the Privacy Policy into a general description of the lobby. If a request involves eligibility, access depends on local law and may require account verification.

It covers account details, phone verification, sign-in and device records, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It explains why we use each category, how we protect it and how you can contact us.

No. Our payment records may include a reference, timestamp and status needed to match a cashier event, but we do not ask you to send a DANA or QRIS PIN. Keep wallet credentials and one-time codes inside the relevant payment service.

Use the support route inside your account and state that you are making a data access request. Add your registered phone number and the categories you want checked. We may verify your identity first so the response is sent to the correct account holder.

Yes, you can ask us to correct eligible account details through the account support path. Describe the current entry and the requested replacement, then complete any phone or account verification we request. We will assess the change against security and legal requirements.

Cookies can preserve a mobile or desktop session and remember selected settings while you move between account pages. You can clear or restrict them in your browser. If cookies are blocked, you may need to sign in again and some account functions may not continue.

Payment references are retained only as long as needed for account operation, receipt matching, security checks, dispute handling and applicable legal duties. The period can vary by record type. Ask support to identify a specific DANA, OVO, GoPay or QRIS reference.

You may submit a removal request through the support route beside the cashier. We will verify the account and assess which records are eligible for removal. Some details may need to remain for security, dispute handling or legal duties where local law permits.