Reference

Open pdf2jpg With Clear Terms

pdf2jpg sets out the account, wallet and access rules before you enter the lobby, so you can check each step with a clear view of your obligations.

Account stepsWallet statusPolicy accessData requests
pdf2jpg Open pdf2jpg With Clear Terms
CONTACT ROUTES

Check Policy Help Through Account Support

A direct support route helps you resolve a Terms & Conditions question without guessing which clause applies.

Account contact Use the support route connected to your account when a Terms & Conditions question concerns phone verification, sign-in or eligibility. We can identify the relevant clause after checking the registered account path, while access remains subject to local law.
Wallet status For a disputed DANA, OVO, GoPay or QRIS status, send the payment reference through account support. We compare the receipt details with the account record and explain which Terms & Conditions step is pending before any further action.
Policy request To ask about a wording change, data correction or account closure under these Terms & Conditions, state the request clearly and use the contact path shown after login. We will identify the required verification before processing the request.
ACCOUNT SAFEGUARDS

Explore How Policy Requests Work

The policy is practical at account level: we use submitted details to administer access, check phone verification and connect payment status with the correct account record.

Data handling

We use account details for the activities described in these Terms & Conditions, including phone verification, access administration and payment matching. A request about stored details should identify your account clearly so we can check the record before responding.

Cookies

Cookies can retain sign-in state and basic page preferences during your account session. The Terms & Conditions describe their policy role without treating a cookie as proof of identity, and support can explain which account step requires verification.

Account security

Keep your phone access and account credentials private, and contact us if a sign-in event does not match your activity. We may ask for account checks before discussing a wallet record or changing details under these Terms & Conditions.

Record retention

Some account, payment and support records may remain available for the period needed to administer the agreement or meet a legal requirement. These Terms & Conditions explain the purpose of retention, while support can receive a specific record question.

Correction request

If your phone, name or account detail is inaccurate, contact us through the account support route and describe the correction. We may verify ownership first, then assess the request against the Terms & Conditions and the record we hold.

Policy contact

Questions about these Terms & Conditions, data handling or account closure should go through the contact path shown after login. Include the relevant account step and avoid sending unnecessary payment credentials in your message.

Find Answers About Terms & Conditions

The questions below address the account decisions that usually matter before you continue: what acceptance means, how local access is assessed, what happens when a payment needs checking and how to request a change. Each answer refers to the Terms & Conditions rather than making a separate promise. Where a clause requires an account check, use the support path available after login and keep your request focused on the relevant record.

They cover account opening, phone verification, sign-in, device use, payment status, data handling, cookies, retention, support contact and account closure. They also explain that access depends on local law. Read the current wording before you continue, because the applicable clauses govern your account activity.

Yes. The account path presents the Terms & Conditions before access is completed, and continuing confirms that you have read the applicable rules. Check your phone number carefully during verification, because the account record and later support requests are connected to that step.

Those payment names may be available as local wallet or QRIS routes shown in the account flow. Their appearance does not change the Terms & Conditions. A payment may still require matching against your account, and support may request the receipt reference before explaining its status.

The same account rules apply when you sign in through a mobile browser or desktop browser. A device change does not remove phone verification or payment checks. If a session behaves differently, contact support from the account path and state which device and account step produced the issue.

Access depends on local law. We may restrict or decline an account action where local rules do not permit it, even when the page or a payment label is visible. Do not attempt to bypass a location or eligibility check; ask support which policy clause applies.

Use the signed-in support contact and describe the exact field that needs correction, such as a phone detail. We may verify account ownership before changing the record. The Terms & Conditions set the request path and any retention obligations that still apply after a correction.

You can ask for account closure through the contact route shown after login. We may first verify the request and check whether a payment or support record still needs to be retained under the Terms & Conditions or applicable law. Support will explain the next step.