Reference

dinar33 Privacy Policy for Your Account

The dinar33 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use payment options such as DANA, OVO…

Account dataDevice detailsWallet recordsPolicy requests

Explore Our Lobby Read FAQ

How Payment Data Enters Our Policy

dinar33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the account details you submit, verification results, sign-in records and payment references needed to connect activity with the correct account. A DANA, OVO, GoPay or QRIS reference can show that a payment request was submitted, while a bank transfer or virtual account record may

1
include a bank reference and status. We do not ask for a wallet password through ordinary support messages. Device type, browser path, approximate connection details and security events help us detect unusual access to your account. We retain records for the period needed to operate the
2
account, answer disputes, meet applicable obligations or protect our service. Where local law permits, you can ask what data we hold, request a correction or ask whether deletion is available. Eligibility and access depend on local law, and this Privacy Policy applies to the dinar33 account
3
path rather than unrelated websites.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH POLICY REQUESTS

Where to Ask About Your Privacy

A clear support route matters when an account record or wallet reference looks unfamiliar. Sign in, open the support path beside your account and include the email or phone detail attached to your profile, plus the payment reference if your request concerns DANA, OVO, GoPay, QRIS or a bank transfer. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account support path

Use the support link inside your signed-in account to ask about stored details, an access record or a correction. Include the account contact used during verification so we can match your request.

Payment record check

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the transaction reference and date. We can check the linked status without requesting your wallet password.

Privacy request route

Ask through the same account support route for a copy, correction or eligible removal of personal data. We may verify account ownership before discussing records tied to your profile.

DATA HANDLING DETAILS

Inside dinar33 Privacy Controls

Our policy work follows the practical steps you meet when using an account: collection at sign-in, checks around payment status, security review for unusual device activity and a response path for data…

Account details

We may store the name, contact details and verification responses you provide when opening an account. These details help us connect your sign-in, policy request and account records to the correct profile.

Phone verification

Before account access is completed, we may use your phone verification status to confirm ownership. We do not treat a verification code as a support password, and we will not ask you to disclose it.

Device activity

Your phone, tablet or desktop path can create security records such as browser type, sign-in time and unusual access signals. These records help us investigate an account event without reading unrelated device content.

Cookies and sessions

Cookies or similar session tools can remember sign-in state and basic preferences. You can adjust browser controls, though changing them may require another sign-in before your account details appear.

Retention period

We keep account, payment reference and security records only as long as needed for account operation, dispute handling, applicable duties or a documented security concern, then assess them for removal.

Changes and contact

To request access, correction or eligible deletion, contact us through the signed-in support path. We may ask for an account detail or payment reference to confirm that the request is yours.

What You Ask About This Privacy Policy

These Privacy Policy answers focus on the records you are most likely to ask about before opening or using a dinar33 account. They cover local wallet references, device activity, account access and requests made through our support route. If your question is not listed, send it through the signed-in contact path and include only the details needed to locate your account.

It covers personal data connected with your account, sign-in, phone verification, device activity, cookies, payment references and support requests. It does not describe unrelated websites or data collected outside the dinar33 account path.

We do not ask for your DANA or QRIS wallet password through ordinary support messages. Our records may contain a payment reference, amount status or bank response needed to match activity with your account.

Device and browser details help us recognise sign-in patterns, investigate unusual access and protect your account. The record can include device type, browser path, sign-in time and approximate connection details.

Sign in and use the support route linked to your account, then ask for a copy of the personal data associated with your profile. We may verify ownership before releasing account-specific records.

Yes, you can request a correction through the signed-in support path. State which detail is inaccurate and provide the updated value; we may compare it with your account verification record before making a change.

We retain payment references for the period needed to operate the account, resolve a dispute, meet applicable obligations or investigate security events. After that need ends, the record is assessed for removal.

The policy is written for Indonesian account access, including requests from Jakarta and Surabaya, but eligibility and access depend on local law. Use the support path to ask how a local rule affects your request.

dinar33 Privacy Policy for Your Account

Where to Ask About Your Privacy

Account support path

Payment record check

Privacy request route

Inside dinar33 Privacy Controls

Account details

Phone verification

Device activity

Cookies and sessions

Retention period

Changes and contact

What You Ask About This Privacy Policy

01 What does the dinar33 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does dinar33 collect device and browser details?

04 How can I request my personal data under this Privacy Policy?

05 Can I ask dinar33 to correct account data?

06 How long does dinar33 keep payment references?

07 Does the Privacy Policy apply in Jakarta and Surabaya?

Related Pages