Reference

wdyuk Privacy Policy For Your Account

Our Privacy Policy shows how wdyuk handles the details connected with your account, wallet activity and device access.

Clear data purposesWallet record detailCookie choicesAccess request path
wdyuk wdyuk Privacy Policy For Your Account
CONTACT FOR CLARITY

Where To Ask About Your Privacy Policy

A direct support route helps you resolve a data question without guessing which team handles it. Tell us the account email or phone number, the subject of your request, and the relevant wallet reference when one exists. We use those details to locate the right record while limiting unnecessary disclosure. If your question concerns a mobile login, cookie setting, payment receipt or account correction, describe the exact step that caused concern. We will use the available support path linked to your account and assess the request under this Privacy Policy.

Team online

Account data request

Ask us which personal details are connected to your account and why they are held. Include your registered phone number or email so we can check identity before discussing records, without asking you to send a password or full wallet credentials.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt concern, share the transaction reference and date rather than screenshots containing unrelated details. We can trace the account event, explain its status and keep the request focused on payment data.

Cookie or access help

If a mobile browser keeps an old session or a cookie choice does not behave as expected, tell us your device path and browser action. We can explain the setting, identify the relevant record and route a correction request.

DATA HANDLING DETAIL

Six Practical Privacy Controls We Use

Privacy is part of the account steps you see, not a statement kept away from the cashier path.

Account creation

When you open an account, we collect the details needed to create your profile and provide access. Phone verification is an account step before access, so we can match the request to the correct person without relying on a shared device alone.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create operational records. We use references, status results and related account details to reconcile a receipt, investigate a mismatch and reduce repeated payment questions.

Cookies

Cookies may keep a session active, remember a selected setting or help us identify a page function that is not working. On a mobile browser, clearing cookies can sign you out and remove saved preferences, so check your account path afterward.

Account security

We use account details and sign-in events to identify unusual access and protect your profile. Never send us your password or a complete wallet credential. If your phone changes, contact support through the account route before asking for profile changes.

Retention

We retain account, security and payment records only for the operational, dispute and legal reasons that apply to the request. When a record is no longer needed for those reasons, our handling follows the applicable retention process and local law.

Changes and access

You can ask for a copy of relevant personal data, a correction, or an explanation of its use. Include your account identifier and a clear request. We may verify ownership first, then respond with the available action or reason for a limitation.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions that arise before and after account access: what data is collected, how wallet references are used, what happens on a phone, and how to request a change. We keep the language practical so you can decide what to share and where to ask for help. Account access and eligibility depend on local law.

It covers account details, phone verification, sign-in events, cookies, payment references and support requests connected with your use of wdyuk. It also explains retention, security handling, access requests and correction requests for Indonesian accounts where local law permits.

We may collect the details needed to create and secure your account, including contact details, phone verification results, device or session events, and records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

A wallet or QRIS reference lets us connect a payment event to the correct account, receipt and status result. We use that operational detail to reconcile a request or investigate a mismatch, rather than treating the payment rail as a separate profile.

Yes. Send a clear access request through the available account support route and include your registered phone number or email. We may verify account ownership before sharing details, and the response or any limitation will follow applicable local law.

Tell support which account detail is inaccurate, what the correct detail should be, and why the change is needed. For a wallet receipt, include its reference and date. We will check the record and apply or explain the available correction.

Cookies can preserve a mobile session, remember a setting and help identify page problems. Clearing them may sign you out or remove preferences. If access changes afterward, tell us the device path and browser action so we can assist.

Retention depends on why a record exists, such as account security, payment reconciliation, a dispute or a legal requirement. We keep it for the applicable operational period, then follow the relevant disposal process where local law permits.