Reference

Privacy Policy for Your momos55 Account

Our Privacy Policy explains how we collect, use and protect details connected with your momos55 account, from phone verification to wallet status.

Account dataWallet recordsCookie choicesAccess depends on local law
momos55 Privacy Policy for Your momos55 Account
PRIVACY HELP DESK

Where To Ask About Your Data

A clear support path matters when you want to understand a privacy decision or correct an account detail. We direct privacy requests through the support channel available after you sign in, so the request can be linked to the right account without asking you to post personal details publicly. If login is stalled, use the account access route on the site and include only the minimum detail needed for us to locate the request. In Yogyakarta and elsewhere in Indonesia, the same account support path handles questions about wallet records, cookies and phone verification.

Team online

Account support

Use the signed-in support channel to ask what account details we hold, why phone verification is needed or how to correct a spelling error. Keeping the request inside your account helps us check identity before discussing records connected with DANA, OVO, GoPay or QRIS.

Wallet record help

If a wallet status or QRIS reference looks wrong, send the transaction date and account reference through support rather than sharing a receipt in an open chat. We use that limited trail to compare the account ledger with the payment request and explain the next privacy step.

Access assistance

When you cannot reach the account page, follow the sign-in recovery path and mention that your request concerns the Privacy Policy. We will use the details needed to confirm ownership, then point you to the relevant data request route without asking for an unnecessary password.

DATA HANDLING

What We Do With Your Personal Details

We handle privacy requests as account operations, not as a generic statement detached from the way you use the site.

Collection

We may collect your phone number, account identifiers, sign-in records, device details and payment references when you open or use an account. A DANA, OVO, GoPay or QRIS reference helps us match a request; it does not mean every wallet detail is stored in the same account record.

Use of data

We use account and transaction details to provide access, confirm phone verification, answer support requests, detect an account mismatch and process a data correction. We do not turn a Privacy Policy request into a marketing message, and we keep the purpose tied to the service action you asked us to handle.

Cookies

Cookies and similar device markers can keep your sign-in path working, remember a selected language setting and help us understand whether a page loads correctly. You can manage browser cookie controls on your Android phone, iPhone or desktop, although disabling some cookies may affect the account access path.

Account security

We protect account changes with sign-in checks and phone verification before discussing sensitive records. Never send us your password or a complete wallet security code. If a login from an unfamiliar device appears, change your password through the account path and contact support with the event details.

Retention

We retain records only while they serve an account, payment tracing, security or legal purpose, then review whether they still need to be kept. A QRIS receipt or bank transfer reference may remain longer than a temporary device session when it is needed to resolve a transaction question.

Changes and requests

You can ask us to access, correct or clarify personal details through the signed-in support route. State the account email or phone reference, describe the requested change and avoid sending extra documents until we ask. We may verify ownership before changing records or releasing account data.

Privacy Policy Questions Before Access

These Privacy Policy answers address the questions we expect before you open an account or send a data request. They explain the account step, device behaviour, wallet references and contact route without shifting into a general description of the lobby. If your situation is not covered, sign in and use the support channel attached to your account so we can check the relevant record.

It covers account creation, phone verification, sign-in and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. It also explains how to ask for access, correction or clarification of personal details.

We use your phone number as part of the account verification path and to help distinguish your account from another request. Before discussing sensitive records or changing access details, we may ask you to complete a verification step. Do not send your password or security code.

Yes. The policy covers payment references and wallet status used to match an account request, including DANA and QRIS. We may also check OVO, GoPay, bank transfer or virtual account references when support needs to trace a transaction, but we request only details relevant to that check.

Cookies can keep your sign-in path active, remember selected settings and help us identify a page-loading problem on Android or iPhone. You can control them in your browser. If you block required cookies, parts of the account path may ask you to sign in again.

Sign in and use the account support channel, then state which detail needs correction and provide the account phone or email reference. We may verify ownership before making a change. Avoid sending a full identity document, password or wallet security code unless support specifically requests a suitable check.

We keep payment references while they support account service, security, transaction tracing or a legal requirement. A temporary device session may be removed sooner, while a bank transfer, virtual account or QRIS reference can remain when it is needed to resolve a payment question.

Use the support route shown after you sign in and label the request as a Privacy Policy question. Include the account reference and a short description of the issue. If you cannot sign in, use the account recovery path and provide only enough detail for us to verify ownership.