Slots / Live
These terms set out the rules that govern your account on juan 635, covering your rights, what we collect, and how disputes are handled. Access to our platform depends on local law and is available only where permitted by your region.
Our platform operates under a policy framework designed for transparency and account accountability. When you open and use a juan 635 account, you agree to the terms stated on this page and any supplementary policy documents linked from your account dashboard. These terms apply regardless of the device you use — mobile or desktop — and regardless of which payment route you choose, whether that is Maya, InstaPay, or PESONet. We do not make legal certainty claims about jurisdictions we cannot verify. If you are accessing juan 635 from a location where online gaming is subject to local restrictions, it is your responsibility to confirm your eligibility before transacting. We will always state, at the point of account creation and within your account settings, whether your region is currently supported. Policy documents may be updated. When material changes occur, we notify you through the contact method on file in your account. Continued use of the platform after a notified update constitutes your acceptance of the revised terms. Archived versions of prior terms are available on request through our support channel.
Not every aspect of your experience falls under the same policy clause. Understanding the boundary between what we govern directly and what is handled by third-party systems helps you know where to direct any concern that arises.
Your login credentials, session activity, and account settings are fully within the scope of this policy. We hold records of all account-level actions, and you can request a review of your access history through your account dashboard at any time.
Deposits and withdrawals processed through Maya, InstaPay, or PESONet are recorded in your wallet history. Our policy governs how we store and use that data — but the payment provider's own terms also apply to any transfer made through their rail.
All page content, game lobby entries, and promotional communications published on juan 635 are produced under this policy. Claims we make in those materials are subject to the same accuracy and compliance standards described here.
Services provided by external processors, identity verification partners, or game content studios operate under their own terms. We do not extend our policy to cover those parties, though we require any partner we work with to meet baseline data-handling standards.
Your rights under this policy are practical, not theoretical. You can review the data we hold on your account at any time by navigating to the Records section inside your account settings. If any detail is incorrect — such as a contact email, linked payment method, or identity field — you can submit a correction request directly from that same section without contacting support first. For questions that go beyond self-service, our support team handles policy-related queries separately from technical issues, so your concern reaches the right team faster. If you believe we have not acted on a correction or access request within a reasonable period, you can escalate through the formal dispute route described in the support section below. We keep records of all requests submitted, so escalation has a traceable starting point.
Go to Account Settings, then Records. Your full transaction log, session history, and stored personal fields are shown there. You do not need to contact support to view this data — it is available to you after login.
If a stored field is wrong, select the relevant entry in Account Settings and submit the correction form shown there. Changes to payment-linked fields may require identity confirmation as displayed in the form.
Policy queries can be submitted via the support route marked Policy and Legal in our contact menu. This routes your message to the team that handles compliance, not the general queue — responses address your specific question, not a generic reply.
Prior versions of our terms, cookie policy, or data retention schedule are available on request. Submit the request through support and specify which document and version you need — we will provide it within the period shown in the support reply.
Policy questions move faster when they reach the correct team. Use the routes below based on the nature of your concern — account corrections, formal disputes, and general policy questions each have a dedicated path so your message is handled without delay.
Select Policy and Legal in the support contact menu on juan 635. This route connects you directly to the compliance team, not the general support queue. Include your account reference and a brief description of your question.
Corrections to stored personal details, linked payment methods such as Maya or InstaPay, or identity records should be submitted through Account Settings first. If self-service is not available for your specific field, use the Account Help route in support.
If a previous support request has not been resolved to your satisfaction, use the Escalation route in the support menu. Provide the original ticket reference so the compliance team can access the full history before responding.
Our data handling practices are built around what your account actually requires — nothing more is collected than what is needed to run your session, process your transactions through Maya, InstaPay, or PESONet, and respond to your support requests. Retention periods are stated in the data retention schedule available on request.
We use session cookies to keep you logged in and functional cookies to remember account preferences. You can review and adjust cookie settings through your browser. Disabling certain cookies may limit account functionality — the specific impact is shown in the cookie settings panel.
Your account credentials are stored using industry-standard hashing. We do not store plain-text passwords. If you suspect unauthorised access to your account, go to Security in Account Settings and follow the steps shown there to lock and recover access.
We retain transaction records and account activity logs for the period required by applicable law and our operational obligations. When the retention period ends, data is deleted or anonymised according to the schedule in our data policy, available on request through support.
To request deletion, portability, or restriction of your personal data, use the Policy and Legal route in the support contact menu. State clearly which data type and account you are referring to. We acknowledge all requests and respond within the period shown in the reply.
These are the questions we see most often from account holders after reading this policy. If yours is not listed here, the Policy and Legal contact route in our support menu is the right place to send it.
Access depends on local law and is available where local law permits. If you are in a region where online gaming is restricted, you are responsible for confirming your eligibility. Our terms apply to all active account holders regardless of how they access the platform.
Yes. Navigate to Account Settings, then Records after login. Your transaction history, session log, and stored personal fields are displayed there. For data not visible in self-service — such as archived records — submit a request through the Policy and Legal support route.
Go to Account Settings and select the field you want to change. Follow the correction form shown there. For fields linked to payment methods like Maya or InstaPay, the form may require identity confirmation as shown on screen. If self-service is unavailable for your field, use the Account Help support route.
Yes. When we make material changes to this policy, we send a notification to the contact method registered in your account. Continued use of your account after that notification constitutes acceptance. Prior versions are available on request through the Policy and Legal support route.
Our policy governs how we store and use transaction data from these payment rails. The payment providers' own terms also apply to each transfer. Both sets of terms are in effect simultaneously — contact us if you have a question about how our side of a specific transaction was handled.
If a previous support request has not been actioned within a reasonable period, use the Escalation route in the support menu. Include the original ticket reference so the compliance team can review the full history. All escalation requests are logged with a traceable reference.