Reference

Open pepper0 Privacy Policy Before Account Access

pepper0 Privacy Policy explains what we collect when you create an account, sign in from a phone, or connect DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsDevice signalsPrivacy requests
pepper0 Open pepper0 Privacy Policy Before Account Access
PRIVACY HELP

Switch To The Right Privacy Support Route

A clear support path helps you control personal data without sending wallet credentials through chat.

Data access request Use the account help route to ask what personal details we hold about you. Include your registered phone reference and the subject of your request, but never send your password, wallet PIN or one-time verification code.
Correction request If your account name, phone detail or payment reference needs correction, tell us which field is wrong and why. We may ask for an account check before changing records connected with DANA, OVO, GoPay or QRIS.
Payment data query For a stalled wallet status or bank transfer record, share the date, reference and payment rail through the support route shown near account help. We can investigate the record without asking you to reveal wallet login credentials.
DATA PRACTICES

Browse Our Data Handling Commitments

We keep the Privacy Policy practical by linking each data use to an account task: access, payment matching, security, support or legal retention.

Account details

We collect details needed to create and maintain your account, including contact data and verification results. These records help us connect your sign-in with the correct wallet status and prevent an unrelated person from changing account information.

Device and sign-in data

A phone or computer may provide session, browser and security signals when you sign in. We use these signals to detect unusual access patterns, keep a session active and investigate why an account sign-in was blocked.

Cookies and preferences

Necessary cookies can keep your selected language, session state and security controls working between pages. Where optional cookies are used, you can ask us what they do and request a change through the privacy support route.

Wallet records

DANA, OVO, GoPay and QRIS may return a payment reference and status to our cashier flow. We use that limited transaction data to match an account action, resolve a failed status and avoid requesting your wallet PIN.

Retention and deletion

We retain records only for the period connected with account security, payment reconciliation, support handling or applicable requirements. You can ask which record is retained, why it remains stored and whether deletion or restriction is available.

Privacy contact

Send a privacy question through the contact route shown in account help and describe the action you want, such as access, correction or deletion. We may verify account ownership before discussing personal records or applying a change.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened. They explain the practical difference between account data, device signals, payment references and support records. If your situation is not covered, use the privacy contact route shown inside account help and include only the details needed to locate your request.

The pepper0 Privacy Policy covers account creation, phone verification, sign-in and device signals, cookies, payment references, support requests and retention. It also explains how you can ask for access, correction, deletion or clarification, where those actions are available under applicable requirements.

No wallet PIN should be sent through our account or support routes. When you use DANA or OVO, we receive the payment reference and status needed to match the account action. Keep your wallet credentials inside the relevant payment service.

Phone verification helps connect you with the correct account and reduces the chance that another person changes your details. We may use the verification result when you sign in, request account help or ask about a wallet status.

Yes, you can ask for a copy through the privacy contact route shown in account help. Describe the account reference and the data period you need. We may verify ownership before releasing records, so do not include your password or wallet PIN.

Send a correction request through account help and identify the exact field, such as a phone detail or account name. We will check the request against the account record and may request verification before changing information connected with payment or sign-in history.

Retention depends on why the record exists, such as payment matching, account security, support handling or applicable requirements. Ask us which record you mean and why it remains stored. We can then explain the relevant period and available deletion options.

The Privacy Policy is written for account access connected with Indonesia, including requests from Yogyakarta. Availability and eligibility depend on local law. Payment rails, data requests and account actions may also require checks tied to your account and the selected payment provider.