Reference

irfz44n Privacy Policy For Your Account

irfz44n Privacy Policy sets out how we collect, use and protect the details connected with your account, wallet status and device access.

Account dataWallet recordsCookie choicesPolicy requests
irfz44n irfz44n Privacy Policy For Your Account
CONTACT THE DESK

Privacy Help Beside Your Account Path

A clear contact route helps when you want to ask about Privacy Policy rather than guess which account screen to use. Send your request through the support route shown after login and include the email or phone number attached to your account. We may ask for a transaction reference, wallet name or device detail so we can find the right record without asking you to repeat the whole issue. Support can also explain how to request a correction, access copy or deletion review.

Team online

Account support

Use the logged-in support path for a Privacy Policy question about your phone verification, sign-in record or account details. Include the contact detail linked to your account so we can match the request before discussing personal data.

Wallet status

If your question concerns DANA, OVO, GoPay or QRIS records, add the payment reference and date. We use those details to locate the relevant cashier event while keeping unrelated account activity outside the request.

Request follow-up

For a copy, correction or removal request, tell us exactly which data you mean and how we can reach you. We may confirm account ownership before making a change, especially when the request concerns withdrawal or transfer records.

DATA HANDLING

Inside irfz44n Privacy Controls

Our Privacy Policy follows the account journey from first phone verification through lobby access, wallet activity and support contact.

Account details

We use your name or contact detail, phone verification result and sign-in history to create the requested account path. These records help us distinguish your account from another person using the same device or payment reference.

Device signals

When you open the lobby on a phone or desktop, we may record device type, browser details, approximate access signals and session events. This helps us identify repeated sign-in failures and protect the account without reading unrelated device content.

Cookies

Cookies can keep a session active, remember selected settings and show the correct page after account access. You can manage cookies through your browser controls, although turning them off may interrupt login or return you to the account start step.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may remain attached to the related account event. We use it to reconcile status, answer receipt questions and investigate a mismatch between your wallet and cashier screen.

Retention checks

We keep records only as long as they support account operation, dispute handling, security checks or legal duties that apply where local law permits. When a record is no longer needed for those purposes, we assess it for removal or de-identification.

Account protection

Keep your phone verification details and sign-in credentials private, and contact support if a session looks unfamiliar. We may pause a request while confirming ownership, because changing personal data without that check could expose your account or wallet history.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an irfz44n account from Indonesia. They cover the records connected with your device, account and local payment route, plus the steps for asking us to access, correct or remove data. If your question is not listed, use the logged-in support path and include enough detail for us to identify the relevant record.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and support messages. It explains why we use each category, how we protect it and how you can ask about a record connected with your account.

Phone verification helps us connect the account to the contact detail you provided and reduces confusion during sign-in or a wallet status check. We may use the result when you request account changes, payment clarification or access to personal data.

Yes. The Privacy Policy covers the account-side references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a cashier event, answer a receipt question and investigate a status mismatch.

You can ask for a copy of personal data connected with your account through the logged-in support path. State the records you want, such as phone verification or payment references. We may confirm ownership before sharing account-specific details.

Send a correction request through support and identify the field that appears wrong, such as a contact detail or account record. We may request confirmation before changing it, then check whether the correction affects a related wallet or sign-in event.

You may request removal through the account support route, explaining which data you want considered. We assess the request against active account needs, dispute records and legal duties. Some payment or security records may need to remain where local law permits.

The policy is available for your reference, while account access and eligibility depend on local law. We apply the service where local law permits and can explain how a regional restriction affects a data request through the support path.