Reference

Privacy Policy for Your iron388 Account

Our Privacy Policy explains what we collect when you open an iron388 account, how we use account and wallet records, and how you can ask about your data.

Account clarityWallet recordsCookie choicesPolicy requests
iron388 Privacy Policy for Your iron388 Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact route helps you resolve a Privacy Policy question without repeating your account story. Start from the signed-in account help path when your request concerns phone verification, a wallet reference or a login record. If you cannot sign in, use the contact route shown on the iron388 site and include the email or phone detail linked to your account. We will ask for enough information to locate the record while avoiding unnecessary disclosure in your message.

Team online

Account help path

Use the account help path for a Privacy Policy request connected to phone verification, sign-in history or a change to your contact details. We can check the account record after confirming that you control the relevant account.

Wallet status query

Mention the affected rail, such as DANA, OVO, GoPay or QRIS, when your question concerns payment data. A reference or status detail helps us locate the record without asking you to send a full wallet password or secret code.

Site contact route

If account access stalls, use the contact route displayed on our site and write that your request concerns the Privacy Policy. Include your linked contact detail, device type and request type so we can direct it correctly.

DATA PRACTICE

Six Details Behind Our Privacy Handling

We keep the Privacy Policy practical by tying each data use to an account task. Phone verification supports account access; device signals help identify unusual sign-in behaviour; wallet…

Account collection

When you open an account, we collect the details needed to create and maintain that account, including contact data and…

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain rail selection, reference details, status and…

Device signals

A mobile browser or desktop session can create technical signals such as browser type, device details and sign-in time.

Cookies and sessions

Cookies can keep your sign-in session active, remember necessary settings and help us understand whether the Privacy Policy page loads…

Security checks

We may compare account details, phone verification and transaction references before changing sensitive records or answering a data request.

Retention and changes

We keep records only for the period connected to their account, security, support or legal purpose, then assess whether they…

Privacy Policy Answers for iron388

These Privacy Policy answers address the account questions you may have before opening an account or sending a wallet request. We explain the practical route for checking data, changing details, managing cookies and contacting us. Access and any related account action depends on local law, and we may confirm your identity before discussing a personal record.

The iron388 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and wallet records. It also explains how we use, retain and protect those records, plus how you can request access, correction or deletion where local law permits.

We collect the contact and account details needed to create your account, including phone verification status. When you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes, we may also record the selected rail, reference details and transaction status.

Our Privacy Policy treats payment details as account and transaction records. We use rail names, references, status changes and related messages to match activity to your account. Do not send wallet passwords or one-time codes in support messages; those are not needed for a policy request.

Yes, you can contact us through the signed-in account help path or the site contact route and ask for a data-access response under the Privacy Policy. Include your linked phone or email detail. We may verify account control before sharing account-specific records.

Send a correction request through account help and identify the detail that needs changing, such as a contact record or phone verification entry. We may ask for confirmation before editing it, and the available action depends on local law and the record type.

On a mobile browser, cookies can maintain a sign-in session, remember necessary settings and help the Privacy Policy page load consistently. You can change cookie controls in your browser. Blocking necessary cookies may interrupt account access or require you to sign in again.

We retain each record for the period connected to its account, security, support or legal purpose. Retention can differ for phone verification, QRIS references and support messages. You can ask us to explain a record's retention context through the Privacy Policy contact route.