Reference

Privacy Policy for jos178 Accounts

The jos178 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for account funding.

Account dataWallet referencesCookie choicesAccess requests
jos178 Privacy Policy for jos178 Accounts
CONTACT YOUR WAY

Three Policy Questions We Can Handle

A clear contact path matters when a Privacy Policy question affects your account or wallet status. Start from the support route connected to your jos178 account and include the email or phone detail used for verification, without sending a password or wallet PIN. We can use the transaction reference for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query. If you are in Surabaya or elsewhere in Indonesia, the same account path lets us identify the relevant record and explain the next step where local law permits.

Team online

Data access request

Ask us for the personal data connected with your account through the account support route. Include your account identifier and the email or phone detail used at registration so we can check identity before preparing a response. We do not need your password, wallet PIN or full payment credentials.

Correction or deletion

If a contact detail is wrong or you want to ask about removal, send the request through account support with the specific field or record concerned. We first verify the account step, then explain what can be changed and what may need to remain for security, payment reconciliation or a legal duty.

Wallet record check

For a DANA, OVO, GoPay or QRIS status question, provide the date, amount and reference shown in your account rather than a wallet password. We compare the account event with the payment status and reply through the support path linked to your account. Bank transfer and virtual account queries follow the same process.

DATA HANDLING DETAILS

Six Practical Privacy Controls We Use

Privacy Policy commitments are reflected in account operations, not only in page text. We separate login details from payment references, limit internal access to records needed for a task, and use device…

Account collection

When you open an account, we collect the contact details and verification result needed to create and protect access. Signing in from a mobile browser may also create a device and security record. We use these details for the account path, not to request your wallet PIN or password.

Payment references

A DANA, OVO, GoPay or QRIS action can produce a reference, amount, timestamp and status that we use to match the cashier event. Bank transfer and virtual account records work in the same way. These references help us investigate a missing status without exposing your wallet credentials.

Cookie controls

Cookies can remember a sign-in preference, protect a session and show whether a page functioned correctly. Your browser settings let you remove or restrict them, although some account steps may then need to be repeated. Our Privacy Policy explains the purpose of each cookie category used on the site.

Device security

We may record device type, browser details, connection signals and failed sign-in events to detect account misuse. If a pattern looks unusual, we may ask you to complete phone verification before account access continues. These checks support security for mobile and desktop paths without requiring an installed app.

Retention periods

We keep account, security and payment records only while they serve an operational, dispute, reconciliation or legal purpose. A request to remove data is assessed against those purposes. When a record no longer needs to be retained, we delete it or separate it from direct account identifiers where appropriate.

Your requests

You can ask what personal data we hold, request a correction, question a processing purpose or ask about deletion through the account support route. Include enough detail for us to locate your record, but never send a password, wallet PIN or complete card credential. We may verify identity first.

Privacy Policy Answers For jos178

These Privacy Policy questions focus on the account, device and wallet situations you are most likely to encounter on jos178. Each answer points to the practical action available to you, from checking a QRIS reference to asking for a copy of your data. If your situation is not covered, use the account support route and describe the exact account step or payment reference involved. We will assess the request where local law permits and explain any limit that applies.

It covers information you submit for an account, phone verification records, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security, access requests and the situations where local law permits processing.

We collect the contact and account details needed to create access, together with the result of the required phone verification step. When you sign in, we may record device type, browser details, connection signals and security events. We do not need your wallet PIN or password for this process.

Yes. The Privacy Policy covers references linked to those wallet actions, including a status, amount, timestamp and reconciliation reference. We use them to match your account event and investigate a missing result. We do not ask you to send a wallet PIN. Bank transfer and virtual account records follow the same approach.

You can ask through the account support route connected with your account. Include the identifier and contact detail used during registration so we can verify the request. We will explain the data available and any lawful restriction. Do not include your password, wallet PIN or complete payment credential.

Send a correction request through account support and name the specific detail, such as an email address or phone number. We may verify your identity before changing it because the account path and wallet status depend on accurate records. We will explain the next step where local law permits.

We retain records for as long as they support account security, payment reconciliation, dispute handling or a legal requirement. Device events may be kept for security analysis, while wallet references help match a DANA, OVO, GoPay or QRIS status. When the purpose ends, we delete or anonymise the record where appropriate.

Your browser can remove or restrict cookies, although some account functions may need to be repeated. For a policy question or concern about a change, use the account support route and identify the relevant page or cookie purpose. We will explain the current handling and any choices available where local law permits.