Reference

wedebos Privacy Policy For Your Account

Our Privacy Policy explains what wedebos collects when you create an account, verify your phone, use the mobile lobby or contact support.

Clear collection rulesWallet record detailsAccess request stepsCookie choices
wedebos wedebos Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when your account record, phone verification or wallet status needs attention.

Account privacy request Ask us to explain, correct or access account details through the support route linked…
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction…
Access and deletion query If you want a copy, correction or removal of eligible data, state the request…
DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each rule to an account action you can recognise.

Account details

We may hold your phone number, verification status, login events and messages sent through support.

Cookie controls

Cookies and similar device records can keep a mobile browser connected to an account session and remember selected settings.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, amount status and time so we can match a wallet action.

Account security

Phone verification before account access helps us identify the account connected to a request.

Retention periods

We retain different records for different reasons: account operation, security checks, payment reconciliation, dispute handling or legal duties.

Changes and contact

To request access, correction or an eligible removal, use the support route in your account area and describe the data…

Privacy Policy Answers For wedebos

These Privacy Policy answers focus on the account steps that matter before you open an account from Indonesia. We explain the data connected to phone verification, mobile browser cookies, wallet references and support requests, along with the route for asking about access, correction or removal. If a rule depends on location or legal requirements, we apply it where local law permits.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, how long records may remain, and how you can request access or correction.

No. We do not ask you to send a DANA, OVO, GoPay or QRIS PIN through support. We may receive a transaction reference, status and time to match an account action, while your wallet credentials remain with the relevant payment service.

Phone verification helps us confirm that a request concerns the correct account before we disclose private details. If you ask for an account copy, correction or eligible removal, we may use the phone number already connected to your account for that check.

Cookies can keep a mobile browser connected to your account session and remember selected settings. You can clear or restrict them in your browser controls. After that change, you may need to complete login and phone verification again before account access.

Yes, you can request a correction through the support route shown in your account area. Name the field that is wrong, such as a phone number, and explain the requested change. We may verify your account first and explain any legal restriction.

Retention depends on why a record is needed. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain for reconciliation, security, dispute handling or legal duties. We remove or separate records when those purposes no longer require them where applicable.

Use the support link in your account area and write the specific Privacy Policy question, such as data access, cookie use or a wallet reference. Include your account phone number only through that route, and never send a password or wallet PIN.