Reference

Privacy Policy for Your gudang wd Account

gudang wd Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay, or QRIS.

Account clarityWallet recordsCookie choicesPolicy requests
gudang wd Privacy Policy for Your gudang wd Account
REQUEST HELP

Get Privacy Policy Help Near Account Access

A clear request path helps when you want to understand a record rather than change a lobby setting. Contact our account help route with the phone number or account identifier connected to your request, and describe whether it concerns sign-in, a wallet status, a cookie choice, or stored profile data. We may ask for account checks before discussing personal details, so your request is not exposed through an unverified conversation.

Team online

Account data request

Send the account identifier and the specific data question. We use an account check before discussing phone verification, sign-in history, or profile records linked to your gudang wd access.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment reference and date. We can use those details to locate a status record without asking for your wallet password.

Cookie choice

Tell us which device and browser you use if a cookie setting does not behave as expected. Our support path can help separate stored browser data from account records held on our systems.

DATA HANDLING

What Our Privacy Policy Does With Your Data

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account security

Phone verification, sign-in events, and device signals help us check whether an account request matches its normal access pattern. We use these details for security checks, not as a substitute for your account credentials.

Payment references

DANA, OVO, GoPay, and QRIS can return transaction references or status details. Bank transfer and virtual account activity can carry a separate reference, while wallet passwords remain with the payment provider.

Mobile and desktop

Our mobile browser path and desktop path may produce different device, browser, and session records. We use those technical details to maintain account access and investigate a sign-in concern you report.

Cookies

Cookies can remember session choices and help connect a browser visit with an account action. You can review browser controls on your device, although removing cookies may affect sign-in continuity or saved preferences.

Retention questions

We retain records for the period needed for account security, payment reconciliation, support handling, and applicable legal duties. Ask us which category applies to your record and why it remains stored.

Policy changes

If this Privacy Policy changes, we update the policy page and identify the revised subject clearly. You can contact us about a correction, access request, deletion question, or concern about a prior policy version.

Privacy Policy Answers for gudang wd

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account. We cover phone verification, wallet references, browser cookies, device access, retention, and requests for correction or deletion. If your question concerns a specific DANA, QRIS, or account event, include its reference when you contact our account help route.

The Privacy Policy covers personal and technical data connected with your account, including phone verification, sign-in events, device details, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use phone verification to connect an account request with the correct account and to reduce unauthorised access. The record can show whether verification was completed; it does not give us your wallet password or replace your own account credentials.

No. Our Privacy Policy distinguishes payment references and status details from wallet credentials. DANA and QRIS may provide a transaction reference for reconciliation, but your payment password remains with the relevant payment provider rather than being supplied to us.

Use our account help route and provide your account identifier, the data category, and the correction you seek. We may complete an account check first, then explain what can be supplied or amended where local law permits.

On a mobile browser, cookies can keep a session choice or account path available between pages. Clearing them may remove that continuity and require another sign-in step. Your browser controls can manage cookies, while account records remain handled under this Privacy Policy.

Retention depends on the record type and the reason it was created, such as account security, payment reconciliation, support handling, or a legal duty. Ask us about a particular record and we will explain the applicable period where local law permits.

You can submit a deletion question through the account help route with your account identifier and requested scope. We assess the request against security, payment reconciliation, support, and legal retention needs; access depends on local law and the applicable record category.