Reference

bejo65 Privacy Policy for Your Account

Your bejo65 Privacy Policy explains what we collect when you create an account, sign in, browse Dragon Tiger or use DANA and QRIS.

Account dataWallet recordsDevice choicesYour privacy rights
bejo65 bejo65 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Login

A clear contact path helps when you want to ask about your Privacy Policy rights, correct an account detail or understand a wallet record.

Account privacy request Use the signed-in support route to ask what account details we hold, why they are used, or which account step created a particular record. Please do not send your password.
Wallet record question For a DANA, OVO, GoPay or QRIS query, share the transaction reference and date through our support contact. We use those details to locate the record without requesting your wallet PIN.
Correction request If your phone or profile detail is inaccurate, contact us through the account help path. We may ask for a verification step before changing information tied to account access.
HANDLING DETAILS

How We Protect Your Privacy Choices

Privacy work is part of each account action, not a separate page we leave behind. We separate sign-in signals from payment references where practical, restrict internal access, and use device checks when…

Account data use

We use your phone number and verification result to create and protect account access. Profile details also help us respond to a request about your account without confusing it with another record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile account activity. We do not ask for your wallet PIN or banking password through our support route.

Cookies and sessions

Cookies can keep a signed-in session and remember selected settings. On a shared device, sign out after checking the lobby and clear browser data if you do not want the session retained locally.

Device security

We may record browser, operating system and session signals to identify unusual sign-in behaviour. This helps protect your account when you move between a mobile browser and desktop browser.

Retention approach

We keep personal and transaction records for operational, security or legal needs, then remove or anonymise them under our retention process where local law permits. Timing can depend on the record type.

Changes and access

You can ask for access, correction or clarification through the signed-in support contact. We verify the request, explain any restriction required by law, and record the outcome against the relevant account.

Privacy Policy Questions for bejo65

These Privacy Policy answers address the account and wallet questions we hear before registration. They cover phone verification, cookies, payment references, device use, data changes and local access. If your case involves a specific account record, use the signed-in support contact so we can check the correct history.

It covers account details, phone verification, device signals, cookies, wallet references and support records created when you use the service. It also explains retention, security controls and your available requests.

We use your phone number to create and protect your account and to connect a verified request with the correct record. We may ask for another verification step before changing access details.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match status records, not to request your wallet PIN.

Sign in and use the support contact shown in your account area. State that you want an access request and include the phone number on the account. We verify the request before sharing account details.

Yes. Send a correction request through the signed-in support route and identify the inaccurate field. We may confirm your identity first, especially when the change affects phone verification or account access.

Cookies can maintain login continuity and remember selected settings. They may also help us measure service use. On a shared phone or computer, sign out and clear browser data after your session.

We retain records only for operational, security or legal needs, then remove or anonymise them where local law permits. The period can differ between account details, device signals and payment references.