Reference

Open artis77 With Privacy Clearly Explained

artis77 Privacy Policy explains how we handle your account details, wallet records and device access before you enter the lobby.

Clear data purposesWallet record detailPhone verification contextCookie choices
artis77 Open artis77 With Privacy Clearly Explained
PRIVACY CONTACT PATH

Contact Us About Your Stored Data

A direct support path helps when your Privacy Policy question concerns an account record, cookie setting or payment reference. Start from the account support route and include the email or phone detail connected to your profile, but do not send a wallet password or full security code. We can then identify the relevant request, explain the next account step and tell you what verification is needed.

Team online

Account data request

Use our account support channel to ask which profile details are connected to your artis77 access. Include your registered contact detail so we can locate the correct record, then complete any identity check before we disclose account-specific material.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the transaction date, amount and reference fragment through support. We use those details to trace the payment record while keeping your wallet PIN, password and one-time security code private.

Cookie access help

When a browser setting affects account access, contact support with your device type and browser path. We can explain which cookie controls matter, while you remain responsible for keeping your phone lock, browser session and account credentials protected.

HANDLING YOUR DETAILS

Browse How We Protect Policy Rights

Privacy is part of the account path rather than a separate promise. We explain why a detail is needed, limit access to operational purposes and keep requests tied to the profile that…

Account records

We may hold your name or contact detail, phone verification result, login events and account preferences so we can maintain access and respond to account questions. We do not ask you to place a password, PIN or full one-time code inside a support message.

Payment matching

A payment record can include the selected route, transaction reference, status and timing. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, these fields let us compare the cashier record with the account without requesting unnecessary wallet credentials.

Cookies and devices

Cookies and device signals can help keep a signed-in session consistent, detect unusual access and remember a setting. You can manage browser cookies through your device path, although refusing some cookies may affect login continuity or require another account check.

Security checks

Phone verification and sign-in checks help us distinguish the account holder from an unfamiliar session. If you change phones, clear browser storage or sign in from a new device, we may ask for an additional check before discussing private account details.

Retention timing

We keep records for as long as needed for account operation, payment reconciliation, security investigation and legal duties. When a record is no longer required for those purposes, our handling process considers deletion, restriction or aggregation where the applicable rules allow it.

Changes and objections

You can contact us to correct an inaccurate profile detail, ask about stored information or raise an objection tied to your Privacy Policy rights. We may verify ownership first, then explain the result, any restriction and the reason a record must remain.

Ask About artis77 Privacy Policy

These Privacy Policy answers address the account questions you may have before using the Indonesia-facing access path. We focus on the records we actually need for login, payment matching, device security and support. If your situation is not listed, contact us through the account support route with enough detail to locate your profile.

It covers account details, phone verification, login and device events, cookies, support messages, payment references and retention. It also explains how we use those records for account access, security, payment reconciliation and legal duties, plus how you can request access or correction.

DANA and QRIS references help us match a transaction question with the correct account record. The same approach applies to OVO, GoPay, bank transfer and virtual account routes. We use payment references and status details, not your wallet password or full security code.

Contact account support using the contact detail registered on your profile and state that your request concerns the Privacy Policy. Tell us whether you want access, correction or deletion information. We may verify account ownership before sharing private records or processing the request.

Yes. It applies when you sign in through a supported mobile browser, complete phone verification or move from login to the lobby. Device and session signals may be used for security. Clearing browser storage can remove a session and trigger another account check.

We use cookies and similar browser signals to maintain sessions, remember relevant settings and identify unusual access. You can manage them through your browser controls. If you refuse required cookies, login continuity or some account functions may require another verification step.

You can ask us to correct an inaccurate account detail through support. Include the registered phone or email and describe the field that needs attention. We verify ownership before changing it, and payment or security records may need to remain for operational or legal reasons.

Use the account support route for questions about your profile, cookies, device access or transaction records. Include a payment reference only when it is relevant, and never include a password, wallet PIN or full one-time code. Access or eligibility depends on local law.