Reference

insta555 Privacy Policy for Your Account

insta555 Privacy Policy shows what we collect when you create an account, verify your phone, sign in on mobile, or connect DANA and QRIS for account activity.

Clear collection detailsWallet data boundariesPhone verification explainedRequest paths included
insta555 insta555 Privacy Policy for Your Account
PRIVACY HELP

Check Support Paths for Privacy Questions

A privacy question should have a clear route, so we keep account help close to the sign-in and cashier paths. From your account area, use the displayed support contact to ask about a stored detail, a wallet reference or a device record. Include your account phone number only through that protected path; do not send a PIN, password or one-time code. We can then confirm ownership before discussing account data.

Team online

Account privacy request

Use the support contact shown after login when you want to ask what account details are held, why a phone verification record appears, or how to request a correction. We first confirm that the request comes from the account holder.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference through the account support path. We can check the matching record without asking for your wallet PIN, password or one-time code.

Access and deletion request

Ask support to review, amend or remove eligible personal data through the contact route displayed in your account. We may request phone verification before acting, so a private request is not changed by another person.

DATA PRACTICE

Explore How Account Data Is Handled

We handle privacy as an account operation rather than a short notice at the bottom of a page.

Account details

We use your phone number and account identifiers to create the profile, complete phone verification and connect requests to the correct account. Keep those details current through the available account path, and contact us if a record needs correction.

Device and login records

Your browser type, device signals and login times can help us spot an unusual sign-in or protect an active session. These records support account security; they are not used to request your device password or wallet credentials.

Cookies and session storage

Cookies or similar storage can keep your login session, language choice and page state working as you move from account access to the lobby. You can manage browser storage in device settings, although some account functions may then need another sign-in.

Wallet and receipt data

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain references needed to match a receipt or resolve a status question. We do not need your wallet PIN or one-time code to perform that check.

Retention and deletion

We keep personal data only for the period needed to provide account access, protect the service, resolve disputes or meet legal duties. When a valid deletion request is accepted, we remove or de-identify eligible records while required records may remain.

Policy changes

If our collection, cookie or retention practice changes, we update this Privacy Policy and show the current version through the privacy link. Check it before opening an account or returning after a material change to how your data is handled.

Browse Privacy Policy Questions Before Joining

These Privacy Policy answers cover the account moments you are most likely to ask about: phone verification, mobile access, local wallets, cookies, retention and requests for changes. We keep the answers tied to insta555 procedures so you know which path to use before opening an account or contacting support.

The insta555 Privacy Policy covers data collected during account creation, phone verification, login, wallet activity, device access and support contact. It also explains cookies, security use, retention and how you can ask us to correct, access or remove eligible personal data.

Phone verification links an account request to the person controlling the submitted number and helps us protect later account access. We may use that check before discussing personal data or acting on a change request, but we do not need your wallet PIN or one-time code.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use a receipt or transaction reference to match account activity and resolve a status question without accessing your wallet credentials.

When you sign in on a phone or tablet, we may record device and browser signals, session details and login times for account security and session operation. These details help identify unusual access; they do not give us your device password or private wallet code.

Use the support contact displayed in your account area and describe the detail you want checked, corrected or removed. We may ask you to complete phone verification before making a change, so another person cannot alter your account through an unverified message.

We retain account data for as long as it is needed for access, security, support, dispute handling or legal duties. When those purposes end, eligible records can be removed or de-identified; some records may remain where a legal duty requires continued storage.

Yes. Send your question through the privacy or account support path shown after login, and we will direct it to the applicable process. Account access and eligibility depends on local law, so the response may differ according to your location and the request.