Reference

maha303 Privacy Policy for Your Account

Our Privacy Policy explains what maha303 collects when you open an account, verify your phone and move between the lobby and wallet screens.

Clear data purposesWallet detail handlingRequest path explained
maha303 maha303 Privacy Policy for Your Account
HELP WITH YOUR DATA

Privacy Questions Beside Your Account Path

A clear support route matters when a phone check, wallet reference or personal-data request stalls. Start from the account support path and include the email or phone detail attached to your profile, plus the relevant transaction reference if DANA, OVO, GoPay or QRIS is involved. We use those details to locate the right record without asking you to send a full password.

Team online

Account access

If your phone verification blocks sign-in, tell us the device path you used, such as mobile browser or desktop browser. We can separate an access issue from a personal-data request.

Wallet reference

For DANA, OVO, GoPay, QRIS, virtual account or bank transfer records, send the reference and date shown in your account. We use that pair to check the stored payment status.

Privacy request

Ask to access, correct or remove eligible personal details through the account support route. We may confirm account ownership before replying, so your records are not disclosed to another person.

SECURITY IN PRACTICE

What We Do With maha303 Account Records

Our handling steps are designed around the records your account actually creates: phone verification, wallet status, browser activity and support history.

Account details

We use the contact and verification details you provide to identify your account, complete the phone check before access and respond to requests about your stored personal data.

Device signals

A mobile browser or desktop browser may send session, browser and security signals. We use them to recognise unusual sign-in patterns and keep your account path separate from another device.

Cookies

Cookies and browser storage can remember session choices and help us trace loading or sign-in faults. You can manage browser storage settings, though some account functions may then need another check.

Wallet records

DANA, OVO, GoPay and QRIS references help us match a wallet action with the account request. We do not need your wallet password to check the displayed transaction status.

Retention

We keep account, security and transaction records while they serve access, dispute or lawful record needs. When a record is no longer needed, our handling process removes or anonymises it.

Your request

You can ask what personal data we hold, request a correction or ask about removal through support. We verify ownership first and explain any restriction that depends on local law.

Privacy Policy Questions About maha303

These answers address the searches we hear before an account is opened or a wallet is connected. They cover the data behind phone verification, mobile access, payment references and requests to change or remove account records in Indonesia. If your situation is not listed, use the account support path and describe the specific record you want us to check.

It covers account details, phone verification, device signals, cookies, wallet references, support records, retention and requests to access, correct or remove eligible personal data.

Yes. When you use DANA or QRIS, we may store the transaction reference, date and status needed to match the wallet request with your account.

Phone verification helps connect the sign-in attempt to your account and helps us check ownership before discussing personal records or changing account access details.

A mobile or desktop browser may provide session, browser and security signals. We use these details for sign-in protection, technical fault checks and unusual-access review.

You can ask through the account support route for the personal data linked to your profile. We confirm ownership first, then explain the response and any local-law restriction.

Send the requested correction through support and identify the affected account detail. We may ask for phone verification or another ownership check before updating the stored record.

We retain records while they support account access, security, payment checks, disputes or lawful record needs. When those purposes end, we remove or anonymise eligible records.