Reference

Privacy Policy For Your api36 Account

api36 Privacy Policy explains how we handle the account, device and wallet details connected with your access to live tables, slots and sports markets.

Account dataWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
api36 Privacy Policy For Your api36 Account
CONTACT OUR TEAM

Privacy Questions Reach The Right Path

A clear contact route helps when your account record or wallet reference needs attention. We ask you to include the account identifier you can safely share and a short description of the request, rather than sending passwords or full payment credentials. Our support team can direct privacy questions to the right handling path, explain the next account step and help distinguish a data request from a cashier-status question. Access and assistance remain subject to local law.

Team online

Account privacy request

Use the support route connected to your api36 account when you want to ask what personal details we hold, why a phone verification record appears, or how to request a correction. Include your account identifier, but never send your password, one-time code or complete wallet credentials.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference that looks unfamiliar, tell us the date, payment rail and visible reference fragment. We use those details to locate the relevant record while limiting the personal data included in your message.

Access and deletion route

If you want access, restriction or removal of eligible account data, contact us through the account support path and state the request clearly. We may need to confirm account ownership before acting, and some records may remain where legal or transaction duties require retention.

DATA HANDLING DETAILS

Six Practical Privacy Safeguards

We treat the Privacy Policy as an operating process, not a page kept apart from the account flow.

Account creation

When you open an account, we use the details you submit to create the account record and provide the requested access. Clear phone verification can be part of that process. We do not need your payment password to connect a wallet reference with your account.

Device and session data

A mobile browser may provide device type, session markers and basic access signals so we can keep your login path working and identify unusual sign-in activity. These signals help protect the account; they are not a substitute for the personal details you choose to submit.

Cookies and preferences

Cookies can remember a session, language choice or page preference so you do not repeat the same account step on every visit. You can manage browser cookie controls, although changing them may affect sign-in continuity and the way policy choices are remembered.

Payment references

Cashier records may contain a rail name such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, together with a reference and status. We use this information to reconcile activity and investigate a mismatch without requesting your wallet password.

Retention and deletion

We keep account, security and transaction records for the period needed for the stated purpose, account protection and applicable legal duties. A deletion request does not automatically erase records that must remain for reconciliation, dispute handling or other required obligations.

Policy changes

When our handling practices change, we update this Privacy Policy and show the revised wording on the policy page. Please check the page before opening an account or sending a request. If a change affects your choices, contact support for clarification before continuing.

Privacy Policy Questions About api36

These Privacy Policy answers focus on the account actions Indonesian customers ask about most often. They cover access, wallet references, cookies, corrections and deletion requests without replacing the full policy wording. If your situation involves a specific record, contact support with only the details needed to locate it. Eligibility depends on local law.

The api36 Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet references and support requests. It also explains retention, security handling, policy changes and the choices available when you ask to access, correct or remove eligible personal data.

Phone verification helps us connect the account to the contact detail you provide and helps protect access when a sign-in or account step looks unusual. We record the verification result for account security and handle it under the Privacy Policy, subject to local law.

Yes. The Privacy Policy covers payment references linked to your account, including DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These references help us reconcile status and investigate a mismatch without requesting your wallet password.

Contact support through the account path and ask for access to your api36 data. State the account identifier you can safely share and describe the records you want located. We may confirm account ownership before responding, and the request remains subject to local law.

Yes, you can ask us to correct inaccurate or incomplete personal data covered by the Privacy Policy. Tell support which account detail is wrong and provide the corrected value through the requested verification path. Do not include your password, one-time code or full wallet credentials.

Cookies can keep your session active and remember a preference on the device you use to access the account. Browser controls let you manage them, but disabling cookies may interrupt sign-in or prevent a policy choice from being retained for your next visit.

We can assess a deletion request for eligible data after confirming account ownership and identifying the records involved. Some account, security or transaction records may need to remain for reconciliation, dispute handling or legal duties, so removal is not automatic in every case.

Related Pages

api36 Indonesia Bundesliga Mix Parlay Account information About Us FAQ