Reference

Privacy Policy for Your dewajudi Account

dewajudi's Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS for wallet…

Account dataDevice checksWallet recordsCookie choices
dewajudi Privacy Policy for Your dewajudi Account
REQUEST A HAND

Get Policy Help Beside Your Account

A clear contact route matters when a Privacy Policy question concerns your phone verification, a wallet reference or an old account record. We ask you to contact support through the account help path and include the email or phone connected to your account, the relevant date and the request you want us to assess. This helps us locate the correct record without asking you to send a password, wallet PIN or full payment credentials.

Team online

Account privacy request

Use the account support path for a copy, correction or deletion request under our Privacy Policy. Include your registered contact detail and a short description of the record involved; we may ask for an account check before discussing personal data.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the transaction date and visible reference through support. We compare the account record with the payment status and avoid requesting your wallet PIN or complete bank credentials.

Access concern

When a phone verification or device check blocks access to policy controls, tell us which sign-in step stopped and whether you used mobile or desktop. We use that detail to route the request without exposing another account's data.

DATA CONTROL ROOM

What We Do With Your Personal Data

We keep the Privacy Policy practical by tying each handling purpose to an account action you can recognise: sign-in, phone verification, wallet reconciliation, support or a policy request.

Account details

We use your name, phone number, email and verification status to create and protect the account you asked us to open. Keeping these details current helps us send an access response to the right contact and separate your records from another account.

Device signals

A sign-in from a mobile phone or desktop can produce device and session signals linked to security checks. We use them to identify unusual access patterns and investigate account concerns, not to request sensitive content stored on your device.

Cookies and settings

Cookies may remember a language choice, session state or policy preference so you do not repeat the same step on each visit. You can manage browser cookie controls, although removing some cookies may affect sign-in and saved settings.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the references needed to match a status with your account. We do not need your wallet PIN, and you should never place it in a support request.

Retention periods

We retain account, security and transaction records only for the period needed for the stated purpose, dispute handling and applicable legal duties. A deletion request may not remove records that we must preserve, but we explain the reason for any limit.

Your contact rights

You can ask us to access, correct or delete eligible personal data, or question a handling purpose described here. Send the request through account support with enough detail to locate your record; we verify ownership before making a change.

Privacy Policy Answers for dewajudi

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening an account. They explain what we need, what you can request, and how local access wording affects our handling of records. If your situation is not covered, contact us through the account support path with a specific question.

It covers personal data connected with your account, including contact details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains our purposes, retention approach, security handling and the requests you can send about eligible records.

Phone verification helps us confirm that the person requesting account access controls the registered contact detail. We record the verification result and related account event so we can protect sign-in and investigate access concerns. Eligibility and access depend on local law.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use these details to match activity, answer a status question and handle disputes without asking for a wallet PIN.

You can ask for access to eligible personal data or request a correction through the account support path. Tell us the registered contact detail and which record seems wrong. We may verify account ownership first, and a legal retention duty can limit deletion.

On a mobile browser, cookies can keep a session active, remember a setting or record a policy choice where permitted. You can adjust cookie controls in your browser. Removing them may require another sign-in or remove saved preferences from that device.

We keep each record for the period needed for its stated purpose, account security, dispute handling and applicable legal duties. The period can differ by record type. If you request deletion, we explain when a required retention period prevents immediate removal.

Use the account support path and state that your request concerns the Privacy Policy. Include your registered email or phone, the relevant date and the action requested. Do not send a password, wallet PIN or complete bank credentials; we will verify ownership safely.