Reference

plasa4d Privacy Policy for Your Account

Our plasa4d Privacy Policy sets out how we use account details, phone verification records, wallet activity and cookie data when you open an account or browse from Indonesia.

Account clarityWallet recordsCookie choicesPhone verificationLocal-law access
plasa4d plasa4d Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Privacy Details

A clear contact path helps you ask what we hold, why we use it or how a wallet record was matched. Use the privacy contact route linked beside the account and cashier areas, and include the email or phone detail connected to your account. We may ask for an account step or verification detail so we do not disclose records to the wrong person. Requests from Makassar follow the same policy route as requests from other Indonesian locations, where local law permits.

Team online

Data access request

Ask us to identify the account details, phone verification record or wallet reference associated with your profile. We may request a matching account detail before sending a copy, so the response reaches the person connected to the account.

Correction request

If your contact detail or account record is inaccurate, use the privacy contact route and describe the correction clearly. We check the account step first, then update the relevant record where the request is valid and where local law permits.

Wallet query

For an unmatched DANA, OVO, GoPay, QRIS, bank transfer or virtual account receipt, share its reference and approximate time. Our support route can compare that record with the account activity without asking you to send a wallet password.

DATA PRACTICE

Six Ways We Handle Your Account Data

We explain the working parts of this policy so you can decide what to share before opening an account.

Account details

We use the details you provide to create and maintain your account, complete phone verification and respond to a request about access. We do not need your wallet password for these steps, and we ask you to keep login details private.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us compare a payment status with the correct account. Bank transfer and virtual account records serve the same matching purpose, while the receipt detail helps resolve a stalled cashier status.

Cookie controls

Cookies can remember a sign-in preference, session state or policy choice on your browser. You can manage browser cookie settings, but blocking some cookies may require you to repeat the login path or select a preference again.

Device signals

When you use a mobile browser, we may receive device, browser and session signals linked to login activity. These details help us investigate repeated access failures and protect the account flow without reading personal files stored on your device.

Retention period

We keep account, wallet and support records for as long as needed for the purpose described in this policy, account security or a legal requirement. When a record no longer needs retention, we remove it or restrict further use.

Policy changes

If we change how account details, cookies or payment references are handled, we place the updated Privacy Policy on this page. Check the page before using the account again, and contact us if a change needs clarification.

Privacy Policy Questions Before Opening an Account

These answers cover the searches we hear most often about the plasa4d Privacy Policy, from wallet references to browser cookies and account access. Each answer stays focused on personal data and the steps used to request, correct or restrict its handling in Indonesia.

The plasa4d Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We do not ask for your DANA or QRIS wallet password to match a receipt. We may receive a transaction reference, status, amount and time so a payment can be connected to the correct account.

Use the privacy contact route shown beside the account and cashier areas. State that you want a data access request and include the account email or phone detail. We may verify those details before releasing records.

Yes. Send a correction request through the privacy contact route and identify the field that is wrong, such as a phone detail. We check the account step, then correct the record where valid and where local law permits.

Cookies can preserve your session, remember a policy choice and reduce repeated steps during mobile browser access. If you block them, you may need to select preferences again or repeat login before reaching the account area.

We retain payment references for the period needed to match wallet status, answer a receipt query, protect account security or meet a legal need. When that purpose ends, we remove the record or restrict its use.

The page can be read from supported locations, but account access and some data requests depend on local law. If you are in Indonesia, use the stated contact route and we will explain the applicable request process.