Reference

mawar28 Privacy Policy In Plain English

mawar28 Privacy Policy explains what we collect when you open an account, verify your phone, sign in from mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
mawar28 mawar28 Privacy Policy In Plain English
CONTACT ROUTES

Ask About Privacy Beside Your Account

A clear contact route helps when you want to understand a data record or change an account detail. Start with the account support path beside the cashier area and state the email or phone number linked to your account. We use that step to locate the correct record before discussing it. If your question concerns a DANA receipt, QRIS status or sign-in device, include the reference and approximate time, but never send a wallet PIN or password.

Team online

Account request

Use the account support path beside the cashier area for a Privacy Policy question. Include your registered phone number and request type, such as access, correction or deletion, so we can match your identity before discussing account data.

Wallet record

For DANA, OVO, GoPay or QRIS records, share only the transaction reference, amount and approximate time. We can check the record connected with your account without asking for a wallet PIN, payment password or full banking credentials.

Device concern

If a mobile browser or desktop sign-in looks unfamiliar, tell us the device type, browser path and approximate access time. We can review the account event, help secure the session and explain which data the event created.

DATA PRACTICES

What We Handle Inside mawar28

We keep the Privacy Policy practical by connecting each data category to an account action you recognise.

Account records

When you open an account, we store the details needed to identify it and keep the registration path working. Phone verification is recorded as an account event before access. We do not need your wallet PIN to confirm that step.

Device signals

A mobile browser or desktop browser may create sign-in, session and device records. These signals help us spot an access pattern that differs from your usual account path. They are reviewed for account protection rather than used to collect wallet credentials.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, status and timestamp to the account flow. Bank transfer and virtual account records can serve the same purpose. We use those details to match receipts and investigate a disputed account event.

Cookie choices

Cookies can remember a session preference, retain a selected language or help us identify a page error. Your browser controls whether some cookies remain. Clearing them may require phone verification again, but it does not erase account records held for valid operational needs.

Retention period

We retain each category while it supports account access, transaction matching, security checks or a legal request. When that purpose ends, we remove or anonymise the record where practical. A support reply can explain why a particular record remains and what happens next.

Your requests

You can ask for a copy of your account data, correction of an inaccurate detail, clarification of a payment reference or deletion where local law permits. Send the request through account support with enough detail to identify your account, and we will verify it first.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect before you open an account or connect an Indonesian wallet. Each answer stays tied to a practical step, from phone verification and mobile browser access to a DANA receipt or a request to change stored data. If your situation is unusual, use the account support path with your registered details.

The mawar28 Privacy Policy covers registration details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can request access, correction or deletion where local law permits.

Phone verification connects your account to a contact detail before access is provided. We record the verification result and related account event to reduce mistaken access and help investigate a sign-in concern. We do not request your DANA, OVO, GoPay or QRIS password.

Yes. The Privacy Policy includes payment references returned during an account transaction, such as a DANA receipt number, QRIS status or timestamp. We use these details to match the account record and check a dispute, while wallet credentials remain with the payment provider.

A mobile or desktop browser can create session details, device signals, browser information and an approximate access time. We use them to maintain the sign-in path and identify unusual activity. You can ask support to explain a specific event linked to your account.

Use the account support path beside the cashier area and provide your registered phone number, the request type and the detail you want checked. We verify account ownership before responding, then explain the available action under the Privacy Policy and local law.

You can submit a deletion request through account support. We first confirm the account and explain which records can be removed or anonymised. Some transaction, security or dispute records may need to remain for a valid operational or legal reason where local law permits.

Cookies can remember a session choice and help us trace a page error, including on a mobile browser. Your browser settings control some cookie storage. Clearing cookies may send you through phone verification again, but it does not automatically remove account or payment records.