Reference

Privacy Policy for Your dian4d Account

dian4d explains how we collect, use and protect the account, device and wallet details needed for your lobby access.

Clear data purposesWallet details explainedPhone access checksDirect correction path
dian4d Privacy Policy for Your dian4d Account
HELP WITH PRIVACY

Privacy Requests Without Wallet Guesswork

A privacy request should not leave you searching through unrelated pages. We keep the account help route close to the cashier path so you can raise a question about personal data, a payment receipt or a login record from the same signed-in area. If access stalls, tell us which account step you reached and which device you used. We will use those details to locate the relevant record without asking you to resend unnecessary wallet data.

Team online

Account data request

Open account help and describe the record you want to access, correct or remove. Include your registered phone number and the relevant account step, but do not send your password or full wallet credentials.

Payment privacy check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the receipt reference and date. We can check the payment status while keeping the request focused on the relevant transaction.

Login concern

If a phone verification or device session looks unfamiliar, use the support path beside account access. Tell us the device type and approximate login time so we can review the session without broadening your request.

DATA HANDLING

What We Do With Your Account Details

Privacy at dian4d is handled through practical account steps rather than vague promises. We separate account identity, device activity and payment references so a request can be checked against the right record.

Account details

We may collect your name, phone number, login credentials and account settings when you create or maintain access. These details let us identify the correct account during a privacy request and prevent one person’s records being sent to another.

Device signals

Browser type, operating system, session time and approximate network location can be recorded when you sign in. We use these signals to compare normal access with an unfamiliar device, including a mobile session moving from login to the lobby.

Cookie choices

Cookies can retain session preferences and help us understand which account pages load correctly. You can adjust cookie controls in your browser. Turning some off may require another login or phone check before account access continues.

Payment references

A DANA, OVO, GoPay or QRIS reference may be stored with a receipt status, while bank transfer and virtual account records can show the route used. We use these details to match a transaction without storing unnecessary wallet credentials.

Retention process

We keep account, device and payment records while they support access, security checks, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or separate identifying details under our retention process.

Requesting changes

To request access, correction or deletion, contact us through account help and identify the relevant record. We may ask for a phone verification step before changing account data, so a request does not expose or alter another person’s details.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers cover the questions we expect when you are deciding whether to open an account or checking an existing one. They focus on the records created during phone verification, mobile browsing, payment status checks and support requests. If your situation is not listed, use the account help path and describe the specific data record involved.

The dian4d Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can request access, correction or deletion through account help.

We use your phone number to create and identify your account, complete an account access check and respond to a privacy request. It may also help us compare a new login with your normal device activity before access continues where local law permits.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use receipt status and route details to match the transaction without requesting your wallet password.

You can request a correction through account help. State which record is wrong, such as a phone number or account detail, and complete the requested verification step. We check the request against the account before changing the stored record.

We retain personal data while it supports account access, security checks, payment matching, dispute handling or a legal requirement. After that need ends, we remove the record or separate identifying details according to our internal retention process.

Cookies can preserve session preferences and help pages load consistently on your phone or computer. You can manage them in your browser settings. If some cookies are disabled, you may need to sign in again or complete another phone check.

Use the account help route beside the cashier area and describe the exact request, such as access, correction or deletion. Include your registered phone number and relevant receipt or device details, but never send your password or full wallet credentials.