Reference

magis4d Privacy Policy for Your Account

Your magis4d Privacy Policy gives you a clear view of how we handle account details, device activity and wallet records before you open an account.

Account dataCookie choicesWallet records
magis4d magis4d Privacy Policy for Your Account
CONTACT ROUTES

Contact magis4d About Your Privacy Policy

A direct support route helps you ask what data we hold, why it appears on your account, or how to correct a detail.

Account privacy request Ask our support desk to explain account data connected to your phone verification or…
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the transaction reference and status…
Correction route If your name, phone detail or contact preference is inaccurate, contact us through the…
DATA PRACTICE

Data Choices Behind This Privacy Policy

We keep the policy practical by separating account access, payment records and security signals rather than treating every detail alike.

Account data

We handle details such as your phone number, account identifier and verification state to create access and respond to account…

Cookies and devices

Cookies and browser signals can keep a mobile session connected to the correct account and help detect unusual sign-in behaviour.

Security checks

Phone verification and sign-in signals help us protect your account.

Payment records

A DANA, QRIS, bank transfer or virtual account request can leave transaction references and status details.

Retention approach

We retain account and transaction records only for the operational, security and legal purposes described in the policy.

Your requests

You can ask for access, correction or clarification through the account support route.

Privacy Policy Questions About magis4d

These Privacy Policy answers cover the account steps you are most likely to question before registration or a wallet request. We keep the wording tied to actual records, including phone verification, mobile browser sessions, QRIS references and support-led data requests.

It covers account details, phone verification, device and cookie signals, support messages, and payment references created through DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify account access, connect support requests to the correct profile, and help detect unusual sign-in activity. Do not send your password with a request.

Yes. The Privacy Policy covers references and status records connected with QRIS, DANA, OVO and GoPay requests. It does not require you to disclose a wallet PIN to our support desk.

Use the support path in your account area and state that you want an account data request. Include your account identifier or verified phone detail; we may confirm ownership before responding.

Yes. Send a correction request through account support and identify the inaccurate name, phone detail or contact preference. We may complete a verification step before changing data tied to account access.

Cookies can preserve a mobile browser session and support security checks. If you block them, login or phone verification may need repeating, and some account functions may not work as intended.

Yes. Our response to an access, correction or deletion request depends on local law. We explain the applicable result through the support route and may retain records where a stated duty applies.