Reference

Privacy Policy For Your dian4d Account

Your account data, wallet activity and device signals are handled under this Privacy Policy before you open the lobby.

Account data scopeDANA privacy contextOVO wallet checksGoPay and QRIS signals

Browse Lobby Read FAQ

Privacy Rules For Your Account

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

This Privacy Policy covers the data we collect when you create an account, sign in, use wallet features, contact support or browse from mobile and desktop. We use your name, phone number, login records, device type, IP address, payment references and support messages to run the

1
account, check wallet actions and keep access records consistent. Eligibility and access depends on local law, so we may process region signals for Indonesia to keep the account flow aligned with that rule. If you connect from Medan or another Indonesian city, the same privacy steps
2
apply: account checks first, wallet matching second, support records only when you contact us. We do not sell your personal data. We share limited data only with payment processors, security tools or service vendors that help us run the account safely.

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

PRIVACY CONTACT

How To Reach Our Privacy Team

Privacy questions should reach the people who can check account records, not a generic inbox.

Live chat privacy request Use live chat between 09:00 and 23:00 WIB when you need a fast privacy check. We verify your registered phone number first, then check account logs without showing wallet data in the chat thread.

Email data correction Send account correction requests by email when your name, phone number or wallet label needs review. Include your username, the affected field and whether the issue relates to DANA, OVO, GoPay or QRIS.

Wallet record query For payment privacy questions, tell us the method, date and approximate time of the transaction. We compare the wallet reference with our account record and reply with what we can correct or explain.

DATA HANDLING

Cookies, Security And Retention Controls

We keep this policy practical so you know what happens after each account step. Cookies support sign-in, device recognition and language choices, while security logs help us spot repeated failed access.

Account creation data

When you join, we collect the details needed to create your account, such as username, phone number and password record. We use them for sign-in, recovery checks and privacy replies tied to your account.

Device and cookie signals

We use cookies and device signals to keep your session active, remember basic preferences and detect unusual access. You can clear browser cookies, but you may need to sign in again afterward.

Payment privacy checks

DANA, OVO, GoPay and QRIS references are used to match wallet actions to your account. We do not need your wallet app password, and support will not ask you to send it.

Security log use

Failed login attempts, IP changes and device shifts are recorded so we can protect account access. If a login looks unfamiliar, contact us with the time and device you normally use.

Retention practice

We keep account and payment records for operational, dispute and legal needs, then limit access when the record is no longer active. Privacy requests are handled with the same account verification step.

Change request path

To update personal data, contact live chat or email from your registered details. We may ask one account question before changing records, especially when the request affects wallet matching.

Privacy Questions Before You Join

These answers cover the privacy points we hear most before you open an account: what data we collect, why payment references matter, how cookies work and how to ask for a correction. We keep the wording direct because your privacy request should not require legal vocabulary. If an answer does not match your situation, contact us with your account name and the record you want us to check.

We collect the details needed to create and protect your account, including username, phone number, password record, login activity and device signals. We use that data for access, recovery, wallet matching and privacy support replies.

Payment references help us match wallet actions to your account and investigate a missing or duplicated record. We use the method name, time and reference only for account operation, dispute checks and required record keeping.

No. We do not sell your personal data. Limited data may be shared with payment processors, security tools or service vendors that help us operate accounts, verify wallet records or maintain safe access.

Contact live chat or email using your registered details and tell us which field needs correction. We verify the account first, then update the record or explain why a wallet or security record must stay unchanged.

Yes, you can ask us to review removal of personal data. We check whether account closure, wallet records, dispute handling or legal duties require us to keep part of the record for a defined period.

Cookies help keep your sign-in session active, remember simple preferences and detect repeated failed access. If you clear cookies on Chrome, Safari or another browser, you may need to sign in again.

Only staff who need the case can view the request, such as support or account security. We keep the request tied to your account record so we can answer without exposing wallet details unnecessarily.

Privacy Policy For Your dian4d Account

How To Reach Our Privacy Team

Cookies, Security And Retention Controls

Account creation data

Device and cookie signals

Payment privacy checks

Security log use

Retention practice

Change request path

Privacy Questions Before You Join

01 What personal data do you collect when I open an account?

02 Why do you keep DANA, OVO, GoPay or QRIS references?

03 Do you sell my personal data to other companies?

04 How can I ask you to correct my account data?

05 Can I ask for my account data to be removed?

06 What cookies do you use on mobile and desktop?

07 Who can see my privacy request inside dian4d?

Related Pages