Reference

Privacy Policy For Your dewa303 Account

Your dewa303 Privacy Policy explains what we collect when you open an account, connect DANA, OVO, GoPay or QRIS, and access the lobby from your phone.

Account dataWallet recordsCookie choicesSecurity checks
dewa303 Privacy Policy For Your dewa303 Account
CONTACT ROUTES

Help With Privacy Policy Requests

A clear contact path matters when a Privacy Policy question concerns your account or a wallet record. Start from the support route shown after login and include the phone number linked to your account, the relevant date and the request you want us to handle. We may ask for account details before discussing personal data, so your request reaches the correct account holder.

Team online

Account access

If you cannot reach the account area, tell us the phone number used for verification and the device path you tried. We can explain how to submit a Privacy Policy request without asking you to send a password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS record, include the payment rail, date and reference shown in your account. We use those details to locate the relevant data while keeping your full wallet credentials out of the message.

Data changes

To ask for a correction or deletion review, describe the exact account field and explain why it is inaccurate. We may confirm your phone verification first, then tell you what can be changed and what must remain for legal or security reasons.

SECURITY PRACTICE

Six Ways We Handle Your Data

Our Privacy Policy follows the account actions you can recognise: opening an account, verifying a phone number, connecting a wallet and entering the lobby from a device.

Account details

We collect details needed to create and maintain your account, such as your phone number and verification status. We use them to recognise your account during sign-in and to respond to a Privacy Policy request about the correct record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account payment can produce a reference, amount and status. We use those operational details to match activity with your account, not to request your wallet PIN.

Cookies

Cookies and similar browser storage can preserve a session, language choice or security setting. You can manage cookie behaviour through your browser controls, although limiting necessary storage may require another account sign-in.

Device signals

When you open the lobby from a phone or desktop, we may receive device and browser signals used for session protection. These signals help us notice unusual access without reading private content from other applications.

Retention periods

We keep personal data for as long as needed to operate the account, check security events, resolve payment questions and meet applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Policy changes

If this Privacy Policy changes in a material way, we will place the updated wording on this page and show the revised date. You can contact us before continuing account access if you need a point explained.

Privacy Policy Questions Before Opening

These Privacy Policy answers address the searches we hear before an account is opened: what data is collected, how wallet references are used, how access requests work and what happens when you change devices. Read them alongside the full policy wording, then use the account support route if your situation needs a specific response.

The dewa303 Privacy Policy covers account details, phone verification, wallet references, device signals, cookies, security records and retention. It explains why we use each category and how you can ask about, correct or delete personal data where applicable.

We collect the details needed to create your account and complete phone verification, plus sign-in and security records. If you connect DANA, OVO, GoPay or QRIS, payment references and status may also be linked to your account.

Yes. This Privacy Policy covers operational records from DANA, OVO, GoPay and QRIS, including a reference, date and status used to match activity. We do not need your wallet PIN to investigate a payment record.

Use the support route available after login and identify the phone number linked to your account. State that you want a copy of your personal data, and we may complete an identity check before explaining the available records.

You can ask dewa303 to correct inaccurate details or delete data that is no longer needed. We first confirm the request belongs to you, then assess account, security and legal needs before telling you what action is available.

Retention depends on why the record exists. Account and security data may remain while your account is active, while payment or dispute records may need longer handling for legal duties. We remove or de-identify records when no longer needed.

The same Privacy Policy applies when you use a phone, tablet or desktop, although each device can create different session and browser signals. Account eligibility and access depend on local law, including the law applicable in your location.