Reference

ulti 700 Privacy Policy, Made Clear

Our Privacy Policy shows how we collect, use, store, and protect details linked to your ulti 700 account.

Account dataWallet referencesDevice controlsPolicy requests
ulti 700 ulti 700 Privacy Policy, Made Clear
CONTACT ROUTE

Privacy Questions Need A Clear Route

A direct contact path helps you resolve a Privacy Policy question without sending the same request several times.

Account data request Ask us to identify the account details connected with your login. Include your registered contact detail and the account step concerned, but do not send a password or full wallet credentials through a support message.
Wallet reference check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, share the transaction reference rather than private wallet access data. We can use that reference to locate the relevant policy record.
Correction request For an incorrect name, phone detail, or account record, contact our privacy route with the change requested. We may ask for account verification before making an amendment, so another person cannot alter your data.
SECURITY PRACTICE

How We Handle Account Data

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account security

Phone verification helps us connect an access request with the correct account. We use sign-in and security signals to detect unusual activity, and we will not ask you to reveal your password when handling a privacy request.

Device signals

A mobile browser may provide device, browser, language, and session details when you sign in. We use these signals to keep the account route working and to investigate access problems, not to replace the account details you submit.

Cookies

Cookies can keep a session active, remember selected settings, and help us understand whether a page loads correctly. Your browser controls can remove or restrict them, although some account steps may then need to be repeated.

Payment records

We handle payment references rather than asking for your wallet password. A DANA, OVO, GoPay, or QRIS reference can help match a cashier event to your account while keeping the wallet login outside our records.

Retention period

We retain account, security, support, and transaction records only for the period connected with their purpose or a legal duty. Ask us about a specific record, and we will explain the reason it remains available.

Policy changes

When our handling of personal data changes, we update this Privacy Policy and show the revised date or wording on the policy page. Check this page before an account step if you need the current policy terms.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and payment questions we hear most often from people accessing ulti 700 in Indonesia. They cover the data collected during phone verification, mobile browsing, wallet references, cookies, retention, and correction requests. If your case involves a specific account record, contact us with the relevant reference and we can assess the request under applicable law.

It covers data created when you open an account, complete phone verification, sign in, use a mobile browser, contact support, or connect DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains cookies, security use, retention, corrections, and access requests.

We may collect the details you submit for an account, verification records, login events, device and browser signals, support messages, and transaction references. We use these details for account access, security, support replies, and legal duties rather than unrelated purposes.

No wallet password should be sent to us through an account or support request. Our policy concerns transaction references and status details connected with DANA, OVO, GoPay, or QRIS, so we can match an event without receiving your private wallet login.

You can contact us to ask what account, device, support, or transaction data is linked to your record. Include your registered contact detail and the scope of the request. We may verify account ownership before responding, and access depends on local law.

Send a correction request through our privacy contact route and name the field that needs changing, such as a phone detail or account name. We may ask for a verification step before editing the record, which helps prevent an unauthorised change.

Retention depends on why the record was created. Account, security, support, and transaction details may remain while needed for that purpose or a legal duty. Ask about a particular record and we will explain the applicable retention reason under this Privacy Policy.

Cookies can support a mobile session, remember settings, and show whether an account page loads properly. You can restrict or remove them through your browser. If you do, phone verification or another account step may need to be repeated.