General terms
These Terms of Service set out the relationship between you and JurisYFlow for access to and use of our services. They describe account obligations, permitted use, intellectual property, payment terms for paid services, limitation of liability, and dispute resolution procedures. Where helpful, sections include practical case examples illustrating how the terms apply in typical legal operations scenarios.
1Eligibility and lawful use
Access to JurisYFlow services is available to legally capable individuals and organizations able to enter binding agreements. Use must be lawful and in line with intended business or research purposes. For example, an in-house counsel team may register to manage contract workflows and compliance tasks; a user registering as a government contractor must ensure any special procurement rules are followed.
Users must be at least 16 years old or have legal authorization to enter into these terms on behalf of an organization. For organizations enrolling trainees under 18, the registering legal representative must confirm lawful consent and supervision.
Services must not be used for unlawful activities, to infringe third-party rights, or to transmit harmful code. Typical permitted uses include contract lifecycle management, compliance tracking, policy drafting and automated document review within the bounds of applicable laws and internal security policies.
Certain features or integrations may be restricted in specific jurisdictions due to local legislation. JurisYFlow documents such restrictions and provides scenario-based guidance for cross-border data transfers and compliance considerations for Swiss entities and multinational corporations.
2Account registration and management
Account registration requires accurate organization and contact information. Accounts may be created for individual practitioners or corporate teams. In case-based onboarding scenarios, JurisYFlow documents user roles and permissions to facilitate workflow delegation and auditability.
You are responsible for keeping account information up-to-date. In practical terms, when a key contact changes role, the account administrator should update permissions and contact details to maintain continuity of compliance operations.
Account holders must use strong authentication methods and follow JurisYFlow's recommended security practices. Example scenarios include enabling multi-factor authentication for administrators and rotating API keys after personnel changes.
Accounts and access rights are personal to the registering organization and may not be transferred without JurisYFlow's written consent. For mergers or acquisitions, parties should notify JurisYFlow to align accounts with the new organizational structure.
If you suspect unauthorized access, notify JurisYFlow immediately at [email protected] and follow containment steps outlined in our incident response playbook. Provide case details, affected assets, and examples of suspicious activity to accelerate remediation.
JurisYFlow may suspend access for breach of terms or security concerns. Suspension in a compliance-critical scenario will be communicated with mitigation instructions and a path to restore access where feasible.
3Service scope and availability
JurisYFlow delivers a suite of legal operations and compliance tools, including policy management, contract lifecycle workflows, custom templates, analytics and integrations. Service descriptions include practical case studies showing how features are applied in enterprise environments to streamline reviews, centralize approvals and track regulatory obligations.
We may update service features or integrations. Changes are rolled out with notice and documentation, and where changes materially affect enterprise workflows we provide migration guidelines and scenario-based examples to help teams adapt without disrupting compliance timelines.
JurisYFlow aims for high availability and provides service level guidance in contractual agreements. Planned maintenance windows are scheduled with advance notice; emergency maintenance may occur to address security incidents, and relevant stakeholders will receive timely case-specific communications.
4Acceptable use rules
To protect users and ensure reliable operations, the following rules apply to the use of JurisYFlow in real-world scenarios involving sensitive legal data and workflow automation.
- Do not upload data obtained unlawfully or containing material you are not authorized to process; include scenario guidance for third-party subpoenas and chain-of-custody considerations.
- Respect intellectual property and confidentiality obligations when sharing templates, precedents, or annotated documents within JurisYFlow workspaces.
- Do not attempt to bypass security controls, exploit system vulnerabilities, or reverse-engineer platform components; follow incident reporting procedures in case of suspected vulnerabilities.
- Use platform automation features responsibly; implement review gates and human-in-the-loop checks for high-risk actions such as contract approvals or rights-granting clauses.
- Comply with export control, sanctions and local regulatory restrictions when using integrations that trigger cross-border data flows. Practical cases include restricted sharing of personal data across non-approved jurisdictions.
- Maintain accurate records of approvals, edits and task assignments to support audits and regulatory inquiries; JurisYFlow logs can be used in case scenarios to reconstruct workflows.
- Cooperate with JurisYFlow in contribute of misuse or security incidents, providing requested case information and access to relevant logs as required by law.
5User content and submissions
Users may submit documents, templates, annotations and other content to JurisYFlow as part of providing or using services. The following rules govern ownership, licensing and responsibilities for such content, with practical examples illustrating common enterprise workflows.
You retain ownership of content you upload, subject to any rights you grant JurisYFlow to provide the service. For instance, organizations maintain ownership of legal templates and precedents uploaded for shared use within their teams.
By uploading content, you grant JurisYFlow a non-exclusive, worldwide license to store, process, and display the content as necessary to deliver services, facilitate integrations, and provide support. Licensing examples are provided for document automation, analytics and training dataset uses with anonymization steps where applicable.
You are responsible for the accuracy and lawfulness of uploaded content. In scenario-based audits, JurisYFlow assists by exporting activity logs but does not accept liability for client-supplied content accuracy or regulatory compliance of that content.
Content may be removed by users or by JurisYFlow when required by law or breach of terms. Removal procedures and retention considerations are explained through workflow examples, such as how to archive contract records during a litigation hold.
6Intellectual property rights
All intellectual property rights in the JurisYFlow platform, software, documentation and brand assets are owned by JurisYFlow or its licensors. Users are granted only the rights expressly set out in these terms. Practical cases explain permitted use of exported reports and derivative works for internal compliance purposes.
- Do not reproduce, distribute, modify or create derivative works of JurisYFlow software beyond permitted use in your organization. Example: copying platform code into an internal tool is prohibited.
- Do not remove or alter proprietary notices or activity embedded in platform outputs or documentation.
- Reverse-engineering, decompilation or extraction of underlying algorithms is prohibited; for collaboration scenarios requiring interoperability, contact JurisYFlow for supported APIs and integration options.
7Paid services and billing
Paid services include subscription tiers, consultancy packages and premium integrations. Each paid service is described in an order form or subscription agreement that references these terms and includes pricing, scope and service-level provisions framed around practical enterprise use cases.
Pricing is set out in the applicable order form or subscription page on JurisYFlow.click. Quotes provided during procurement scenarios are valid for the period specified and are based on the scope and number of seats required for the described workflows.
Invoices are issued according to the billing cycle in your agreement. Payment methods and invoicing details are handled through secure channels. In scenario-based implementations, payment milestones align with deployment phases and acceptance testing.
Subscription services renew automatically unless cancelled in accordance with the applicable agreement. Enterprise subscriptions may include onboarding support and training sessions, scheduled per mutually agreed deployment plans.
Refunds are considered in limited circumstances described in the applicable agreement and based on documented case scenarios such as failure to meet specified onboarding milestones. Routine dissatisfaction without a contractual basis does not automatically entitle a refund.
Cancellation procedures are set out in the subscription agreement. For planned contract termination, we provide data export and transition assistance to help preserve records and minimize disruption to ongoing compliance activities.
Prices exclude applicable taxes, duties or levies. In enterprise procurement scenarios, JurisYFlow will indicate taxes on invoices where required and cooperate to support tax reporting obligations.
Price adjustments are communicated with advance notice. For existing contracts, changes follow the terms of the agreement; for renewals, JurisYFlow provides scenario-based impact assessments to help budget planning.
Non-payment may result in suspension of services after notice and an opportunity to cure. In critical compliance contexts, JurisYFlow will work with clients to identify interim measures to preserve audit trails and minimize regulatory exposure.
8Disclaimer
JurisYFlow provides tools and guidance to support legal operations and compliance processes. The platform does not provide legal advice tailored to a specific client's facts unless provided under a separate consultancy agreement. Case studies illustrate typical outcomes but are not assurances of results in other settings.
9Limitation of liability
Except where prohibited by applicable law, JurisYFlow's liability is limited to direct damages arising from proven breach of contractual obligations, up to the amounts paid for the relevant services in the preceding 12 months. Liability for indirect, consequential or predictive losses is excluded. Practical risk scenarios and recommended mitigation steps are set out in our enterprise onboarding materials.
10Third-party products and links
Third-party integrations and linked services are provided by independent vendors. JurisYFlow documents known data flows and control mappings for common integrations and assists clients in reviewing third-party terms during implementation scenarios, but JurisYFlow is not responsible for third-party failures.
11Termination and suspension
Either party may terminate for material breach if the breach is not remedied within the specified cure period. JurisYFlow may suspend or terminate access for security or legal reasons, with case-specific notices and data retention or export options provided to affected customers.
On termination, user access will cease. JurisYFlow will provide the terminating party with a copy of their data in a standard export format where applicable and a specified retention period to retrieve records. Transition examples illustrate how to migrate workflows and preserve audit logs.
12Privacy and data processing
JurisYFlow's handling of personal data is described in the privacy policy and relevant agreements. Processing required to deliver services is governed by data processing terms and documented in implementation playbooks that include examples of lawful bases, retention schedules and subprocessors.
13Communications and notices
Notices under these terms should be sent to the addresses in the contact section. For operational matters such as security incidents or support, use the designated operational contact channels. Example notice templates for breach reporting and service escalations are available to enterprise customers.
14Changes to terms
We may update these terms; material changes affecting enterprise obligations will be highlighted and communicated with guidance for migration where needed. Case notes accompany major updates to explain practical effects on workflows and integrations.
15Governing law
These terms are governed by the laws of Switzerland. For customers operating cross-border, JurisYFlow provides scenario-based guidance on applicable local laws and regulatory considerations.
16Dispute resolution
Parties shall first seek to resolve disputes through good-faith negotiations. If unresolved, disputes may be submitted to the competent Swiss courts or to agreed alternative dispute resolution mechanisms set out in the applicable agreement. Practical dispute resolution scenarios and escalation paths are provided in enterprise contracts.