Reference

Your Privacy Policy starts here

Your account details, wallet status and device choices have a clear place in the wedebos Privacy Policy.

Account data explainedWallet records coveredCookie choices includedContact steps shown
wedebos Your Privacy Policy starts here
PRIVACY HELP

Get help with a privacy request

A privacy question should not get lost beside a payment question. We give you a direct route through account support when you need to ask about stored details, a wallet reference, a…

Account request Ask us to confirm which account details are connected to your sign-in. We may ask you to complete the clear phone verification step before discussing private records, so a request is matched with the right account rather than a similar contact detail.
Wallet record If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt number and approximate transaction date through the account help route. We can compare the status held in our records without asking you to share a wallet password or full secret credential.
Cookie choice For questions about cookies or device storage, tell us whether you used a mobile browser or desktop browser and which account step showed the issue. That detail helps us separate a browser setting from information stored against your account.
DATA PRACTICE

Controls we use for account data

Privacy is handled through practical account steps rather than broad promises. We separate sign-in details from payment references where the process allows, limit staff access to the records needed for a request…

Collection

We collect details needed to open and maintain your account, such as contact information, phone verification status, sign-in events and device signals. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account help us match a transaction without requesting your wallet password.

Cookie controls

Cookies can keep a session active, remember a language or help us understand which account step failed. You can adjust browser cookie settings, although switching them off may require another sign-in. We explain the effect when a cookie choice changes access to a page.

Account security

A clear phone verification step helps us distinguish the account owner from someone using a copied address or device. We do not ask for your wallet PIN or password in a privacy request. If an access detail changes, contact support before sending further documents.

Payment records

A payment reference is used to trace status, investigate a mismatch and connect a cashier event to your account. For example, a QRIS receipt or BCA transfer reference can help us locate the event while the sensitive credentials remain with the relevant bank or wallet service.

Retention

We keep account and transaction records for as long as needed for the stated service, account protection, dispute handling or legal duties. If you ask how long a particular record is retained, include its account step or receipt reference so we can answer about the relevant data.

Change requests

You can ask us to correct an inaccurate contact detail, clarify a stored device record or explain how a request was handled. Send the request from the contact attached to your account when possible. We may verify your identity before making a change to private information.

Privacy Policy questions for Indonesian accounts

These Privacy Policy answers focus on the account actions you are most likely to take at wedebos: opening access, verifying a phone, checking a wallet record, changing a browser setting or asking for a copy of stored details. If your situation is not listed, use the account support route and include enough detail for us to find the relevant record.

It covers account details, phone verification, sign-in activity, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains contact steps for correction, access, deletion where applicable and questions about retention.

Phone verification helps us match a privacy request or account access event with the correct account. It reduces the chance of discussing private records with the wrong person. We will not ask for your wallet PIN or password as part of that verification step.

Yes. Privacy Policy treatment includes the transaction reference and status needed to match a DANA or QRIS event with your account. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. Wallet credentials remain with the relevant provider.

You can request a correction when a contact detail, verification record or other account data appears inaccurate. Send the request through account support from an attached contact where possible. We may verify your identity first, then explain the action taken or why more detail is needed.

Cookies may keep your session active, remember a language or help identify a failed account step. Browser settings let you remove or block them, but you may need to sign in again. If a page behaves differently after a change, tell support which device and browser you used.

Ask through the account support route and state that you want access to the data connected with your account. Include your attached contact detail and, if relevant, a DANA, OVO, GoPay, QRIS or bank reference. We may complete an identity check before sharing private records.

Yes. Account access and any request handling depend on local law. Our Privacy Policy is written for Indonesian access where local law permits, while your bank or wallet provider may apply separate rules to DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.