Reference

testi138 Privacy Policy For Your Account

The testi138 Privacy Policy explains how we handle the details tied to your account, device and wallet activity before you enter titles such as Live Blackjack Table or…

Clear data purposesWallet record handlingCookie choicesAccount contact path
testi138 testi138 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Policy Help Near Login

A clear contact route helps when you want to ask about a record connected with your account.

Account request Use the support path beside your account controls to ask what contact, login or…
Wallet record For a DANA, OVO, GoPay or QRIS question, tell us the date, route and…
Cookie question If a device keeps a preference after you change it, contact us through the…
HANDLING PRACTICES

What We Do With Your Account Data

Privacy Policy choices should be practical, not hidden behind broad wording. We separate account access records from wallet references, use device signals to help spot unusual sign-ins, and…

Account records

When you open an account, we record the details needed for access and phone verification.

Device signals

Our mobile and desktop pages may receive device or browser signals linked to a login session.

Cookie choices

Cookies can retain sign-in preferences, session settings and page choices.

Payment references

A wallet record can show a rail such as QRIS, DANA, OVO or GoPay, plus a reference and status.

Security steps

Phone verification is part of the account access path, and we may compare sign-in context with earlier activity when a…

Retention requests

We retain records only for the period needed for account operation, security checks, dispute handling or legal duties that apply…

Privacy Policy Answers For testi138

These Privacy Policy questions cover the points most often raised before account access: what we collect, why wallet references appear, how cookies work and where to send a request. Each answer stays focused on your testi138 account and the records created when you sign in or use a supported payment route.

It covers details connected with your account, phone verification, login sessions, device signals, cookies, support messages and wallet references. It also explains why we use those records, how we protect account access and how you can ask for a copy, correction or deletion where local law permits.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer or virtual account routes. We use these fields to reconcile your account activity, while your wallet PIN, banking password and one-time approval code should remain private.

We use the phone detail supplied during account setup or verification to support sign-in, confirm account ownership and respond to account requests. If you believe it is wrong, send a correction request through the account support path and identify the contact detail currently attached to your account.

You can ask for a copy of eligible details linked to your account through the support route shown after login. Include your account contact and describe the records you need, such as login events, cookie choices or wallet references. We may verify ownership before responding.

Send the request through the account support path, state whether you want correction or deletion, and name the specific record. We assess the request under applicable rules because some security, dispute or legal records may need to remain for a stated period.

Cookies may keep a session preference or page setting on your browser. Clearing them through your mobile browser removes stored entries, but it can sign you out and require phone verification again. Contact support if a cookie choice does not appear to change.

Yes. Account access and eligibility depend on local law, and some data requests may have limits under the rules that apply to your location. We will explain the applicable response path when you contact us, without asking for your wallet password or one-time code.