Reference

Open diba33 Privacy Policy Before Account Access

At diba33, our Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount access controlsCookie choicesRequest path
diba33 Open diba33 Privacy Policy Before Account Access
PRIVACY HELP

Ask About Privacy Through Your Account Path

A privacy request should be easy to connect with the right account record.

Data access request Ask which account, login, device and payment details we hold.
Correction request Send the detail that needs changing, such as a contact number or wallet reference.
Security concern Report an unfamiliar sign-in or account change through the support path.
DATA PRACTICE

See How We Handle Wallet Data

Our Privacy Policy is tied to practical account work: confirming access, matching DANA or QRIS status, checking a bank transfer reference and keeping the right security record.

Account details

We handle the contact and identity details you provide during account creation so we can connect your login with the…

Device signals

A mobile browser may send device, session and security signals when you sign in.

Wallet references

DANA, OVO, GoPay and QRIS activity can create a reference or status record.

Cookie controls

Cookies can keep a session working, remember selected settings and support security checks.

Retention decisions

We keep account, payment and support records for the period needed for service checks, disputes and legal duties.

Change requests

Contact us through your account help path to request access, correction or a deletion assessment.

Find diba33 Privacy Policy Answers

These Privacy Policy answers cover the questions you may have before creating an account or connecting an Indonesian wallet. We keep each answer focused on the data action involved, from mobile login signals to payment references and requests made through the account help path. Where access or eligibility is discussed, it depends on local law.

The diba33 Privacy Policy covers data collected through diba33.club, including account details, login activity, device signals, support messages, cookies and payment references from routes such as DANA, OVO, GoPay and QRIS.

We use your account details to create and protect the correct login, connect support requests with your record and confirm account actions. We do not ask you to send a password or private login code when requesting help.

Yes. The Privacy Policy explains that DANA and QRIS actions may produce a payment reference or status detail linked to your account. We use that record to match the action, check a receipt and resolve a status question.

When you sign in through a mobile browser, we may receive session, device and security signals. These help us identify unusual access and protect your account. They are handled for account security and related service checks described in the policy.

Use the account help path and ask for a data access request. Include the email or phone detail linked to your account and enough context to locate it. We verify ownership before explaining or providing the relevant record.

You can request a correction or ask us to assess deletion through the account help path. We verify the request, update inaccurate details where appropriate and explain when a record must remain for disputes, security or legal duties.

We retain account, payment and support records for the period needed for account security, receipt checks, disputes and applicable legal duties. The retention period can vary by record type; you can ask about a specific record through support.