Reference

Open kaya33 Legal details before joining

kaya33 Legal sets out how account access, wallet records and personal data are handled before you open an account.

Account termsData requestsLocal-law accessWallet records
kaya33 Open kaya33 Legal details before joining
CONTACT THE POLICY TEAM

Use a clear route for Legal questions

A direct policy route helps when you need to understand account access, request a correction or ask why a wallet record is attached to your profile. Start from the signed-in account area and include the email or phone detail connected to your account. We use that step to locate the right record without asking you to post private details in a public message.

Team online

Account access

If your Legal question concerns login or phone verification, open the account support route and describe the exact step that stopped you. Include your registered contact detail, but never send a password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, attach the payment reference shown in your account. We can then match the record without treating a receipt image as proof of identity by itself.

Policy changes

When you want a data correction, access question or policy clarification, use the same signed-in contact path. Tell us what should change and why; we may request phone verification before confirming the request.

DATA HANDLING

Protect your account and policy record

Legal practice is easier to understand when each data step has a clear purpose. We use account details to maintain access, connect wallet references and answer requests, while security checks help prevent…

Account data

We use the contact details you provide to identify your account, complete phone verification and respond to a Legal request. Keep those details current so a correction or access question can be matched to the right profile.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us locate wallet activity connected with your account. Bank transfer and virtual account records are handled in the same request path when a policy question concerns a transaction.

Cookies

Cookies can support sign-in continuity, language settings and the return from a policy page to your account area. You can review cookie controls in your browser, though changing them may affect account access on that device.

Security checks

Phone verification helps us distinguish an account owner from an unauthorised contact. Do not share your password, one-time code or wallet PIN; our policy route may ask for account details, never secret credentials.

Record retention

We retain account and wallet records for the period needed to operate the account, address disputes and meet applicable policy duties. A retention question should include your account contact so we can explain the relevant record category.

Change requests

To request access, correction or removal of eligible data, contact us through the signed-in account path and state the specific request. We may verify your phone before making a change or confirming what can be provided.

Find answers about kaya33 Legal

These Legal answers cover the questions you may have before opening an account or asking us to change a record. We keep the route practical: check your local position, use the signed-in contact path and provide the account detail needed to identify your request. Where access is discussed, it depends on local law.

kaya33 Legal covers account creation, phone verification, data handling, cookies, wallet references, record retention and requests for access or correction. It also explains that service access or eligibility depends on local law, so you should check the rules that apply where you are located.

You can ask for access to eligible account data through the signed-in support route. State the contact detail linked to your profile and the records you want to understand. We may complete a phone verification step before discussing private account information.

Send a correction request through your account contact path and identify the field or wallet reference that appears wrong. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the visible reference so we can locate the relevant entry.

Yes. The Legal notice states that access or eligibility depends on local law. We do not replace local requirements with a general statement, so you should confirm that use is permitted in your location before completing phone verification or entering the lobby.

Phone verification helps us confirm that a policy request comes from the account holder. We may use it before changing personal details, discussing wallet records or providing account data. Never send your password, one-time code or wallet PIN as part of that request.

Cookies may help maintain sign-in continuity, remember page settings and connect your phone or desktop session with the policy area. Your browser controls them, but restricting cookies can affect account access or require you to repeat a sign-in step.

Use the signed-in policy contact route and ask about the category of record you want clarified. Include your account contact and, where relevant, a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so we can identify the retention question.