Reference

ilmutoto Privacy Policy For Your Account

Our Privacy Policy gives you a clear view of how account details, device signals and wallet references are handled when you use ilmutoto.

Account data explainedWallet details separatedCookie choices includedContact route available
ilmutoto ilmutoto Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Account Access

A direct support route helps you ask what we hold, why we use it or how to correct an account detail. Send your request through the account help contact shown on our site, and include the phone number linked to your profile without sharing a password or wallet PIN.

Team online

Data questions

Ask which account, device or payment-status records relate to your profile. We use the phone number on your account to locate the request and may ask for an account step to confirm it is yours.

Correction requests

If your phone number or account detail needs changing, contact us through the account help path. We check the request before updating records, so another person cannot alter your profile through an unverified message.

Wallet status concern

For a DANA, OVO, GoPay or QRIS reference that appears incorrect, send the payment receipt and status detail through support. Remove wallet PINs and unrelated private credentials before sending any attachment.

SECURITY PRACTICE

Keep Control Of Account Data

We keep this Privacy Policy practical: you should know what enters the account record, how security checks work and where a change request goes.

Account details

We use details such as your phone number and verification result to create, secure and maintain your account. Phone verification comes before account access, helping us connect requests to the correct profile.

Device signals

Browser type, device identifiers and sign-in events can help us detect unusual access. We use these signals for account protection and service diagnostics, not as a substitute for your account credentials.

Payment references

A transaction reference can show whether a DANA, QRIS, bank transfer or virtual account step reached the expected status. We use that reference for matching and support checks rather than storing a wallet PIN.

Cookies

Cookies and local storage may keep a session active, remember a selected setting or support security checks. You can manage browser storage through your device settings, though some account functions may then need another sign-in.

Retention periods

We retain records only for the operational, security or legal purpose connected to them. The period can differ for verification, payment status and support messages, and we remove or restrict records when that purpose ends.

Change requests

To request access, correction or deletion where available, use our account help contact and describe the record concerned. We may request verification through your registered phone before making a change.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the practical questions we expect before account creation, including wallet references, cookies, phone verification and requests to change stored details. If your situation is not covered, use the account help contact with only the details needed to identify your request.

It covers account details, phone verification, device and sign-in records, cookies, payment-status references, support messages, retention and requests to access or correct your information.

Our Privacy Policy does not ask you to send a DANA or QRIS PIN. We may handle a transaction reference or status needed to match an account action and answer a payment question.

Phone verification helps connect account access and privacy requests to the correct person. It also gives us a security check when you ask to change account details or recover access.

We may record browser type, device signals, session activity and sign-in events. These details help identify unusual access, maintain a session and diagnose account issues without replacing your login credentials.

Use the account help contact and ask for access to your stored account information. Include your registered phone number, but do not send a password, wallet PIN or unrelated identity documents.

Yes. Send a correction request through the account help path and identify the detail that is wrong. We may verify your registered phone before changing the account record.

Retention varies by record type and purpose. Verification, payment status, security events and support messages may follow different periods, after which we remove or restrict them where applicable.