Reference

Privacy Policy For Your dewi15 Account

Clear account, wallet and device data rules help you decide how to use dewi15.

Account dataWallet recordsCookie choicesAccess requests
dewi15 Privacy Policy For Your dewi15 Account
CONTACT PATHS

Three Ways To Ask About Privacy

Privacy questions should not get lost beside a wallet status issue. We keep the account help path close to the cashier area so you can identify the relevant account, payment or device…

Account access Use the signed-in account help path for a Privacy Policy question about phone verification, an email or phone detail, login records, or a correction to your account profile. We may ask you to confirm account ownership before discussing personal data.
Wallet status For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, start from the cashier-linked support path. Include the status reference and time shown on your account, not a wallet password or full security code.
Access request Ask through the same support path when you want a copy, correction or removal request handled under this Privacy Policy. We check the request against your account details before changing or releasing information tied to you.
HANDLING DETAILS

Six Controls Behind Our Privacy Policy

The practical side of privacy is visible in ordinary account steps. We separate identity checks from wallet status, limit internal access to account records and keep policy requests tied to a traceable…

Account collection

We collect the details needed to create and maintain your account, including contact details and the phone verification step before account access. If a field is not needed for that task, our policy does not present it as a required account detail.

Payment matching

A wallet or bank record is matched to the account reference used for the request. This helps us investigate DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI status without asking you to share a wallet password.

Device signals

A phone browser and a desktop session can create device and access records such as session time, browser details and security events. We use these signals to detect unusual access and to keep a policy request connected to the right account.

Cookies

Cookies can remember a session, support account navigation and help us understand which policy page is being opened. Your browser settings provide a way to manage cookies, although disabling some may affect login or account-area functions.

Retention

We keep account, payment and support records only for the period needed for the purpose described in this Privacy Policy, account protection and applicable legal duties. A retention question can be sent with the relevant account reference.

Security requests

If you suspect an account detail is wrong or access was not yours, contact us through the account support route promptly. We may verify ownership, restrict discussion to the affected record and document the action taken.

Privacy Policy Questions For Indonesia

These answers cover the questions we expect before you open an account or connect a local wallet. They focus on the dewi15 Privacy Policy rather than general lobby features, so you can see what data is involved and which account step to use when you need help.

The dewi15 Privacy Policy covers account creation, phone verification, lobby access records, wallet and bank references, device signals, cookies, retention and requests to access or correct your data. It applies when you use the service from Indonesia where local law permits.

Phone verification helps connect account access to the person creating the profile and supports account protection. It also gives us a way to check ownership before discussing personal data, changing account details or handling a Privacy Policy request.

It can record the account reference, status and timing connected with a DANA, OVO, GoPay or QRIS request. Bank transfer and virtual account references may also be retained for tracing and account support. We do not need your wallet password for that check.

Yes, you can send a data access request through the account support path. Tell us which record you need, such as profile, device, cookie or payment activity. We verify account ownership first and may limit disclosure where a legal or security reason applies.

Start with the account help route and identify the field that needs correction. We may ask you to complete phone verification or provide another ownership check before changing it. The request is handled under this Privacy Policy and linked to your account record.

Retention depends on why the record exists, including account protection, payment tracing, support handling and applicable legal duties. The Privacy Policy does not treat every record alike. Ask us to confirm the period for a specific DANA, QRIS, bank or virtual account reference.

Yes. Ask through the account support path and identify whether your question concerns cookies, a phone browser, a desktop session or an unusual login signal. You can also adjust browser cookie settings, though some account-area functions may then work differently.