Reference

msg77 Privacy Policy for Your Account Data

The msg77 Privacy Policy shows how we collect, use and protect the data linked to your account, wallet activity and mobile access.

Account dataWallet recordsCookie choicesSecurity steps
msg77 msg77 Privacy Policy for Your Account Data
CONTACT ROUTES

Get Policy Help Beside Your Account

A clear contact path matters when you want to ask about personal data, a cookie choice or a wallet record. Use our support chat from the account area, including the route beside the cashier when a payment receipt needs checking. Tell us the account phone number and the request you want handled, but never send a password or full payment credential. We use the details you provide only to locate the right account case.

Team online

Account chat

Open the support chat from your account area to ask about the msg77 Privacy Policy, stored account data or a request to correct a phone detail. We may ask for a limited account check before discussing records, so your data is not disclosed to the wrong person.

Wallet status

When a DANA, OVO, GoPay or QRIS receipt is attached to your account history, use the cashier-side support path and describe the status you see. We can review the related reference without asking you to share a wallet PIN, password or complete card credential.

Access request

For a copy, correction or removal request, write the exact account phone number and the data action you want through support chat. We confirm account control first, then explain which records can be changed or retained under the applicable local rules.

SECURITY PRACTICE

How We Handle Your Privacy Choices

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Collected data

We may collect your account phone number, verification result, sign-in timestamps, device details and support messages. Payment references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity may also appear when needed to match a wallet status to your account.

Cookie controls

Cookies can remember a session, support account navigation and record a preference on the browser you use. You can manage or clear them through your mobile or desktop browser settings; clearing them may require you to complete phone verification again at the next account access.

Account security

We use phone verification, login records and device signals to help protect account access. Keep your verification code private and sign out on a shared device. If a login looks unfamiliar, contact support chat and include the time shown in your account history.

Retention period

We keep each data type only while it supports the stated account, security, support or transaction purpose, unless a legal requirement calls for longer storage. When retention ends, we remove or separate the record through our operating process rather than keeping it indefinitely.

Your choices

You can ask us to access, correct or delete eligible account data, and you can ask why a particular record is used. We may need to verify account control before acting. Some records cannot be removed immediately when they are needed for security or a legal duty.

Policy contact

Use the support chat linked to your account to raise a privacy question or request a policy change. Include the relevant account step, such as phone verification, cookie setting or wallet receipt status, so we can route the request without collecting unrelated personal details.

Privacy Policy Answers for msg77

These Privacy Policy answers cover the searches we hear most often before account access. They explain what data may connect to your account, how wallet references are handled, what happens on a mobile browser and how to contact us when you want a correction or access request. If your question is not listed, support chat can route it to the right account case.

The msg77 Privacy Policy covers account creation, phone verification, login and device records, cookie choices, support messages and payment references. It also explains retention, security practices and your routes to request access, correction or deletion where that action is available under applicable rules.

We can collect the phone number used for your account, verification results, login timestamps, device signals, browser cookie preferences and messages sent to support. If you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, related transaction references may be recorded for status matching.

Phone verification helps us connect an account request with the correct account holder and reduce mistaken disclosure. It can also support account security when a login or device looks unusual. Keep each code private, and contact support chat if you did not request a verification message.

We use wallet and payment references to match a status or receipt with the correct account, not to request your private wallet PIN. The same approach applies to OVO, GoPay, bank transfer and virtual account references. Share only the receipt details support asks for.

Yes. Send the request through the account support chat and state whether you want access to a record or correction of a detail. We first confirm account control, then explain the result and any records that must remain stored for security or legal reasons.

Open the browser settings on the phone you use to access the account, then manage or clear site cookies there. A change may end the current session or require phone verification again. Our support chat can explain the account effect without asking for your browser password.

The page is available for you to read before opening an account, while account access and related eligibility depends on local law. Where local law permits, we apply the data choices described here; if a local rule changes the process, support chat can explain the relevant route.