Reference

Open permen4d Privacy Policy Clearly

permen4d Privacy Policy explains how we use account details, mobile-browser data and payment records when you access our lobby from Semarang or elsewhere in Indonesia.

Account dataWallet recordsCookie choicesAccess depends on law
permen4d Open permen4d Privacy Policy Clearly
CONTACT ROUTES

Ask About Privacy Through Your Account

Privacy questions should reach the team through the contact route shown in your account area, because that lets us separate a genuine request from an unrelated message. We can help you locate a privacy request, clarify a wallet record or explain why a verification step appears. If you are in Makassar, the same online route applies; we handle requests by account details rather than city.

Team online

Account privacy path

Open your account area and use the displayed support route for a copy, correction or deletion request. We may ask for account details before discussing private records.

Wallet record check

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, include its date and reference in your message. We compare the record with the account before replying.

Access clarification

When a mobile browser or desktop sign-in raises a privacy question, tell us the device path and account step involved. We use that context to investigate without requesting wallet passwords.

DATA PRACTICES

Explore How We Handle Your Privacy

We keep this policy practical: each data category has a purpose, an access path and a request route.

Data we collect

We may collect account contact details, verification material, sign-in events, browser signals and payment references. These records support account access, fraud checks, payment matching and replies to your privacy requests.

Cookie controls

Cookies can retain session settings and help us recognise the browser path from login to the lobby. You can clear browser cookies or ask us which cookie purpose relates to your account.

Account security

Before releasing private account records, we may compare your request with the account contact and verification step. Never send a wallet password; DANA, OVO, GoPay and QRIS credentials stay with you.

Retention periods

We retain records only for the account, security, payment matching or legal purpose that requires them. When that purpose ends, deletion or anonymisation follows our internal retention process.

Correction requests

If your contact detail or account record is wrong, send the relevant field through the privacy contact route. We may request a verification step before changing a record tied to access.

Deletion requests

You can ask us to delete eligible personal data, although payment, security or legal records may need to remain for a defined period. We explain any limit in our reply.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the searches we hear most from people considering a permen4d account. Each answer points to a practical step, from checking a QRIS record to requesting a copy of account data. If your situation is different, use the privacy contact route and include only the details needed to identify your request.

It covers account details, verification records, browser and device signals, cookies, support messages and payment references connected with access. It also explains purposes, retention, security and ways to request changes.

We use a payment reference, amount and status to match a DANA or QRIS receipt with the correct account and investigate disputes. We do not need your wallet password for that check.

Yes. Send a request through the privacy route displayed in your account area. We first verify the requester, then explain which account records can be copied and how they will be provided.

Identify the inaccurate field in a privacy request, such as a contact detail or verification record. We compare the request with your account before making a correction or explaining why a check is required.

You may request deletion of eligible personal data. Some payment, security or legal records can require temporary retention, and our reply will identify the purpose and expected handling for those records.

Yes. The policy applies when you sign in through a mobile browser or desktop browser. We may record browser type, device signals and session events needed to secure the account path.

Where local law permits, you can request access, correction or deletion through the privacy contact route. Account verification may be required, and access or eligibility depends on local law.