Reference

Open periktoto Legal details before joining

periktoto Legal explains how your account, wallet records, data choices and site access are handled before you open an account.

Account rulesData choicesLocal access
periktoto Open periktoto Legal details before joining
HELP PATHS

Choose a Legal support route

A clear contact route helps when you need a policy answer rather than a game or wallet explanation. We sort requests by account access, payment records and data changes, so your message reaches the relevant path. If you are in Medan or elsewhere in Indonesia, include your account identifier and the exact policy point you want clarified.

Team online

Account access

Ask about phone verification, login ownership or an access pause through the account help path. Include the mobile number linked to your account, but never send your password or a private security code.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, use the cashier-status path and attach the receipt reference. We can then compare the payment record with your account details.

Policy changes

Request a correction, deletion assessment or clarification through the policy contact path. Tell us which Legal clause concerns you and what change you seek, so we can respond without guessing.

ACCOUNT SAFEGUARDS

Explore how our Legal process works

We keep this policy area practical: you can see why an account step is needed, which records relate to a wallet action, and where to ask for a correction.

Data handling

We use account details to identify the account holder, process access checks and connect payment references with the correct record. Legal requests should identify the relevant account without exposing passwords or private codes.

Cookie choices

Cookies can support browser sessions and remember necessary access settings. Your policy request may ask which device or browser showed the issue, helping us separate a cookie problem from an account problem.

Account security

Phone verification is part of the account access path. Keep your login details private, sign out on shared devices, and contact us if a mobile-browser session or desktop session looks unfamiliar.

Record retention

We retain account and payment records for the periods required by the applicable policy and local rules. A retention question should name the record type, such as a QRIS receipt or login event.

Correction requests

If your account name, phone detail or wallet reference is wrong, ask for a correction through the policy route. We may need account verification before changing a record tied to DANA or bank transfer.

Access wording

Our Legal position does not replace local requirements: access depends on local law. Where local law permits, we present the account path; otherwise, do not attempt to bypass a regional restriction.

Browse common periktoto Legal questions

These answers address the Legal searches we hear most often before account creation. They cover access, personal data, payment records, cookies and account changes, with practical steps for contacting us when a policy point needs attention.

periktoto Legal covers account access, phone verification, data handling, cookies, payment records, security duties, retention and policy requests. It also explains that eligibility depends on local law.

Access is presented where local law permits and depends on local law. Use the normal mobile-browser or desktop-browser path, complete phone verification, and do not bypass a regional restriction.

Phone verification helps connect account access with the correct account holder. If your number has changed or verification stalls, use the account access path and describe the step that stopped.

Legal covers records linked to DANA, QRIS and other listed payment rails. Keep your receipt reference, because we may compare it with the account identifier before correcting or explaining a status.

Yes, you can request a correction or ask how a data change is assessed through the policy contact path. Identify the affected field, such as a phone detail, without sending your password.

Cookies may support a browser session and necessary access settings. If a session behaves unexpectedly, tell us the device and browser used so we can distinguish cookie behaviour from account security.

Use the policy contact path and quote the clause or subject that concerns you. Include your account identifier and requested outcome; never include a password, private security code or unnecessary wallet credentials.