Reference

dewi311 Privacy Policy for Your Account

Our Privacy Policy explains how dewi311 handles the details you provide when opening an account, confirming your phone number and using DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
dewi311 dewi311 Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Policy Help Beside Account Support

A clear contact path matters when you have a question about personal data rather than a lobby title. Tell us which account step concerns you, such as phone verification, a DANA receipt or a QRIS status, and include only the details needed to locate the record. We use the account support route for privacy requests so the conversation stays connected to the correct profile. Do not send a password or full wallet credentials in a message.

Team online

Account data request

Ask us to confirm the data linked to your account after phone verification. We may request account identifiers before responding, so we do not disclose private details to the wrong person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks incorrect, include the date, rail and visible receipt reference. We use those details to locate the relevant payment record without asking for your wallet password.

Policy change request

You can ask for a correction, removal or explanation of personal data through account support. We will explain any record that must remain for security, dispute handling or a legal duty.

SECURITY IN PRACTICE

What We Do With Your Personal Data

We keep this Privacy Policy practical by connecting each data use to an account action.

Account creation

When you open an account, we collect the details needed to create your profile and begin phone verification. We use them to provide account access and connect later support or wallet questions to the correct record.

Phone verification

A verified phone step helps protect account access from mistaken or unauthorised sign-ins. If your number changes, contact support before creating another profile so we can address the existing account record.

Device sessions

Our security checks may use browser, device and session signals when you move between mobile and desktop. These signals help us spot unusual access without treating your device details as a marketing message.

Cookies and storage

Essential cookies can keep a session active and remember choices needed for account access. Where browser controls support it, you can clear or restrict non-essential storage, although some account steps may then need repeating.

Retention periods

We retain personal data for as long as its purpose requires, including account security, payment matching, support history, disputes or legal duties. When a record no longer needs retention, we remove or anonymise it through our data process.

Correction and access

You may ask what personal data we hold, request a correction or ask about deletion. We first verify the request, then explain the result and any reason a specific record must remain.

Privacy Policy Questions About dewi311

These answers address the searches we hear most often about the Privacy Policy. They cover account details, local wallet records, cookies, device access and requests to change stored data. If your situation involves a payment reference or an account you can no longer access, use the support path above and share the smallest useful set of details.

It covers data connected with account creation, phone verification, sign-in, device sessions, cookies, support messages and payment references. That includes records related to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when you use those rails.

We use your phone number for account creation and verification, helping connect access to the correct profile. It can also help support locate your account when you ask about a sign-in issue or a wallet receipt. Do not send your password with a request.

Yes. The Privacy Policy covers payment references and status details associated with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use those records to match receipts, investigate status questions and protect account activity, not to request your wallet password.

Contact account support and state that you want an access request under the Privacy Policy. Include the account identifier you can safely share. We may verify your identity or phone connection first, then explain which data we hold and how it is used.

You can request a correction or deletion through the account support route. We check the request before changing anything and explain if a record must remain for account security, payment matching, dispute handling or a legal duty. Removal also depends on local law.

Essential cookies may keep your session working and preserve account access choices. Browser controls can let you clear or restrict other storage where available. If you remove essential cookies, you may need to repeat phone verification or sign in again.

Yes. Our handling of access, retention and deletion requests depends on local law and applies where local law permits. If you are in Jakarta or another Indonesian location, contact support with your account question so we can explain the applicable request path.