Reference

jasa61 Privacy Policy for Your Account

The jasa61 Privacy Policy explains how we collect, use and protect details linked to your account, wallet activity and device access.

Account dataWallet recordsDevice accessCookie choices
jasa61 jasa61 Privacy Policy for Your Account
CONTACT ROUTES

Choose a Clear Privacy Contact Route

Privacy questions should reach the team that can locate the relevant account record. Start with the support route inside your account help area and include your registered phone number, request type and any payment reference. We use those details to avoid sending account data to the wrong person. If access is unavailable, use the policy contact path shown on jasa61 and state that your request concerns the Privacy Policy.

Team online

Account access

If you cannot sign in, tell us the registered phone number and the device path you used. We can explain the verification step without disclosing account details before identity checks are complete.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date. We compare the receipt with the account record, then explain what data was used to check its status.

Policy requests

To request access, correction or deletion, name the specific record and preferred contact route. We may ask for account verification before changing or releasing personal data connected with jasa61.

DATA PRACTICE

Explore How We Handle Account Data

We keep this policy tied to actions you can recognise: opening an account, confirming a phone number, using a wallet or returning from a mobile browser.

What we collect

We may collect your name or contact detail supplied during account setup, phone verification events, login history, device type, browser…

Why we use it

We use account and device records to sign you in, detect unusual access, match a wallet reference and answer a…

Cookies and browsers

Cookies can keep a session active and remember basic settings on your mobile browser.

Account security

Phone verification helps connect access to the correct account.

Retention period

We keep records for as long as needed to provide account support, resolve payment questions, protect access and meet applicable…

Your changes

You can ask us to correct an inaccurate contact detail, explain a data use, provide eligible account records or remove…

Browse Privacy Policy Answers for jasa61

These answers address the searches we receive about the jasa61 Privacy Policy, from phone verification to wallet receipts and mobile browser cookies. If your question concerns a record not listed here, use the policy contact route and describe the account step involved. We will check the request under applicable law and confirm what can be done.

It covers account setup, phone verification, sign-in events, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access with the correct contact detail and reduce mistaken access. If a request changes account data, we may repeat verification before taking action.

Yes. The Privacy Policy explains cookies and browser signals used during mobile access, including session support and security checks. You can clear cookies in your browser, but sign-in checks may return.

We use DANA and QRIS references to match a payment status with your account, investigate a receipt question and answer support requests. The record may include its reference, amount, status and time.

You can ask for eligible account records or correction of an inaccurate detail through the policy contact route. Include your registered phone number and request type; we verify the account before responding.

We retain account, security and payment records only while needed for account support, access protection, payment questions and applicable legal duties. Some records may remain longer when a legal obligation requires it.

Use the support route inside account help, or the policy contact path shown on jasa61 if you cannot sign in. Include the relevant account step, such as login, phone verification or wallet status.