Reference

permatawin Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a permatawin account, verify your phone, browse on mobile or use DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesPolicy requests

Explore Our Lobby Read FAQ

How DANA And QRIS Records Are Used

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

This Privacy Policy covers details you provide during account opening, including your contact details and phone verification status. We also record sign-in events, browser or device signals, selected lobby pages and wallet activity needed to match a transaction with your account. A DANA, OVO, GoPay or

1
QRIS reference can help us trace a payment status without treating the wallet name as your full identity. Bank transfer and virtual account references may be retained for reconciliation and account support. Cookies can remember session settings and help us detect unusual access; you can manage
2
them through your browser controls. We keep records for as long as needed for account operation, dispute handling and applicable legal duties, then remove or anonymise them when practical. Requests to access, correct or delete eligible data can be sent through the account help route. Service
3
availability and eligibility depend on local law, and this policy applies to access where local law permits.

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

CONTACT PATHS

Where To Ask About Your Privacy Policy

A clear contact route matters when you want to check or change account data.

SECURITY PRACTICE

How We Handle Account Data On Mobile

We keep this Privacy Policy practical by linking each data category to an account action.

Phone verification

Before account access is completed, we use the phone verification step to associate the account with the contact detail supplied during opening. This reduces confusion when you request a data change.

Device signals

Browser type, device signals and sign-in time can be recorded to identify unusual account access. These signals are used for account protection and are not a substitute for your identity details.

Cookie control

Cookies can retain session preferences on a mobile browser or desktop browser. You can clear or restrict them in browser settings, although some account steps may need to load again.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status with the correct account. We do not need the wallet label to describe your full profile.

Retention requests

You can ask why a particular account record is retained, request correction or ask whether removal is available. We assess the request against account support needs and applicable legal duties.

Request identity

For privacy changes, we may ask you to confirm account details before releasing or editing data. This step protects your record when a request arrives through the support path.

Privacy Policy Questions About Your Account

These answers address the Privacy Policy searches we hear most often, including payment records, mobile cookies, account access and requests to change stored data. If your situation is not covered, use the account help route and describe the exact record or device step involved.

It covers account details, phone verification, sign-in and device signals, cookies, selected account activity, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification connects the account to the contact detail supplied during opening. It also helps us confirm that a privacy request, correction or access question comes from the account holder.

Yes. Cookies may remember a session or browser setting on your mobile device. You can restrict or clear them through browser controls, though an account step may need to load again.

We use DANA and QRIS references to match payment status with the relevant account and support request. The same approach can apply to OVO, GoPay, bank transfer and virtual account references.

You can request a correction through the account help path. State which detail is wrong, such as a contact record or payment reference, and confirm the account step so we can locate it.

Send a removal request through support with the account detail involved. We assess whether removal is available because some records may be needed for account operation, disputes or legal duties.

Yes. Some rights, retention duties and account access conditions depend on local law. We handle requests where local law permits and explain any restriction through the account help route.

permatawin Privacy Policy for Your Account

Where To Ask About Your Privacy Policy

How We Handle Account Data On Mobile

Phone verification

Device signals

Cookie control

Payment references

Retention requests

Request identity

Privacy Policy Questions About Your Account

01 What does the permatawin Privacy Policy cover?

02 Why does permatawin need my phone verification detail?

03 Does the Privacy Policy mention mobile browser cookies?

04 How are DANA and QRIS records handled under this policy?

05 Can I ask permatawin to correct my account data?

06 How do I request removal of data under the Privacy Policy?

07 Does access to privacy requests depend on local law?

Related Pages