Reference

Open the pdf2jpg Privacy Policy

The pdf2jpg Privacy Policy shows what account, wallet and device data we use when you open your account, sign in and check payment status.

Clear data purposesWallet record contextAccess request pathLocal law wording

Explore Our Lobby Read FAQ

Check How Privacy Policy Applies

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

Our Privacy Policy applies when you create an account, complete phone verification, sign in from a mobile browser or desktop, and use account tools connected with payment status. We may record account details, verification results, device and browser signals, login events, support messages, and transaction references

1
so we can protect access and match a receipt to the correct account. DANA, OVO, GoPay and QRIS can appear in payment records, while bank transfer and virtual account references may identify a payment attempt. We use these records for the purposes described here, retain them
2
only as needed for those purposes or legal duties, and limit access within our operating process. Where access or eligibility is discussed, it depends on local law.

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

REACH POLICY SUPPORT

Reach Support About Privacy Policy

A direct support route helps when your Privacy Policy question concerns a login, wallet record or account detail.

Account data questions Ask through the signed-in support path when you need to know which account details we hold. Include your verified phone number and the specific field you want clarified, so we can check the correct account without requesting your password.

Wallet record checks For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate date through support. We can compare the receipt or status entry with your account while keeping full wallet credentials out of the message.

Privacy request route Use the account support contact to request access, correction or removal of eligible data. We may ask for an account step or phone check before acting, because a privacy request must reach the right account holder.

BROWSE PRIVACY CONTROLS

Browse Privacy Controls Inside pdf2jpg

Privacy work is tied to practical account events rather than broad statements. We separate sign-in signals from payment references, use cookies and similar device storage to keep account sessions working, and apply…

Account data

We may hold the details you submit during account creation, including contact data and phone verification results. This lets us connect a support request to the correct account and explain which fields can be changed.

Cookies and sessions

Cookies or similar browser storage can keep a signed-in session, remember basic access settings and help us identify unusual login activity. You can manage browser storage, although clearing it may require another account sign-in.

Wallet references

Payment records can contain a rail name such as QRIS, DANA, OVO or GoPay, plus a reference and status. We use that limited context to reconcile an account event, not to request your wallet password.

Account security

Phone verification and sign-in checks help prevent an account change from being made by the wrong person. If your device changes, we may ask for the same account checks before discussing private records.

Retention period

We keep personal data for the period needed for the stated purpose, account support and applicable legal duties. A retention question should name the record, such as a QRIS receipt or login event, for a useful response.

Change requests

You can ask us to access or correct eligible data through the signed-in support route. Where local law permits, you may also request deletion or restriction, subject to records we must retain for legal or account reasons.

Find Privacy Policy Answers Before Access

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record from Indonesia. We keep the wording tied to actual account steps, including phone verification, mobile browser access, payment references and support requests. When a right or access condition depends on jurisdiction, the applicable position depends on local law.

The pdf2jpg Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references linked with DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security checks and how you can request access or correction.

We use phone verification to connect account access with the correct person and to reduce unauthorised changes. The result can also help support locate your account when you ask about a login or payment record. Handling of this data follows the Privacy Policy.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including a rail name, status and receipt reference. We use this context to reconcile an account event and do not ask you to share a wallet password in support.

On a mobile browser, cookies or similar storage may keep your session active, remember basic access settings and help identify unusual sign-in activity. Clearing browser storage can end the session and require phone verification or another sign-in check before access resumes.

Use the signed-in support contact and ask for an account data access request. State the phone number connected with your account and the data area you mean, such as login events or QRIS records. We may verify account control before responding.

You can request correction of inaccurate eligible data through the support path shown in your account. Where local law permits, you may ask about deletion or restriction. We may retain selected records when account support, payment reconciliation or legal duties require them.

Contact us through the signed-in account support route and describe the Privacy Policy request clearly. Include a relevant account step, such as phone verification, or a payment reference when needed. Do not send passwords, wallet PINs or complete payment credentials.

Open the pdf2jpg Privacy Policy

Reach Support About Privacy Policy

Browse Privacy Controls Inside pdf2jpg

Account data

Cookies and sessions

Wallet references

Account security

Retention period

Change requests

Find Privacy Policy Answers Before Access

01 What does the pdf2jpg Privacy Policy cover?

02 Why does pdf2jpg collect phone verification data?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What cookies does pdf2jpg use on mobile?

05 How can I request a copy of my account data?

06 Can I ask pdf2jpg to correct or delete data?

07 Who should I contact about a Privacy Policy request?

Related Pages