Reference

Legal access for your dewi15 account

dewi15 Legal sets out how your account, identity details, wallet activity and lobby access are handled before you open an account.

Account clarityPayment checksLocal-law accessData requests
dewi15 Legal access for your dewi15 account
CONTACT ROUTES

Three routes for Legal questions

A clear contact path helps when a Legal question affects your account or wallet status.

Account help Use the account help route when you need clarification about phone verification, access conditions or an account detail connected with Legal. Keep your registered contact detail ready, but never send a password or one-time code in a support request.
Wallet status For a Legal question involving DANA, OVO, GoPay or QRIS, include the payment rail, visible status and receipt reference. We can then separate a policy query from a pending cashier check without asking you to disclose unnecessary wallet credentials.
Policy request Ask through the policy contact route when you want a term clarified, a stored detail corrected or an account request recorded. Quote the section heading or sentence that concerns you, and we will keep the response tied to that Legal point.
DATA PRACTICE

Six controls around account data

Legal handling is practical: we collect what is needed for account access, payment checks, security and support, then use it for those stated purposes.

Account details

We use the details attached to your account to support phone verification, access checks and policy-related replies. Enter accurate contact details, because an unclear account record can delay a request to correct information or change an account setting.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be needed to examine a payment-status question. We use the reference to match the request, not to ask for your wallet password or one-time security code.

Cookies

Cookies and similar browser storage can help keep your account session, policy page state and security checks working across mobile and desktop. Your browser settings control some cookie behaviour, although changing them may affect access to account functions.

Account security

Phone verification and account-detail checks help us distinguish an authorised request from an unknown device or contact. If your phone changes or access looks unusual, use account help before attempting repeated wallet or profile changes.

Retention

We retain account, security and payment-related records for operational needs, dispute handling and applicable legal duties. The relevant period can depend on the record, so contact us if you need a clear explanation of a particular stored detail.

Change requests

You can ask us to correct inaccurate account data, explain a policy decision or address a data-handling concern. State what should change and why, then confirm the account contact detail so we can assess the request safely.

Legal answers before account access

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They focus on local access, account checks, payment records, browser storage and data changes, with practical wording for Indonesian account holders.

Legal covers account access, acceptable account use, phone verification, payment-status checks, data handling, cookies, security, retention and contact requests. It also explains that access depends on local law, so you must check whether your intended use is permitted where you are located.

You may check the account route from Indonesia, but access depends on local law. We do not replace local legal advice. If local rules do not permit the service or your intended activity, do not continue, deposit funds or attempt to bypass an access control.

Phone verification connects an account request to the contact detail you provided and helps us handle sensitive changes safely. It may be relevant before account access or when you request a correction. Never share your one-time code with support or another person.

A payment rail and receipt reference can be used to investigate a wallet-status question. We may match that reference with your account and the cashier record, while avoiding requests for wallet passwords or one-time codes. The available rail remains subject to the displayed account status.

Yes. Use the policy contact route and identify the account detail you believe is inaccurate, along with the correction you seek. We may ask for account verification before changing sensitive records, and we will assess the request against operational and legal requirements.

Cookies or browser storage may keep a policy page state, account session or security check available when you move between mobile screens. You can adjust browser settings, but blocking required storage may interrupt account access or remove details needed for a policy request.

Use the policy contact route and quote the policy heading or decision that concerns you. Add your registered contact detail and any relevant receipt or status reference. We will keep the request focused on Legal and ask only for details needed to assess it.