Reference

Privacy Policy For Your jos13 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your jos13 account, including phone verification, device access and wallet records for DANA, OVO…

Account dataWallet recordsCookie choicesPolicy requests
jos13 Privacy Policy For Your jos13 Account
PRIVACY SUPPORT

Where Privacy Questions Reach Our Team

A clear contact route helps you ask about the Privacy Policy without explaining your account history in an open chat or public channel.

Policy request Ask our support team to explain how a particular account field, phone verification record or device identifier is used under the Privacy Policy. We will use the account details you provide to locate the relevant record and may ask for a further account step before responding.
Wallet record When a DANA, OVO, GoPay or QRIS receipt appears incorrectly, tell us the transaction reference and account phone number through the support route. We can review the privacy record connected with that receipt without asking you to disclose your wallet PIN or password.
Account access If a device change or phone verification step prevents you from reaching your account, contact support with the affected device type and approximate time. We use those details to check the access record and protect your account while handling the Privacy Policy request.
DATA CONTROLS

Six Controls Behind Your Account Record

Our privacy process follows the same practical path you see when an account is opened: we identify the account, record the action, limit internal access and keep only what the stated purpose…

Data collection

We collect details needed for an account record, such as your phone number, verification result, sign-in event and selected settings. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match account status, not to request your private wallet credentials.

Cookie choices

Essential cookies support sign-in continuity and remember settings on the device you use. Where optional cookies are offered, your choice is recorded separately from account details. Clearing browser storage can remove local preferences, so you may see the consent prompt again on a later visit.

Account security

Phone verification connects account access with the number you submit, while device and session signals help us notice unusual activity. We do not ask for your password in a support message. A security check may be required before we disclose or change account data.

Record retention

We keep personal data while it serves the account, security, payment reconciliation or legal purpose described in the Privacy Policy. When a record is no longer required, we remove it or separate it from direct account identifiers according to our retention process.

Change requests

You can ask us to correct an inaccurate phone, device or wallet reference through the support route. State what appears wrong and provide the account phone number. We may verify ownership before making a change, especially when the request affects sign-in or payment history.

Contact ownership

Privacy questions are handled by our support team through the account contact path, including requests about cookies, retention, access records and payment references. We keep the request connected to your account so the response addresses your actual record rather than a generic platform explanation.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we expect before you open a jos13 account: what we collect, why payment references appear, how device activity is used and where to ask for a change. We keep each answer tied to an account action, from phone verification through a QRIS receipt check. Availability and eligibility depend on local law, so the policy should be read alongside the access conditions shown for your region.

The jos13 Privacy Policy covers account details, phone verification, device and session records, cookie choices, payment references and support requests. It also explains retention, account security and how you can ask us to correct, access or remove personal details where local law permits.

We record the result of phone verification to connect account access with the number you submitted and to reduce mistaken or unauthorised sign-ins. The record can also help support locate your account when you ask about the Privacy Policy or request a data correction.

Yes. The Privacy Policy includes references connected with DANA, OVO, GoPay and QRIS, such as a receipt number, status or account match. We use those details to reconcile activity and answer support requests. We do not need your wallet PIN or password.

We use device type, session details and sign-in timing to protect account access and investigate unusual activity. These signals help us distinguish a normal mobile return from a possible account issue. They are handled under the Privacy Policy and are not a request for your private device content.

You can contact our support route to request a correction to an account phone number, device record or payment reference. Describe the specific error and identify your account. We may complete an ownership check before changing data that controls access or affects account history.

We retain account, security and payment-reference data only while it supports the purpose stated in the Privacy Policy or a legal requirement. After that period, we remove the record or separate it from direct identifiers according to our retention process.

Yes. Ask our support team about cookie choices, stored account details or a removal request through the account contact path. We will explain what can be changed or removed, verify ownership when needed and apply the request where local law permits.