Reference

joss777 Privacy Policy for Your Account Data

The joss777 Privacy Policy explains what we collect when you create an account, verify your phone, use a mobile device or select DANA, OVO, GoPay and QRIS.

Phone verificationWallet recordsCookie choicesData requests
joss777 joss777 Privacy Policy for Your Account Data
CONTACT ROUTES

Reach Us About a Privacy Request

A clear contact path helps when you want to ask about a Privacy Policy matter, correct a phone detail or question a wallet record. From the account support route, tell us the account identifier, the request you need and a safe reply address. We may ask for account verification before disclosing personal data, including when you contact us from Medan or Semarang.

Team online

Account data request

Use the support contact route linked from your account to ask which personal data we hold, why it is used and what verification we need before replying.

Wallet record question

Send the payment reference and method, such as QRIS, DANA or bank transfer, so we can match a receipt or status without asking for your wallet password.

Correction request

Tell us which phone, profile or contact detail needs changing. We confirm ownership first, then record the request and explain any legal or operational reason for keeping an old entry.

SECURITY PRACTICE

Browse the Security Steps Behind This Policy

We apply this Privacy Policy through practical account and payment controls rather than vague promises.

Purpose of collection

We collect account, phone, device and transaction data for account access, payment matching, support replies, security checks and legal duties. We do not need your wallet password to confirm a payment reference.

Cookie handling

Cookies and similar browser records can keep a session active, remember selected settings and help identify suspicious sign-in patterns. You can manage browser cookie choices, though some account functions may then behave differently.

Account protection

Phone verification and sign-in event records help us confirm account ownership. Keep your credentials private and contact support if a device path or login event does not match your activity.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account payments, we use references and status data to match the account action. We do not treat a receipt image as permission to access your wallet.

Retention periods

We keep records for as long as needed for the stated purpose, account support, security checks or legal duties. When a record is no longer required, we remove it or restrict its use where applicable.

Changes and requests

You can contact us to ask for access, correction or deletion of eligible personal data. We may request identity checks, and the outcome depends on local law and the record involved.

Find Answers About Privacy Policy Requests

These Privacy Policy answers address the account, device and payment questions you may have before opening an account. We keep the same request path available after phone verification, so you can ask about a specific record instead of sending sensitive wallet credentials.

It covers account and phone details, device and cookie records, payment references, support messages, security events and the reasons we use or retain those records for account services.

We use your phone number for account identification and phone verification before account access. It can also help us connect a privacy request to the correct account when ownership must be checked.

Yes. The Privacy Policy explains our handling of DANA and QRIS references, payment status and support records. DANA, OVO, GoPay, QRIS and banks may apply separate terms to their own data handling.

You can contact support with the account identifier and the field that appears wrong. We verify ownership before making a change, and some records may need to remain for legal or payment reasons.

Send a data request through the account support contact path, naming the records you want, such as phone, device or payment references. We may ask for verification before preparing a reply.

Retention depends on the purpose, security needs, support history and legal duties connected with the record. We remove or restrict data when it is no longer needed where local law permits.

Yes. Contact us with the device or browser context and your question. Cookies may support sessions, settings and security checks, while your browser controls can affect how those functions operate.