Reference

join99 Privacy Policy for Your Account

Our Privacy Policy explains what join99 collects when you open an account, sign in from a phone or desktop, and use the lobby with DANA, OVO, GoPay or…

Clear data purposesWallet record controlsCookie choicesAccount request path
join99 join99 Privacy Policy for Your Account
CONTACT THE TEAM

Reach Support About Privacy Requests

A direct support route helps you ask what data we hold, why a record appears, or how to correct an account detail. Start from your signed-in account support path when you can, because it helps us connect the request with the right account. If you cannot sign in, use the public support contact and include only the minimum details needed to locate your request. We may ask for an account step or identity check before changing information. Our responses follow the Privacy Policy and applicable local law.

Team online

Account support

Use the signed-in support path to ask about account data, a phone verification record or a wallet status entry. We can connect your request to the correct account more reliably when you send it from the same device and account session.

Payment records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, provide the payment reference rather than your wallet password. We use the reference to check the receipt and explain what personal data is attached to that transaction.

Access problems

If a privacy request is blocked because you cannot sign in, contact support through the available account help channel and describe the device path, such as mobile browser or desktop browser. We will ask for only the checks needed to confirm ownership.

HOW WE HANDLE DATA

Browse join99 Privacy Controls Clearly

The practical side of our Privacy Policy is simple: we keep account records connected to the service task they support, limit access to people who need it, and use account checks before…

Data we receive

We may receive your phone number, account details, sign-in events, device information, connection data and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can identify a transaction without requiring your wallet password.

Cookies on devices

Cookies can keep a browser session available, remember selected settings and help us detect unusual sign-in activity. You can manage cookies through your browser controls, although removing them may require you to repeat the account access step on mobile or desktop.

Account protection

We use phone verification and sign-in checks before allowing account access or sensitive changes. Do not send a password, wallet PIN or one-time code in a support message. If a sign-in looks unfamiliar, report it through the account support path.

Retention decisions

We retain records for the period needed to provide account support, reconcile payment references, address disputes and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the retention rules described by this Privacy Policy.

Your data requests

You can ask us to access, correct or clarify eligible personal data connected with your account. Send the request through support with a reachable contact and account reference. We may confirm ownership before releasing details or applying a change.

Policy questions

For a question about collection, cookies, security, retention or a payment record, contact us through the available support channel. Include the subject of your request and avoid unnecessary personal details. We will assess the request under this policy and local law.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. We explain the data connected with sign-in, mobile browsing, payment references, cookies and support requests in plain terms. If your situation is different, send a focused request through the available support channel. Access and eligibility depends on local law, so a policy answer cannot replace a requirement that applies in your location.

The join99 Privacy Policy covers account details, phone verification, sign-in events, device data, cookies, support messages and payment references. It explains why we use those records, how we protect access, how long records may remain and how you can request access or correction.

We may collect the phone number and account details you provide, along with device and connection data created during sign-in. If you contact support, we receive the message and any account reference you include. We ask for only the details needed for the stated account task.

Yes. The Privacy Policy covers payment references and receipt details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. These details help us match a transaction to your account. We do not ask you to send a wallet password.

Cookies may support sign-in continuity, remember a selected setting and help identify unusual account activity. Your mobile browser controls whether cookies remain available. If you remove them, you may need to repeat phone verification or the account access step when returning.

You can contact support to ask for access to eligible account data or correction of an inaccurate detail. Include a reachable contact and account reference, but do not send passwords or wallet codes. We may confirm ownership before completing the request under this Privacy Policy.

We keep account and payment records for as long as needed for support, receipt matching, dispute handling and applicable legal duties. The period can differ by record type. When the reason for keeping a record ends, our handling follows the retention approach in this Privacy Policy.

Use the signed-in account support path when you can, or the available public support contact if sign-in is not working. State whether your concern involves data access, correction, cookies, security, retention or a payment reference. We may request an ownership check before discussing account-specific details.