Reference

mitra77 Privacy Policy For Your Account

Your account details, phone verification, device signals and wallet records are handled under the mitra77 Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesCookie choicesAccount access rights
mitra77 mitra77 Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Your Privacy

A clear contact path matters when you want to check a record, correct an account detail or ask why a cookie appeared.

Account data request Ask us to confirm the personal data connected with your account, such as your phone verification state, login records or saved contact details. We may request an account check before sending any response.
Payment record query For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the payment reference and date. We use those details to locate the receipt without asking for a wallet password.
Cookie support If a cookie setting does not match your choice, contact us through the signed-in support route and tell us your browser and device path. We can assess the setting linked to that session.
SIX DATA CONTROLS

Six Controls Behind Your Data

Our privacy process follows the account journey rather than treating every record alike. We separate identity details from payment references where practical, limit staff access by service need and use security checks…

Collection

We collect account details, phone verification results, device information, login events and payment references because those records help us provide account access, investigate errors and protect the account from misuse.

Cookies

Cookies can remember a session choice, support security checks and measure basic page operation. You can manage browser cookie settings, although changing them may affect login continuity or privacy preferences.

Account security

Phone verification and sign-in event checks help us identify unusual access. Never send a wallet password or one-time code through support; our team uses account details and payment references instead.

Retention

We keep personal and transaction records only for the period needed for account service, security checks, dispute handling and applicable legal duties. When a record is no longer needed, we remove or restrict it.

Your changes

You can ask us to correct an inaccurate name, phone detail or contact record through the account support route. We may retain an earlier value where a transaction or legal record requires an audit trail.

Privacy contact

For a copy request, deletion question, cookie concern or data-use objection, contact us through the signed-in support path. Include your account identifier and request type so we can route it correctly.

Privacy Policy Questions For mitra77

These answers address the practical questions you may have before opening an account or sending a payment reference. They explain the mitra77 Privacy Policy in plain English, including identity checks, device records, cookies, wallet data, corrections and deletion requests.

It covers account details, phone verification, login and device records, cookies, game-session records, payment references and support requests. It also explains why we use each category and how you can contact us.

No. The Privacy Policy concerns transaction references, status, amount and receipt details for DANA, QRIS and other supported routes. We do not need your wallet password to investigate a payment record.

Device type, browser signals and sign-in events help us detect unusual access, protect phone verification and investigate account disputes. These records are used for security and service operation, not to request your private wallet credentials.

Use the signed-in support contact and identify the record that needs correction, such as your phone number or contact detail. We verify the account first and may preserve earlier transaction values for required records.

You can submit a deletion request through the account support path. We assess it under the Privacy Policy and applicable duties; payment, security or dispute records may need restricted retention rather than immediate removal.

Cookies can keep a session choice, remember privacy settings and support security checks. You can change browser controls, but blocking required cookies may interrupt login, phone verification or the account path.

Our data handling explanation applies to accounts using the service, while access and eligibility depend on local law. If you ask about a location-specific restriction, contact support with your account details.