Reference

mampir4d Privacy Policy for Your Account

Our Privacy Policy explains how mampir4d handles the account details, device signals and wallet records connected with your access.

Account dataWallet recordsMobile accessPolicy requests
mampir4d mampir4d Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Account Data

A clear contact path matters when a Privacy Policy request concerns a phone number, wallet reference or sign-in record.

Account access If a phone verification step blocks access, tell us the account identifier and device…
Wallet status For a DANA, OVO, GoPay or QRIS data question, provide the payment label and…
Policy request Ask through the support route beside the cashier path when you need a copy…
DATA PRACTICE

How mampir4d Handles Device And Wallet Data

We apply the Privacy Policy to the practical records created during account access, payment checks and support conversations.

Account details

We use the contact details and phone verification result you submit to create, secure and locate your account.

Device signals

A mobile browser or desktop browser can send device type, session timing and security signals.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment-status question.

Cookie choices

Cookies and similar browser storage can keep your session working and remember selected access settings.

Account security

We use phone checks, session controls and access logs to protect your account.

Retention requests

We keep records only for operational, security or legal reasons described in the Privacy Policy.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the questions we expect before you open an account or contact support. They cover wallet references, browser access, phone verification and requests for changes. If your case involves a specific DANA, OVO, GoPay or QRIS record, use the support route beside the cashier path so we can check the right account context.

The mampir4d Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references, support messages, retention and requests to correct or assess removal of personal data.

We may process a DANA or QRIS reference to match a payment-status question with your account. We use the reference for reconciliation and support, not as a request for your wallet PIN or password.

Yes. The Privacy Policy covers OVO and GoPay references connected with an account request. We use the payment label and transaction context to investigate status questions while avoiding unnecessary wallet credentials.

When you sign in through a mobile browser, we may receive device type, browser details, session timing and security signals. These records help us identify unusual access and explain phone verification issues.

Use the account support route beside the cashier area and identify the account step involved. We may ask for account verification before correcting a phone number, contact detail or linked record.

We retain personal data for the operational, security or legal period described in the Privacy Policy. You may ask what remains connected with your account and request a deletion assessment.

Account access depends on local law and is available where local law permits. Our Privacy Policy does not override local eligibility rules, so check your position before submitting account or wallet details.