Reference

Privacy Policy for m1911 Account Access

m1911 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support team.

Account dataDevice signalsWallet recordsSupport requests
m1911 Privacy Policy for m1911 Account Access
CONTACT DATA DESK

Get Privacy Help Through Support

A direct support route helps you ask about the Privacy Policy without sending account details through public channels. Our team can explain which record is involved, confirm the account step needed to verify your identity and route a correction or access request to the right internal team. Contact us through the support channel shown on the m1911 site, or use the account help path beside the cashier when your request concerns DANA, OVO, GoPay, QRIS or a bank transfer. Requests are handled during the support hours displayed on the site, with replies tied to your account contact details.

Team online

Account data requests

Ask us to identify the personal details attached to your account, such as your phone number, verification record or support history. We will ask for an account check before disclosing anything, so a request cannot be completed solely from an unverified message.

Wallet record questions

For DANA, OVO, GoPay, QRIS or bank transfer records, include the transaction reference and approximate time shown in your account. We use those details to locate the payment event while avoiding requests for your wallet PIN, password or full banking credentials.

Correction and deletion

Tell us which personal detail is wrong or which request you want assessed. We may retain a limited record when it is needed for account security, payment reconciliation or a legal duty, and we will explain that reason through the verified support path.

HANDLING YOUR RECORDS

How m1911 Handles Privacy Requests

Our Privacy Policy is applied through practical account and support steps rather than a broad promise.

Account security checks

Before we disclose, change or remove account data, we may confirm your phone verification and ask for a recent account step. This protects the details connected with your login and reduces the chance that another person can redirect a privacy request.

Device and sign-in data

A phone or desktop session can create records such as browser type, operating system, connection details and sign-in time. We use these signals to spot unusual access around the account, and they are not treated as your wallet password or banking credential.

Cookies and preferences

Cookies can keep a session active, remember a selected setting or help us understand a failed page visit. You can remove or restrict them in your browser. Some account functions may then ask you to sign in again or repeat a preference.

Payment status records

When you use QRIS, DANA, OVO, GoPay, virtual account or bank transfer, we may receive a reference, amount status and time from the payment route. We use this to reconcile your account, while your wallet PIN stays with the payment provider.

Retention by purpose

We retain account, support and transaction records only while they serve security, reconciliation, dispute handling or a legal duty. Once a purpose ends, we remove the record or separate it from direct account identifiers where that approach is practical.

Requesting a policy change

Send a correction, access, restriction or deletion request through the verified support path shown on the site. Include the account contact and the specific record involved. We will confirm the next account step and explain any reason a record must remain.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what data is involved, why a verification step may appear and how to reach us when a payment record or device event needs checking. The same support path applies whether you connect from Jakarta on a phone or use a desktop browser. Account access and any request outcome depend on local law, and we will explain the applicable next step through the contact details linked to your account.

We use your phone number to create and protect your account, complete phone verification and send account-related support replies. It can also help us match a privacy request to the correct account. We do not ask you to disclose a DANA, OVO or GoPay wallet PIN.

Yes. Contact us through the verified support route and ask for an account data access request. We may confirm your phone verification and a recent account step before responding. The response can cover account details, device records, support history and payment references held for your account.

We may receive a payment reference, status, timestamp and related account match for QRIS, bank transfer or virtual account activity. This allows us to check whether a record belongs to your account. Your bank password, wallet PIN and private banking credentials remain outside our requested data.

Device type, browser details, connection data and sign-in time help us identify unusual account access and investigate a failed session. A phone session in Jakarta and a desktop session can create different security events. We use these signals for account protection and support, not as wallet credentials.

You can request a correction or deletion through the verified support path, naming the record and the change needed. We will assess the request under local requirements. Some security, payment reconciliation or dispute records may need to remain, and we will explain that reason.

Retention depends on why the record exists. Account security events, support cases and payment references may remain while needed for protection, reconciliation, dispute handling or a legal duty. After that purpose ends, we remove the record or separate it from direct identifiers where practical.

Yes. Account access, data requests and the way we handle certain records depend on local law and are available where local law permits. Use the support channel connected to your account for a case-specific answer, and include the relevant verification or payment reference.