Reference

peti4d Privacy Policy For Your Account

Our peti4d Privacy Policy explains what we collect when you create an account, verify your phone, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Clear collection purposesWallet data boundariesPhone verification contextDirect privacy requests
peti4d peti4d Privacy Policy For Your Account
PRIVATE HELP ROUTES

Where To Ask About Privacy

A privacy question should not be mixed into a general payment request.

Account privacy request Send your request from the signed-in account path when possible.
Wallet reference query For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than wallet…
Login access support If phone verification blocks access, contact support through the account entry route.
DATA HANDLING PRACTICE

What We Do With Account Data

We separate service records by purpose instead of treating every detail as permanent account content. Account security, wallet matching, device access and support history each have a practical reason to exist.

Account details

We use your phone number and account credentials to create access, complete phone verification, and protect sign-in. We do not need your wallet PIN to connect DANA, OVO, GoPay or QRIS status.

Device signals

Your browser or mobile device may provide session, language, time and security signals. These help us recognise unusual sign-ins and keep a returning device connected to the correct account.

Cookies

Cookies can keep a session active, remember selected settings and help us detect account misuse. You can manage cookies through your browser, although some sign-in and security functions may then need another check.

Payment references

A DANA or QRIS transaction reference helps us match a status request, while bank transfer and virtual account references help resolve account records. We do not request card or wallet passwords through support.

Retention periods

We retain records while they serve account security, transaction matching, dispute handling or legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account details.

Changes and contact

You can ask us to correct an inaccurate phone, contact or account detail through support. We may request ownership checks before changing private data, especially after a new-device sign-in.

Privacy Policy Questions About peti4d

These answers address the searches we receive most often about the peti4d Privacy Policy. They focus on account access, device behaviour, local wallet references and requests to see or change personal records, so you know what to prepare before contacting us.

It covers account details, phone verification, device signals, cookies, support messages, payment references and retention. It applies when you access peti4d from Indonesia where local law permits.

No. We use the transaction reference and status needed for account matching or support. We do not ask for your DANA, OVO, GoPay or QRIS PIN through our privacy route.

Phone verification helps create the correct account and protect sign-in. We may use the linked number to confirm ownership before discussing private records or changing account contact details.

Cookies support sign-in sessions, saved settings and security checks. Browser controls let you manage them, but refusing necessary cookies can require another sign-in or limit account access.

Yes. Contact support from the signed-in account path when possible, identify the record and explain the correction. We may verify ownership before changing a phone number or private detail.

We keep references while needed for transaction matching, account security, dispute handling or legal duties. When that purpose ends, we remove the record or separate it from direct account details.

Provide your linked phone number, account identifier and a precise request. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account matters, provide the reference only, never a PIN.