Reference

zk998 Legal Rules For Your Account

zk998 Legal sets out how account access, wallet checks and personal data are handled before you enter the lobby.

Account termsData handlingLocal-law accessWallet records
zk998 zk998 Legal Rules For Your Account
CONTACT ROUTES

Legal Help For Login And Wallet Questions

A clear support route matters when a Legal question affects your account or payment status.

Account access If phone verification or login stops your account path, send the registered phone detail…
Payment records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment…
Policy requests You can ask us to clarify a Legal clause, correct an account detail or…
DATA PRACTICES

How We Apply zk998 Legal Controls

Our Legal process is designed around practical account events rather than broad promises.

Account data

We use your account details to identify the profile, complete phone verification and protect access.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be retained with the related account event so we can check receipt…

Cookies

Cookies and similar browser records may keep your session usable, remember selected account settings and help us identify repeated access…

Security steps

Do not share your password, phone verification code or payment confirmation with another person.

Retention

We retain account, payment and support records only for the operational, security or legal reasons that apply to that record.

Change requests

To request a correction, access copy or deletion review where local law permits, contact us using the details attached to…

Answers About zk998 Legal Access

These Legal answers address the account questions we expect you to ask before opening or continuing a profile. They cover local access, identity checks, payment records, cookies and requests about your data. If your case depends on a receipt, phone number or account event, use the support path above and provide that specific reference.

zk998 Legal covers account creation, phone verification, access conditions, payment records, cookies, security steps, retention and requests about your personal data. Access depends on local law, so you should confirm that using the service is permitted for your location before submitting account details.

Yes, we may require phone verification before account access continues or before we discuss sensitive account details. Use a phone number you control and keep the code private. If the number is wrong, contact us through the account route rather than creating a duplicate profile.

We may retain DANA and QRIS references with the related account event so we can check receipt status, identify a mismatch or answer a payment query. A receipt does not replace account verification, and you should remove private wallet credentials before sending any supporting image.

You can request a correction through the contact details attached to your account. Name the field that needs changing, such as a phone number, and provide enough context for us to identify the profile. Where local law permits, we will explain the applicable next step.

We first confirm that the request comes from the account holder, then identify the data category and account record involved. This may include profile details, payment references or support history. We will explain any Legal condition that affects the request before processing it.

Yes. Browser cookies can maintain a session and preserve selected account settings, while blocking them may interrupt parts of the login or verification path. You can change cookie controls on your phone or desktop, then contact us if the account path no longer works.

Use the support route linked to your registered account and state whether the issue concerns access, data, cookies or a payment reference. Include a receipt or reference when relevant, but never send your password, phone code or wallet PIN. We will direct the request to the proper account check.