{"id":2741,"date":"2026-06-19T18:32:42","date_gmt":"2026-06-19T16:32:42","guid":{"rendered":"https:\/\/www.canyonclan.com\/?page_id=2741"},"modified":"2026-08-03T19:30:37","modified_gmt":"2026-08-03T17:30:37","slug":"algemene-voorwaarden-workhub","status":"publish","type":"page","link":"https:\/\/www.canyonclan.com\/en\/algemene-voorwaarden-workhub\/","title":{"rendered":"Workhub General Terms and Conditions"},"content":{"rendered":"

Deze algemene voorwaarden zijn een uitbreiding op onze standaard General Terms and Conditions<\/a> met betrekking tot onze Workhub tool. Dit betreft de Engelstalige versie. Op verzoek kan een Nederlandstalige versie bezorgd worden.<\/p>\n\n\n\n

<\/p>\n\n\n\n

GENERAL TERMS AND CONDITIONS FOR WORKHUB<\/strong><\/h2>\n\n\n\n

Canyon Clan VOF<\/strong><\/p>\n\n\n\n

Version: 26 July 2026<\/strong><\/p>\n\n\n\n

Table of Contents<\/strong><\/h2>\n\n\n\n
    \n
  1. Scope<\/li>\n\n\n\n
  2. Subject Matter of the Agreement<\/li>\n\n\n\n
  3. Licence and Right of Use<\/li>\n\n\n\n
  4. Requests and Tickets<\/li>\n\n\n\n
  5. Pricing<\/li>\n\n\n\n
  6. Approval of Tickets, Quotations and Changes<\/li>\n\n\n\n
  7. Performance, DelivDefinitions<\/li>\n\n\n\n
  8. ery and Acceptance<\/li>\n\n\n\n
  9. Subscription, Module Fees and Maintenance<\/li>\n\n\n\n
  10. Payment Mandate, Automatic Collection and Invoicing<\/li>\n\n\n\n
  11. Hosting, Availability and Platform Maintenance<\/li>\n\n\n\n
  12. Support and Incidents<\/li>\n\n\n\n
  13. Third-Party Integrations<\/li>\n\n\n\n
  14. Customer Data and Customer Responsibilities<\/li>\n\n\n\n
  15. Intellectual Property<\/li>\n\n\n\n
  16. Confidentiality<\/li>\n\n\n\n
  17. References, Use Cases and Marketing<\/li>\n\n\n\n
  18. Privacy and Processing of Personal Data<\/li>\n\n\n\n
  19. Security<\/li>\n\n\n\n
  20. Back-ups, Export and End of Access<\/li>\n\n\n\n
  21. Acceptable Use<\/li>\n\n\n\n
  22. Platform Changes and Roadmap<\/li>\n\n\n\n
  23. Liability<\/li>\n\n\n\n
  24. Force Majeure<\/li>\n\n\n\n
  25. Duration, Termination and Ending of the Agreement<\/li>\n\n\n\n
  26. Suspension<\/li>\n\n\n\n
  27. Amendments to these Terms and Conditions<\/li>\n\n\n\n
  28. Assignment<\/li>\n\n\n\n
  29. Severability<\/li>\n\n\n\n
  30. Governing Law and Competent Courts
    Appendix 1. Data Processing Clause<\/li>\n<\/ol>\n\n\n\n

    Article 1. Definitions<\/strong><\/h2>\n\n\n\n

    1.1. \u201cCanyon Clan\u201d or \u201cSupplier\u201d<\/strong>: Canyon Clan VOF, the supplier of the Platform and the related services.<\/p>\n\n\n\n

    1.2. \u201cCustomer\u201d<\/strong>: any company, organisation or professional user that uses the Platform or enters into an agreement with Canyon Clan.<\/p>\n\n\n\n

    1.3. \u201cPlatform\u201d<\/strong>: the Workhub software platform offered by Canyon Clan, which can grow according to the needs of its users through Modules, integrations, dashboards, workflows, reporting and other functionalities within a user-friendly framework.<\/p>\n\n\n\n

    1.4. \u201cUser\u201d<\/strong>: any natural person who is granted access to the Platform by or on behalf of the Customer.<\/p>\n\n\n\n

    1.5. \u201cRequest\u201d<\/strong>: a request submitted by the Customer or a User, including a bug report, feature request, change request, integration request, dashboard request, optimisation request or any other request to extend or modify the Platform.<\/p>\n\n\n\n

    1.6. \u201cTicket\u201d<\/strong>: the registration of a Request in the Platform or in a ticketing system used by Canyon Clan, including its description, scope, price, price indication, timing, status, comments and any approvals.<\/p>\n\n\n\n

    1.7. \u201cModule\u201d<\/strong>: a functional component, feature, integration, dashboard, report, workflow, automation or other extension within or connected to the Platform.<\/p>\n\n\n\n

    1.8. \u201cBase Licence Fee\u201d<\/strong>: the monthly fee for the use of the Platform, excluding any one-off or recurring fees for additional Modules, Requests, capacity or usage.<\/p>\n\n\n\n

    1.9. \u201cOne-off Fee\u201d<\/strong>: a one-off charge for the analysis, development, configuration, implementation, migration or activation of a Request, Module, integration or other service.<\/p>\n\n\n\n

    1.10. \u201cRecurring Fee\u201d<\/strong>: a periodic fee for a Module, integration, capacity, service, subscription, maintenance, usage or other extension.<\/p>\n\n\n\n

    1.11. \u201cInitial Module Period\u201d<\/strong>: the first period of twenty-four months during which a Module is active or made available and during which the agreed Initial Module Fee is payable, unless another period is agreed in writing.<\/p>\n\n\n\n

    1.12. \u201cInitial Module Fee\u201d<\/strong>: the agreed price for, among other things, the analysis, development, configuration, implementation, activation and initial provision of a Module. This fee may be paid in full in advance, in installments or through monthly payments during the Initial Module Period.<\/p>\n\n\n\n

    1.13. \u201cMaintenance Phase\u201d<\/strong>: the period that automatically starts after the Initial Module Period, provided that the relevant Module remains active.<\/p>\n\n\n\n

    1.14. \u201cMaintenance Fee\u201d<\/strong>: the recurring fee payable during the Maintenance Phase for keeping the relevant Module technically available, secure, compatible and maintainable.<\/p>\n\n\n\n

    1.15. \u201cCustomer Data\u201d<\/strong>: all data, files, content, input, configurations and information entered, uploaded, configured or supplied in the Platform by or on behalf of the Customer.<\/p>\n\n\n\n

    1.16. \u201cEffective End Date\u201d<\/strong>: the date on which the agreement or a separate Module effectively ends after application of the agreed notice period.<\/p>\n\n\n\n

    1.17. \u201cTransition Period\u201d<\/strong>: the limited period of one month following the Effective End Date during which Canyon Clan, where technically and reasonably possible, keeps the Customer\u2019s account accessible on a limited basis for the consultation and export of Customer Data.<\/p>\n\n\n\n

    1.18. \u201cFinal Settlement\u201d<\/strong>: the settlement of all amounts that remain payable on or as a result of the ending of the agreement or a Module.<\/p>\n\n\n\n

    Article 2. Scope<\/strong><\/h2>\n\n\n\n

    2.1.<\/strong> These general terms and conditions apply to every offer, quotation, order, payment, use of the Platform, licence, request, module and service provided by Canyon Clan, unless expressly agreed otherwise in writing.<\/p>\n\n\n\n

    2.2.<\/strong> Any deviating terms and conditions of the Customer shall not apply unless Canyon Clan has expressly accepted them in writing in advance.<\/p>\n\n\n\n

    2.3.<\/strong> These terms and conditions are intended for agreements between businesses and professional users.<\/p>\n\n\n\n

    2.4.<\/strong> If the Platform is exceptionally offered to a consumer, the applicable mandatory consumer protection rules shall apply and shall prevail over any conflicting provisions of these terms and conditions.<\/p>\n\n\n\n

    2.5.<\/strong> In the event of a conflict between these terms and conditions and a separate written agreement, quotation, purchase order or approved Ticket, the more specific document shall prevail to the extent that it expressly deviates from these terms and conditions.<\/p>\n\n\n\n

    2.6.<\/strong> All documents forming part of the cooperation, including quotations, approved Tickets, purchase orders, data processing agreements and service level agreements, shall together constitute the agreement between the parties.<\/p>\n\n\n\n

    Article 3. Subject Matter of the Agreement<\/strong><\/h2>\n\n\n\n

    3.1.<\/strong> Canyon Clan makes the Platform available as a software-as-a-service solution that can evolve according to the needs of the Customer and its user group.<\/p>\n\n\n\n

    3.2.<\/strong> The Customer receives a non-exclusive, non-transferable and temporary right to use the Platform and the Modules activated for it, for the duration of the agreement and within the agreed conditions of use.<\/p>\n\n\n\n

    3.3.<\/strong> The agreement does not transfer source code, intellectual property rights, technical know-how, architecture, designs, frameworks, libraries or any other rights of Canyon Clan, unless expressly agreed otherwise in writing.<\/p>\n\n\n\n

    3.4.<\/strong> The Platform is an evolving framework. Functionalities may be added, changed, improved, replaced or removed for technical, commercial, security-related, legal, operational or product-related reasons.<\/p>\n\n\n\n

    3.5.<\/strong> Canyon Clan is subject to a best-efforts obligation, unless a result obligation has been expressly agreed in writing for a specific service.<\/p>\n\n\n\n

    Article 4. Licence and Right of Use<\/strong><\/h2>\n\n\n\n

    4.1.<\/strong> The Customer may use the Platform solely for its own internal professional purposes and within the agreed scope, number of Users, entities, volumes and functionalities.<\/p>\n\n\n\n

    4.2.<\/strong> The Customer may not sell, rent, sublicense, copy, reverse-engineer, decompile or modify the Platform outside the permitted configuration options.<\/p>\n\n\n\n

    4.3.<\/strong> The Customer may not make the Platform or any part of it available to third parties without the prior written consent of Canyon Clan, except to Users acting on behalf of the Customer.<\/p>\n\n\n\n

    4.4.<\/strong> Access to the Platform is conditional upon payment of the applicable fees and compliance with these terms and conditions.<\/p>\n\n\n\n

    4.5.<\/strong> Canyon Clan may impose technical and contractual restrictions, including limits on Users, storage, API calls, data processing, integrations, support requests, bandwidth, AI usage or other capacities, provided that such restrictions reasonably relate to the selected subscription or the use of the Platform.<\/p>\n\n\n\n

    4.6.<\/strong> The Customer is responsible for all use taking place through its accounts, Users or access credentials, except in the event of proven misuse that cannot be attributed to the Customer.<\/p>\n\n\n\n

    Article 5. Requests and Tickets<\/strong><\/h2>\n\n\n\n

    5.1.<\/strong> The Customer and its Users may submit Requests through the Platform or through other communication channels accepted by Canyon Clan.<\/p>\n\n\n\n

    5.2.<\/strong> A Request must be described with sufficient clarity and completeness. Canyon Clan may request additional information, reformulate or refine the Request, divide it into several Tickets or combine it with existing Tickets.<\/p>\n\n\n\n

    5.3.<\/strong> Canyon Clan is not obliged to accept every Request.<\/p>\n\n\n\n

    5.4.<\/strong> Canyon Clan may refuse, postpone or modify a Request where, among other things, it:<\/p>\n\n\n\n

    a. is not technically feasible;
    b. falls outside the product vision or agreed scope;
    c. jeopardises the stability, security or maintainability of the Platform;
    d. is disproportionately complex or risky;
    e. may infringe third-party rights;
    f. conflicts with legislation or good practices;
    g. is incompatible with reasonable commercial terms;
    h. depends on information, access or cooperation that has not been provided.<\/p>\n\n\n\n

    5.5.<\/strong> Requests may be performed by software developers, analysts, designers, AI systems, subcontractors, employees or partners appointed by Canyon Clan.<\/p>\n\n\n\n

    5.6.<\/strong> The submission of a Request does not in itself create a right to performance.<\/p>\n\n\n\n

    5.7.<\/strong> A Request shall only be scheduled or performed after acceptance by Canyon Clan and, where applicable, after approval by the Customer of the related scope, price, payment structure and conditions.<\/p>\n\n\n\n

    Article 6. Pricing<\/strong><\/h2>\n\n\n\n

    6.1.<\/strong> When a Request is submitted or processed, a price indication or price proposal may be prepared through an automated, semi-automated or manual process.<\/p>\n\n\n\n

    6.2.<\/strong> The price may be determined on the basis of, among other things:<\/p>\n\n\n\n

    a. the estimated analysis and development time;
    b. the technical and functional complexity;
    c. the added value for the Customer;
    d. the reusability within the Platform;
    e. the impact on maintenance and support;
    f. infrastructure, licence, AI and API costs;
    g. security and compliance risks;
    h. urgency and scheduling;
    i. dependencies on third parties;
    j. market-standard rates.<\/p>\n\n\n\n

    6.3.<\/strong> A price indication is not binding until it has been confirmed by Canyon Clan or until it is clear from the communication that Canyon Clan has accepted performance at that price.<\/p>\n\n\n\n

    6.4.<\/strong> Canyon Clan may correct an automatically or manually generated price proposal in the event of an obvious error, incomplete information, an incorrect estimate, a changed scope, changed circumstances or unforeseen technical circumstances.<\/p>\n\n\n\n

    6.5.<\/strong> The price may consist of:<\/p>\n\n\n\n

    a. a One-off Fee;
    b. an Initial Module Fee;
    c. a Recurring Fee;
    d. a Maintenance Fee;
    e. a usage-based fee;
    f. a combination of these pricing structures.<\/p>\n\n\n\n

    6.6.<\/strong> The applicable pricing structure shall be stated in the Ticket, quotation, purchase order, Platform or a separate agreement.<\/p>\n\n\n\n

    6.7.<\/strong> Where an Initial Module Fee is paid monthly over an agreed period of time or as predicted as standard payment over twenty-four months, each monthly payment constitutes part of one previously agreed total price for the Module. This payment structure is not a monthly cancellable subscription for the development of the Module.<\/p>\n\n\n\n

    6.8.<\/strong> Unless stated otherwise, the total Initial Module Fee under a monthly payment structure shall be calculated as twenty-four times the agreed monthly amount with official INDEX fee, calculated to Module Fee every 12 months.<\/p>\n\n\n\n

    Article 7. Approval of Tickets, Quotations and Changes<\/strong><\/h2>\n\n\n\n

    7.1.<\/strong> A Ticket, price proposal, quotation, change or extension shall be deemed approved once the Customer confirms it:<\/p>\n\n\n\n

    a. through the Platform;
    b. by email;
    c. through a message in a communication channel used by the parties;
    d. through a Ticket comment;
    e. through a purchase order;
    f. by making payment;
    g. by expressly requesting that performance begin.<\/p>\n\n\n\n

    7.2.<\/strong> A written or digital confirmation shall have the same contractual value as a signature, provided that the communication reasonably demonstrates that the Customer agrees to the content, scope, price or performance.<\/p>\n\n\n\n

    7.3.<\/strong> Payment of a specific amount implies approval of the related Request, Ticket, price proposal, invoice or order.<\/p>\n\n\n\n

    7.4.<\/strong> Payment of the Base Licence Fee does not automatically imply approval of separate additional Requests, unless this is clear from the context.<\/p>\n\n\n\n

    7.5.<\/strong> A person granting approval through the Customer\u2019s account, a business email address of the Customer or a communication channel used by the Customer shall be deemed authorised to do so, unless the Customer has notified Canyon Clan otherwise in writing in advance.<\/p>\n\n\n\n

    7.6.<\/strong> The Customer is responsible for its internal approval processes, budget control and authorisations.<\/p>\n\n\n\n

    7.7.<\/strong> Internal restrictions of the Customer cannot be invoked against Canyon Clan where Canyon Clan could reasonably rely on the approval received.<\/p>\n\n\n\n

    7.8.<\/strong> Following approval, changes to the scope, priority, timing or requirements may result in a revised price proposal and schedule.<\/p>\n\n\n\n

    Article 8. Performance, Delivery and Acceptance<\/strong><\/h2>\n\n\n\n

    8.1.<\/strong> A Ticket may state an indicative performance period, start date or delivery date. These timeframes are indicative and do not constitute a binding result obligation, unless expressly agreed otherwise in writing.<\/p>\n\n\n\n

    8.2.<\/strong> Canyon Clan shall process Requests within a reasonable period, taking into account complexity, availability, priority, technical dependencies, external parties, testing, Customer feedback and general scheduling.<\/p>\n\n\n\n

    8.3.<\/strong> A Module or Request shall be considered delivered when, depending on the nature of the service, it:<\/p>\n\n\n\n

    a. is made available in a testing or production environment;
    b. is activated for the Customer;
    c. is demonstrated to the Customer or submitted for review;
    d. is delivered as a file, report, configuration or technical deliverable;
    e. is made available in another agreed manner.<\/p>\n\n\n\n

    8.4.<\/strong> Canyon Clan may deliver Tickets in phases, activate them temporarily in beta, first make them available in a testing environment or deliver an initial version with limited functionality where this fits within an iterative development approach.<\/p>\n\n\n\n

    8.5.<\/strong> Timeframes may be extended where the Customer fails to provide feedback, information, access, data, content, validation or approval in a timely manner.<\/p>\n\n\n\n

    8.6.<\/strong> Timeframes may also be extended in the event of technical dependencies, changed requirements, unforeseen circumstances or events outside the reasonable control of Canyon Clan.<\/p>\n\n\n\n

    8.7.<\/strong> Where a Module is ready for activation but activation is delayed solely by an act or omission of the Customer, Canyon Clan may consider the Module delivered from the date on which it notified the Customer in writing that the Module was ready.<\/p>\n\n\n\n

    8.8.<\/strong> The Customer undertakes to test delivered functionalities as soon as possible and to provide substantiated feedback.<\/p>\n\n\n\n

    8.9.<\/strong> In the absence of substantiated comments within eight calendar days following delivery, the delivery shall be deemed accepted, unless:<\/p>\n\n\n\n

    a. another acceptance period has been agreed in writing; or
    b. the defect could not reasonably have been identified within that period.<\/p>\n\n\n\n

    8.10.<\/strong> Acceptance shall not be prevented by minor errors or imperfections that do not materially interfere with the normal use of the delivered functionality.<\/p>\n\n\n\n

    8.11.<\/strong> Demonstrable defects compared with the approved scope shall be handled in accordance with Article 12.<\/p>\n\n\n\n

    8.12.<\/strong> Requested improvements, changed expectations, additional validations, new situations or extensions following approval shall be treated as a new or amended Request.<\/p>\n\n\n\n

    8.13.<\/strong> Delivery or acceptance does not involve the transfer of source code or intellectual property rights.<\/p>\n\n\n\n

    Article 9. Subscription, Module Fees and Maintenance<\/strong><\/h2>\n\n\n\n

    9.1. Base Licence Fee<\/strong><\/h3>\n\n\n\n

    9.1.1.<\/strong> A monthly Base Licence Fee is payable for the use of the Platform, unless agreed otherwise in writing.<\/p>\n\n\n\n

    9.1.2.<\/strong> The Base Licence Fee may include, among other things:<\/p>\n\n\n\n

    a. access to the base Platform;
    b. hosting and technical availability;
    c. standard updates;
    d. standard security;
    e. basic usage within agreed limits;
    f. reasonable standard support.<\/p>\n\n\n\n

    9.1.3.<\/strong> The Base Licence Fee is separate from fees for additional Modules, Requests, integrations, capacity, usage or specific services.<\/p>\n\n\n\n

    9.2. Additional Costs<\/strong><\/h3>\n\n\n\n

    9.2.1.<\/strong> Additional Modules, integrations, dashboards, Users, storage capacity, API usage, AI usage, support packages or other extensions may give rise to a One-off Fee, Initial Module Fee, Recurring Fee, Maintenance Fee or a combination thereof.<\/p>\n\n\n\n

    9.2.2.<\/strong> Recurring costs shall apply from the first invoicing period following approval or activation, unless otherwise provided in the Ticket or quotation.<\/p>\n\n\n\n

    9.3. Initial Module Period of Twenty-Four Months<\/strong><\/h3>\n\n\n\n

    9.3.1.<\/strong> Unless agreed otherwise in writing, each paid Module shall be subject to an Initial Module Period of twenty-four months.<\/p>\n\n\n\n

    9.3.2.<\/strong> The Initial Module Period shall begin on:<\/p>\n\n\n\n

    a. the date stated in the Ticket, quotation or order confirmation;
    b. in the absence of a stated date, the date on which the Module is first made available in production; or
    c. where activation is delayed solely by the Customer, the date on which Canyon Clan notified the Customer that the Module was ready for activation.<\/p>\n\n\n\n

    9.3.3.<\/strong> Each Module has its own Initial Module Period and may therefore have a different start and end date.<\/p>\n\n\n\n

    9.3.4.<\/strong> Where the Initial Module Fee is paid monthly, the agreed development and implementation price is spread over twenty-four monthly payments.<\/p>\n\n\n\n

    9.3.5.<\/strong> The Customer acknowledges that the Initial Module Fee relates to an investment already made or reserved for analysis, development, configuration, implementation and provision, and not solely to the use of the Module during one individual month.<\/p>\n\n\n\n

    9.4. Ending during the Initial Module Period<\/strong><\/h3>\n\n\n\n

    9.4.1.<\/strong> The Customer may terminate the agreement or a separate Module in accordance with Article 25.<\/p>\n\n\n\n

    9.4.2.<\/strong> Termination during the Initial Module Period does not end the obligation to pay the Initial Module Fee in total.<\/p>\n\n\n\n

    9.4.3.<\/strong> Where the agreement or relevant Module ends before expiry of the Initial Module Period as a result of:<\/p>\n\n\n\n

    a. termination by the Customer;
    b. a decision by the Customer to stop using the Platform;
    c. ending or suspension resulting from a contractual breach by the Customer;
    d. non-payment, misuse or another cause attributable to the Customer,<\/p>\n\n\n\n

    the unpaid balance of the Initial Module Fee shall become due and payable.<\/p>\n\n\n\n

    9.4.4.<\/strong> The unpaid balance shall in principle be calculated by multiplying the number of remaining months of the Initial Module Period by the most recently applicable monthly amount of the Initial Module Fee.<\/p>\n\n\n\n

    9.4.5.<\/strong> Variable usage costs that are no longer incurred after the Effective End Date shall not be charged as future usage.<\/p>\n\n\n\n

    9.4.6.<\/strong> Payment of the remaining balance of the Initial Module Fee shall not be considered a termination penalty, but payment of the outstanding balance of the agreed development and implementation price.<\/p>\n\n\n\n

    9.5. Maintenance Phase during and\/or after Twenty-Four Months<\/strong><\/h3>\n\n\n\n

    9.5.1.<\/strong> Where a Module remains active after expiry of the Initial Module Period, it shall automatically enter the Maintenance Phase.<\/p>\n\n\n\n

    9.5.2.<\/strong> A monthly Maintenance Fee shall be payable during the Maintenance Phase.<\/p>\n\n\n\n

    9.5.3.<\/strong> Unless agreed otherwise in writing, the Maintenance Fee shall amount to thirty per cent of the most recently applicable monthly Initial Module Fee.<\/p>\n\n\n\n

    9.5.4.<\/strong> Where the Initial Module Fee was paid in full in advance, as a one-off amount or in unequal installments, the standard monthly reference amount for the Maintenance Fee shall be calculated by dividing the total Initial Module Fee by twenty-four.<\/p>\n\n\n\n

    9.5.5.<\/strong> Before the Maintenance Phase starts, Canyon Clan may propose a different Maintenance Fee based on objective criteria, including:<\/p>\n\n\n\n

    a. the technical complexity of the Module;
    b. the maintenance requirements;
    c. security requirements;
    d. infrastructure usage;
    e. external integrations and API dependencies;
    f. required licences;
    g. the frequency of updates;
    h. the expected support burden;
    i. the business or operational impact of the Module.<\/p>\n\n\n\n

    9.5.6.<\/strong> A different Maintenance Fee shall, where reasonably possible, be communicated at least sixty calendar days before it takes effect.<\/p>\n\n\n\n

    9.5.7.<\/strong> Where the Customer does not accept a proposed different Maintenance Fee, it may request that the relevant Module be deactivated no later than the end of the Initial Module Period or following the applicable notice period.<\/p>\n\n\n\n

    9.5.8.<\/strong> Where the Module is technically interconnected with other functionalities, Canyon Clan may indicate in advance that deactivation:<\/p>\n\n\n\n

    a. requires additional work;
    b. affects certain other functionalities;
    c. is not possible without ending or modifying a broader service.<\/p>\n\n\n\n

    9.6. Scope of the Maintenance Phase<\/strong><\/h3>\n\n\n\n

    9.6.1.<\/strong> The Maintenance Fee may include, among other things:<\/p>\n\n\n\n

    a. keeping the Module technically available;
    b. compatibility updates within the Platform;
    c. general security updates;
    d. necessary technical corrections;
    e. limited modifications required to keep the Module operational within the existing scope;
    f. monitoring and maintenance of the relevant technical components.<\/p>\n\n\n\n

    9.6.2.<\/strong> The Maintenance Fee does not automatically include:<\/p>\n\n\n\n

    a. new functionalities;
    b. functional extensions;
    c. changed business processes;
    d. new reports or dashboards;
    e. migrations;
    f. substantial redevelopment;
    g. specific assistance or training;
    h. changes caused by third parties or external APIs;
    i. new legal or sector-specific requirements;
    j. support outside the agreed support package.<\/p>\n\n\n\n

    9.6.3.<\/strong> Such work may be charged as a separate Request.<\/p>\n\n\n\n

    9.7. Price Adjustments<\/strong><\/h3>\n\n\n\n

    9.7.1.<\/strong> Canyon Clan may periodically adjust its prices to take account of, among other things:<\/p>\n\n\n\n

    a. indexation every 12 months;
    b. increased labour and personnel costs;
    c. hosting and infrastructure costs;
    d. licence, AI and API costs;
    e. changed market prices;
    f. expanded usage;
    g. an increased support or maintenance burden.<\/p>\n\n\n\n

    9.7.2.<\/strong> Price changes to existing Recurring Fees shall be announced in advance, unless the change directly results from a Ticket, extension or change in usage approved by the Customer.<\/p>\n\n\n\n

    9.7.3.<\/strong> All prices are exclusive of VAT and other applicable taxes, unless expressly stated otherwise.<\/p>\n\n\n\n

    Article 10. Payment Mandate, Automatic Collection and Invoicing<\/strong><\/h2>\n\n\n\n

    10.1.<\/strong> The Customer undertakes to activate and maintain a valid payment mandate through a payment provider offered by Canyon Clan, including Mollie, unless another payment method has been agreed in writing.<\/p>\n\n\n\n

    10.2.<\/strong> The payment mandate authorises Canyon Clan to automatically collect, among other things:<\/p>\n\n\n\n

    a. Base Licence Fees;
    b. Initial Module Fees;
    c. Maintenance Fees;
    d. Recurring Fees;
    e. approved One-off Fees;
    f. approved Requests and Tickets;
    g. AI, API, storage and other usage costs;
    h. the Final Settlement.<\/p>\n\n\n\n

    10.3.<\/strong> The Base Licence Fee and other Recurring Fees shall be charged monthly, unless agreed otherwise.<\/p>\n\n\n\n

    10.4.<\/strong> One-off costs may be automatically collected after the relevant Ticket, Request, price proposal or order has been approved.<\/p>\n\n\n\n

    10.5.<\/strong> Recurring costs or subscription increases shall be automatically collected from the applicable invoicing period.<\/p>\n\n\n\n

    10.6.<\/strong> Invoices are payable on the invoice date or on the due date stated on the invoice. Where no due date is stated, a payment period of eight calendar days shall apply.<\/p>\n\n\n\n

    10.7.<\/strong> Invoices shall be issued electronically, including through Peppol where legally required or practically possible.<\/p>\n\n\n\n

    10.8.<\/strong> The Customer is responsible for timely providing and keeping up to date correct invoicing details, including:<\/p>\n\n\n\n

    a. the legal name;
    b. the company registration and VAT number;
    c. the invoicing address;
    d. Peppol details;
    e. the invoicing email address;
    f. any internal references or purchase order numbers.<\/p>\n\n\n\n

    10.9.<\/strong> The absence or late provision of an internal reference or purchase order number shall not suspend the payment obligation where the order or service was validly approved.<\/p>\n\n\n\n

    Final Settlement<\/strong><\/h3>\n\n\n\n

    10.10.<\/strong> When the agreement or a Module ends, Canyon Clan shall prepare a Final Settlement.<\/p>\n\n\n\n

    10.11.<\/strong> The Final Settlement may include:<\/p>\n\n\n\n

    a. outstanding invoices;
    b. due but unpaid amounts;
    c. work performed but not yet invoiced;
    d. approved Requests and Tickets;
    e. AI, API, storage or other usage not yet settled;
    f. the remaining balance of Initial Module Fees;
    g. costs for export, migration or transfer;
    h. other due and payable amounts.<\/p>\n\n\n\n

    10.12.<\/strong> Canyon Clan may collect the correctly invoiced and due Final Settlement through the existing payment mandate.<\/p>\n\n\n\n

    10.13.<\/strong> The payment mandate shall remain valid following the Effective End Date to the extent necessary to collect the Final Settlement and other payment obligations that have already arisen.<\/p>\n\n\n\n

    10.14.<\/strong> Canyon Clan shall endeavour to include all determinable amounts in the final direct debit or automatic collection.<\/p>\n\n\n\n

    10.15.<\/strong> Amounts that could not reasonably be determined at that time, including externally reported usage received later, may be charged through an additional invoice.<\/p>\n\n\n\n

    Failed and Late Payments<\/strong><\/h3>\n\n\n\n

    10.16.<\/strong> If an automatic payment fails, the Customer remains liable for payment of the full amount due.<\/p>\n\n\n\n

    10.17.<\/strong> Canyon Clan may resubmit the collection and may suspend access to the Platform, the performance of open Tickets or the provision of additional services until full payment has been received.<\/p>\n\n\n\n

    10.18.<\/strong> Any dispute concerning an invoice or charged amount must be reported in writing and with reasons within eight calendar days following the invoice date.<\/p>\n\n\n\n

    10.19.<\/strong> A dispute must state at least:<\/p>\n\n\n\n

    a. the invoice or amount being disputed;
    b. the precise disputed portion;
    c. the specific reason for the dispute;
    d. the available supporting evidence.<\/p>\n\n\n\n

    10.20.<\/strong> The undisputed portion of an invoice shall remain payable at all times.<\/p>\n\n\n\n

    10.21.<\/strong> In the absence of a timely and substantiated dispute, the invoice shall be deemed accepted, except in the event of a proven clerical error.<\/p>\n\n\n\n

    10.22.<\/strong> In the event of late payment, the Customer shall automatically and without prior notice be liable for the interest and reasonable recovery costs permitted under the applicable legislation on late payment in commercial transactions.<\/p>\n\n\n\n

    10.23.<\/strong> Reasonable costs of recovery, bailiffs, lawyers and legal proceedings may be recovered to the extent permitted by law.<\/p>\n\n\n\n

    Article 11. Hosting, Availability and Platform Maintenance<\/strong><\/h2>\n\n\n\n

    11.1.<\/strong> The Platform shall be hosted on servers located in Belgium, within the European Economic Area or within another infrastructure managed or selected by Canyon Clan for which appropriate safeguards apply, unless agreed otherwise in writing.<\/p>\n\n\n\n

    11.2.<\/strong> Canyon Clan is responsible for the technical management of the hosting environment, except for components managed by the Customer or third parties.<\/p>\n\n\n\n

    11.3.<\/strong> Canyon Clan shall use reasonable efforts to keep the Platform available, secure and performant.<\/p>\n\n\n\n

    11.4.<\/strong> Uninterrupted or error-free availability is not guaranteed, unless a separate service level agreement has been concluded in writing.<\/p>\n\n\n\n

    11.5.<\/strong> Canyon Clan may perform maintenance, updates, migrations, security patches, back-ups, restarts and technical modifications.<\/p>\n\n\n\n

    11.6.<\/strong> As a result, the Platform may temporarily be restricted or unavailable.<\/p>\n\n\n\n

    11.7.<\/strong> Planned maintenance shall be announced in advance where reasonably possible.<\/p>\n\n\n\n

    11.8.<\/strong> Urgent maintenance for security, stability or continuity reasons may be carried out without prior notice.<\/p>\n\n\n\n

    11.9.<\/strong> Canyon Clan shall not be liable for interruptions or delays caused by:<\/p>\n\n\n\n

    a. internet or network outages;
    b. hosting issues outside its reasonable control;
    c. cyberattacks;
    d. force majeure;
    e. incorrect use;
    f. external APIs or services;
    g. failures by the Customer;
    h. necessary urgent security measures.<\/p>\n\n\n\n

    Article 12. Support and Incidents<\/strong><\/h2>\n\n\n\n

    12.1.<\/strong> The Customer may report support requests and incidents through the channels designated by Canyon Clan.<\/p>\n\n\n\n

    12.2.<\/strong> Canyon Clan shall process support requests within a reasonable period, taking into account severity, impact, urgency, the subscription, availability and technical complexity.<\/p>\n\n\n\n

    12.3.<\/strong> Response and resolution times are indicative, unless a separate service level agreement has been concluded.<\/p>\n\n\n\n

    12.4.<\/strong> Support for standard use, demonstrable bugs and general disruptions may, within reasonable limits, be included in the Base Licence Fee or Maintenance Fee.<\/p>\n\n\n\n

    12.5.<\/strong> Support may be charged separately where it results from:<\/p>\n\n\n\n

    a. incorrect or non-standard use;
    b. insufficient training;
    c. modifications by the Customer or third parties;
    d. issues in external systems;
    e. incorrect data or configuration;
    f. data corrections or imports;
    g. specific assistance;
    h. investigations in which no defect in the Platform is identified.<\/p>\n\n\n\n

    12.6.<\/strong> A bug is a demonstrable deviation from the expressly agreed or reasonably expected operation of the Platform.<\/p>\n\n\n\n

    12.7.<\/strong> A requested improvement, process change, additional validation, new integration, additional reporting or changed expectation shall be treated as a Request and may be chargeable.<\/p>\n\n\n\n

    12.8.<\/strong> Canyon Clan may provide a temporary workaround pending a structural solution.<\/p>\n\n\n\n

    12.9.<\/strong> The Customer must sufficiently document incidents, including a description, steps to reproduce the issue, screenshots, relevant data and the observed impact.<\/p>\n\n\n\n

    Article 13. Third-Party Integrations<\/strong><\/h2>\n\n\n\n

    13.1.<\/strong> The Platform may connect with external systems, APIs, data sources, payment providers, accounting software, CRM systems, AI services, email services, authentication services or other third parties.<\/p>\n\n\n\n

    13.2.<\/strong> The Customer is responsible for valid accounts, licences, API keys, access rights, permissions and correct configuration of external systems, unless agreed otherwise.<\/p>\n\n\n\n

    13.3.<\/strong> Canyon Clan is not responsible for the availability, operation, price changes, API changes, restrictions, errors, data loss or discontinuation of third-party services.<\/p>\n\n\n\n

    13.4.<\/strong> Canyon Clan cannot guarantee that an integration will continue to function where a third party changes its system, terms, API, pricing model or security requirements.<\/p>\n\n\n\n

    13.5.<\/strong> Additional work required as a result of changes by third parties, changed APIs, expired keys, changed access rights or changed configurations may be charged separately.<\/p>\n\n\n\n

    13.6.<\/strong> Costs charged by external suppliers directly or through Canyon Clan may be passed on to the Customer.<\/p>\n\n\n\n

    Article 14. Customer Data and Customer Responsibilities<\/strong><\/h2>\n\n\n\n

    14.1.<\/strong> All Customer Data shall remain the property of the Customer or the relevant third-party rights holder.<\/p>\n\n\n\n

    14.2.<\/strong> Canyon Clan does not acquire ownership of Customer Data.<\/p>\n\n\n\n

    14.3.<\/strong> The Customer grants Canyon Clan the right to process Customer Data to the extent necessary to provide, secure, maintain, support, improve and invoice the Platform and related services.<\/p>\n\n\n\n

    14.4.<\/strong> The Customer is responsible for:<\/p>\n\n\n\n

    a. the accuracy and completeness of Customer Data;
    b. the legality and quality of Customer Data;
    c. the necessary rights and permissions;
    d. the content of files, documents, images and texts;
    e. the lawful processing of personal data.<\/p>\n\n\n\n

    14.5.<\/strong> The Customer remains responsible for decisions, actions, reports, conclusions and business processes based on data, dashboards, calculations, automations or output from the Platform.<\/p>\n\n\n\n

    14.6.<\/strong> The Customer must verify the suitability and accuracy of important output before relying on it for operational, legal, medical, financial or other important decisions.<\/p>\n\n\n\n

    14.7.<\/strong> The Customer is responsible for managing its Users, roles, access rights, passwords, internal authorisations and the security of its devices and accounts.<\/p>\n\n\n\n

    14.8.<\/strong> The Customer shall immediately inform Canyon Clan if it suspects that data, accounts or access credentials have been used without authorisation.<\/p>\n\n\n\n

    Article 15. Intellectual Property<\/strong><\/h2>\n\n\n\n

    15.1.<\/strong> All intellectual property rights in the Platform, software, source code, object code, architecture, database structures, workflows, generic Modules, designs, documentation, interfaces, methodologies, know-how, templates, analyses, algorithms and technical implementations shall remain the property of Canyon Clan or its licensors.<\/p>\n\n\n\n

    15.2.<\/strong> The Customer only receives the right of use described in these terms and conditions.<\/p>\n\n\n\n

    15.3.<\/strong> No intellectual property rights are transferred unless expressly agreed otherwise in writing.<\/p>\n\n\n\n

    15.4.<\/strong> Requests, ideas, feedback, suggestions and functional needs of the Customer may be used by Canyon Clan for the further development of the Platform.<\/p>\n\n\n\n

    15.5.<\/strong> The technical implementation, generic functionalities, Modules and improvements developed as a result shall remain the property of Canyon Clan.<\/p>\n\n\n\n

    15.6.<\/strong> The Customer retains its rights in:<\/p>\n\n\n\n

    a. its own data;
    b. business information;
    c. materials supplied by it;
    d. logos and brand elements;
    e. texts and documents;
    f. other pre-existing Customer content.<\/p>\n\n\n\n

    15.7.<\/strong> Unless agreed otherwise in writing, the Customer has no right to exclusivity in relation to a Request, Module, workflow, integration, dashboard or other functionality.<\/p>\n\n\n\n

    15.8.<\/strong> Canyon Clan may offer similar, generic or derived functionalities to other customers, provided that no confidential information or Customer Data is disclosed.<\/p>\n\n\n\n

    15.9.<\/strong> The Customer may not remove or alter any copyright notices, trademarks, trade names or other proprietary notices.<\/p>\n\n\n\n

    Article 16. Confidentiality<\/strong><\/h2>\n\n\n\n

    16.1.<\/strong> The parties undertake to keep the other party\u2019s confidential information secret and to use it solely for the performance of the agreement.<\/p>\n\n\n\n

    16.2.<\/strong> Confidential information includes, among other things:<\/p>\n\n\n\n

    a. business information;
    b. Customer Data;
    c. prices and commercial terms;
    d. technical information and source code;
    e. roadmaps and strategy;
    f. processes and know-how;
    g. reports and documents;
    h. access credentials and passwords;
    i. all information that should reasonably be considered confidential.<\/p>\n\n\n\n

    16.3.<\/strong> The confidentiality obligation does not apply to information that:<\/p>\n\n\n\n

    a. is publicly known without fault of the receiving party;
    b. was lawfully received from a third party;
    c. was independently developed;
    d. is disclosed with permission;
    e. must be disclosed pursuant to legislation, a court decision or an order from a public authority.<\/p>\n\n\n\n

    16.4.<\/strong> Where disclosure is legally required, the receiving party shall inform the other party in advance, to the extent legally permitted.<\/p>\n\n\n\n

    16.5.<\/strong> Canyon Clan may use anonymised and non-confidential insights for product development, internal training, marketing, sales and example cases, provided that no personal data or commercially sensitive information of the Customer is disclosed.<\/p>\n\n\n\n

    16.6.<\/strong> The confidentiality obligations shall remain in force after the agreement ends for as long as the information remains confidential.<\/p>\n\n\n\n

    Article 17. References, Use Cases and Marketing<\/strong><\/h2>\n\n\n\n

    17.1.<\/strong> Canyon Clan may use the Customer\u2019s name and logo as a commercial reference, unless the Customer objects in writing.<\/p>\n\n\n\n

    17.2.<\/strong> Canyon Clan may use completed solutions, Modules, Requests and insights as anonymised examples, use cases or inspiration for product development, marketing and sales.<\/p>\n\n\n\n

    17.3.<\/strong> No confidential information, personal data or commercially sensitive information shall be disclosed.<\/p>\n\n\n\n

    17.4.<\/strong> An extensive public case study containing recognisable substantive details about the Customer shall only be published:<\/p>\n\n\n\n

    a. following consultation with the Customer;
    b. with the Customer\u2019s permission; or
    c. where the Customer has otherwise clearly agreed to publication.<\/p>\n\n\n\n

    Article 18. Privacy and Processing of Personal Data<\/strong><\/h2>\n\n\n\n

    18.1.<\/strong> To the extent Canyon Clan processes personal data on behalf of the Customer, the Customer shall in principle act as controller and Canyon Clan as processor, unless the specific context requires otherwise.<\/p>\n\n\n\n

    18.2.<\/strong> The parties shall comply with applicable data protection legislation, including the General Data Protection Regulation.<\/p>\n\n\n\n

    18.3.<\/strong> Personal data shall be processed for the provision, security, maintenance, support, invoicing and improvement of the Platform and related services, or in accordance with documented instructions from the Customer.<\/p>\n\n\n\n

    18.4.<\/strong> Canyon Clan shall implement appropriate technical and organisational measures to protect personal data against unauthorised access, loss, alteration, destruction or disclosure.<\/p>\n\n\n\n

    18.5.<\/strong> In selecting these measures, account shall be taken of:<\/p>\n\n\n\n

    a. the nature and scope of the processing;
    b. the risks to data subjects;
    c. the state of the art;
    d. implementation costs;
    e. the specific services.<\/p>\n\n\n\n

    18.6.<\/strong> Canyon Clan may engage subprocessors for, among other things:<\/p>\n\n\n\n

    a. hosting;
    b. payment processing;
    c. invoicing;
    d. monitoring and logging;
    e. support;
    f. email;
    g. back-ups;
    h. security;
    i. AI processing;
    j. other necessary services.<\/p>\n\n\n\n

    18.7.<\/strong> Canyon Clan shall impose appropriate privacy, security and confidentiality obligations on subprocessors.<\/p>\n\n\n\n

    18.8.<\/strong> The Customer grants general authorisation for the engagement of subprocessors.<\/p>\n\n\n\n

    18.9.<\/strong> Upon request, Canyon Clan shall provide information regarding the main subprocessors relevant to the services.<\/p>\n\n\n\n

    18.10.<\/strong> In the event of a reasonable suspicion of a personal data breach involving Customer Data or personal data of the Customer, Canyon Clan shall inform the Customer without undue delay, provided that Canyon Clan is aware of the incident and notification is legally required.<\/p>\n\n\n\n

    18.11.<\/strong> The Customer is responsible for:<\/p>\n\n\n\n

    a. the legal basis for the processing;
    b. information obligations;
    c. retention periods;
    d. handling data subject rights;
    e. the substantive lawfulness of the personal data.<\/p>\n\n\n\n

    18.12.<\/strong> The provisions of Appendix 1 shall apply to the extent Canyon Clan acts as processor.<\/p>\n\n\n\n

    18.13.<\/strong> Where the parties enter into a separate data processing agreement, that data processing agreement shall prevail for data protection-related provisions.<\/p>\n\n\n\n

    Article 19. Security<\/strong><\/h2>\n\n\n\n

    19.1.<\/strong> Canyon Clan shall implement reasonable technical and organisational security measures to protect the Platform.<\/p>\n\n\n\n

    19.2.<\/strong> The Customer undertakes to:<\/p>\n\n\n\n

    a. use strong and unique passwords;
    b. use available multi-factor authentication where reasonable;
    c. properly manage access rights;
    d. promptly deactivate the accounts of departing employees;
    e. keep devices and browsers up to date and secure;
    f. immediately inform Canyon Clan in the event of suspected misuse.<\/p>\n\n\n\n

    19.3.<\/strong> The Customer may not perform security testing, penetration testing, scans, load testing or other technical tests without the prior written consent of Canyon Clan.<\/p>\n\n\n\n

    19.4.<\/strong> Canyon Clan may block access, terminate sessions, disable integrations or temporarily restrict accounts where necessary to protect the security, stability or integrity of the Platform.<\/p>\n\n\n\n

    19.5.<\/strong> Canyon Clan may retain reasonable usage and security logs for monitoring, incident investigation, support, invoicing and evidentiary purposes.<\/p>\n\n\n\n

    Article 20. Back-ups, Export and End of Access<\/strong><\/h2>\n\n\n\n

    20.1.<\/strong> Canyon Clan may create back-ups of the Platform and Customer Data in accordance with its internal procedures.<\/p>\n\n\n\n

    20.2.<\/strong> Back-ups are intended for recovery following technical incidents and do not constitute an individual archive service or an unlimited recovery guarantee for the Customer.<\/p>\n\n\n\n

    20.3.<\/strong> The Customer remains responsible for its own exports or archives where it is required to retain data for a specific legal or operational period.<\/p>\n\n\n\n

    20.4.<\/strong> During the agreement, the Customer may request a reasonable export of its Customer Data, provided that:<\/p>\n\n\n\n

    a. this is technically possible;
    b. this does not infringe third-party rights;
    c. this does not jeopardise the security or operation of the Platform.<\/p>\n\n\n\n

    One-Month Transition Period<\/strong><\/h3>\n\n\n\n

    20.5.<\/strong> Following the Effective End Date, Canyon Clan shall keep the Customer\u2019s account accessible on a limited basis for one month, where technically possible and reasonable.<\/p>\n\n\n\n

    20.6.<\/strong> The Transition Period is intended solely to allow the Customer to:<\/p>\n\n\n\n

    a. consult existing Customer Data;
    b. perform standard exports;
    c. download available documents;
    d. complete an agreed transfer.<\/p>\n\n\n\n

    20.7.<\/strong> Canyon Clan may place the account in a restricted or read-only mode during the Transition Period.<\/p>\n\n\n\n

    20.8.<\/strong> During the Transition Period, the Customer shall in principle not be entitled to:<\/p>\n\n\n\n

    a. submit new Requests;
    b. request new development;
    c. add new Users or integrations;
    d. request functional changes;
    e. receive regular operational support;
    f. continue unrestricted use of the Platform.<\/p>\n\n\n\n

    20.9.<\/strong> The Transition Period:<\/p>\n\n\n\n

    a. does not extend the agreement;
    b. does not postpone the Effective End Date;
    c. does not suspend the Final Settlement;
    d. does not create a new Initial Module Period.<\/p>\n\n\n\n

    20.10.<\/strong> Canyon Clan may refuse, shorten or immediately end the Transition Period in the event of:<\/p>\n\n\n\n

    a. a serious security risk;
    b. fraud or misuse;
    c. a legal obligation;
    d. an order from a competent authority;
    e. a serious contractual breach;
    f. a technically unacceptable risk.<\/p>\n\n\n\n

    20.11.<\/strong> The Customer must request or perform all necessary exports no later than the end of the Transition Period.<\/p>\n\n\n\n

    20.12.<\/strong> Following expiry of the Transition Period, Canyon Clan may permanently discontinue access.<\/p>\n\n\n\n

    20.13.<\/strong> Canyon Clan may subsequently delete Customer Data after a reasonable retention period, unless longer retention is necessary for:<\/p>\n\n\n\n

    a. legal or accounting obligations;
    b. security and fraud prevention;
    c. disputes and evidentiary purposes;
    d. the normal back-up cycle;
    e. other legitimate interests.<\/p>\n\n\n\n

    20.14.<\/strong> Assistance with export, migration, data analysis, specific reporting or transfer to a third party may be charged separately.<\/p>\n\n\n\n

    Article 21. Acceptable Use<\/strong><\/h2>\n\n\n\n

    21.1.<\/strong> The Customer may not use the Platform for illegal, harmful, misleading, discriminatory, fraudulent, infringing or unauthorised activities.<\/p>\n\n\n\n

    21.2.<\/strong> The Customer may not use the Platform to:<\/p>\n\n\n\n

    a. distribute malware or malicious code;
    b. overload systems;
    c. bypass security;
    d. access data belonging to other customers;
    e. perform unauthorised scraping;
    f. interfere with the normal operation of the Platform;
    g. infringe third-party rights.<\/p>\n\n\n\n

    21.3.<\/strong> Canyon Clan may restrict or suspend use where the Customer\u2019s use jeopardises the security, stability, reputation, legal position or commercial operation of Canyon Clan or the Platform.<\/p>\n\n\n\n

    21.4.<\/strong> In the event of structurally excessive usage outside the normal use of the selected subscription, Canyon Clan may:<\/p>\n\n\n\n

    a. impose reasonable fair-use restrictions;
    b. apply technical limits;
    c. propose an adjusted subscription or price;
    d. separately charge for the excessive usage.<\/p>\n\n\n\n

    Article 22. Platform Changes and Roadmap<\/strong><\/h2>\n\n\n\n

    22.1.<\/strong> Canyon Clan may continuously improve, modify, extend, restructure or optimise the Platform.<\/p>\n\n\n\n

    22.2.<\/strong> Canyon Clan may modify functionalities, interfaces, workflows, technical components or integrations where useful or necessary for:<\/p>\n\n\n\n

    a. security;
    b. stability;
    c. scalability;
    d. maintainability;
    e. product strategy;
    f. user experience;
    g. legal compliance;
    h. compatibility.<\/p>\n\n\n\n

    22.3.<\/strong> Canyon Clan shall use reasonable efforts not to remove essential functionalities without an alternative or reasonable transition period.<\/p>\n\n\n\n

    22.4.<\/strong> A transition period or alternative shall not be required where an immediate change is necessary for security, legal, technical or operational reasons.<\/p>\n\n\n\n

    22.5.<\/strong> Roadmaps, future plans, demonstrations, prototypes and product communications are indicative and do not constitute a binding commitment, unless expressly agreed otherwise in writing.<\/p>\n\n\n\n

    Article 23. Liability<\/strong><\/h2>\n\n\n\n

    23.1.<\/strong> Canyon Clan shall only be liable for proven direct loss that is the direct result of an attributable contractual breach by Canyon Clan.<\/p>\n\n\n\n

    23.2.<\/strong> To the extent permitted by law, Canyon Clan shall not be liable for:<\/p>\n\n\n\n

    a. indirect loss;
    b. consequential loss;
    c. loss of profit or revenue;
    d. reputational damage;
    e. loss of customers or opportunities;
    f. lost savings;
    g. business interruption;
    h. the cost of replacement services;
    i. loss of or damage to data;
    j. loss arising from decisions made on the basis of the Platform.<\/p>\n\n\n\n

    23.3.<\/strong> Canyon Clan shall not be liable for loss arising from:<\/p>\n\n\n\n

    a. inaccurate or incomplete Customer Data;
    b. incorrect use;
    c. unauthorised access through the Customer\u2019s accounts;
    d. third-party services or systems;
    e. modifications not performed by Canyon Clan;
    f. failure to follow instructions or warnings.<\/p>\n\n\n\n

    23.4.<\/strong> The total liability of Canyon Clan shall, to the extent permitted by law, be limited to the amount actually paid by the Customer to Canyon Clan for the relevant part of the services during the twelve months preceding the event giving rise to the loss.<\/p>\n\n\n\n

    23.5.<\/strong> The limitations of liability shall not apply to the extent liability cannot be excluded or limited under mandatory law, including in the event of wilful misconduct or fraud.<\/p>\n\n\n\n

    23.6.<\/strong> The Customer must inform Canyon Clan in writing of a loss event within a reasonable period after the Customer identified or should reasonably have identified the event.<\/p>\n\n\n\n

    23.7.<\/strong> The Customer shall take reasonable measures to prevent and limit loss.<\/p>\n\n\n\n

    23.8.<\/strong> The Customer shall indemnify Canyon Clan against third-party claims arising from:<\/p>\n\n\n\n

    a. Customer Data;
    b. incorrect or unlawful use;
    c. a breach of legislation by the Customer;
    d. an infringement of third-party rights by the Customer;
    e. decisions and processes for which the Customer is responsible.<\/p>\n\n\n\n

    Article 24. Force Majeure<\/strong><\/h2>\n\n\n\n

    24.1.<\/strong> Canyon Clan shall not be liable for delays or failures resulting from force majeure or circumstances outside its reasonable control.<\/p>\n\n\n\n

    24.2.<\/strong> Force majeure includes, among other things:<\/p>\n\n\n\n

    a. internet and network outages;
    b. hosting issues outside reasonable control;
    c. power failures;
    d. cyberattacks;
    e. strikes and labour disputes;
    f. serious illness or unavailability of essential employees;
    g. pandemics;
    h. fire and natural disasters;
    i. war and terrorism;
    j. government measures;
    k. failures by third parties;
    l. changes to or discontinuation of external APIs;
    m. disruptions to payment or invoicing infrastructure.<\/p>\n\n\n\n

    24.3.<\/strong> In the event of force majeure, the affected obligations shall be suspended for the duration of the force majeure event.<\/p>\n\n\n\n

    24.4.<\/strong> Canyon Clan may propose reasonable alternatives, workarounds or adjusted methods of performance.<\/p>\n\n\n\n

    24.5.<\/strong> Where a force majeure event makes a material part of the services impossible for an extended period, the parties may discuss a reasonable adjustment or ending of the affected part.<\/p>\n\n\n\n

    Article 25. Duration, Termination and Ending of the Agreement<\/strong><\/h2>\n\n\n\n

    25.1. Duration<\/strong><\/h3>\n\n\n\n

    25.1.1.<\/strong> The agreement shall be entered into for the duration stated in the quotation, purchase order, Platform or a separate agreement.<\/p>\n\n\n\n

    25.1.2.<\/strong> In the absence of a specified duration, the agreement shall be for an indefinite period, with monthly invoicing and a notice period of six months.<\/p>\n\n\n\n

    25.1.3.<\/strong> The duration of the general agreement is separate from the Initial Module Period of individual Modules.<\/p>\n\n\n\n

    25.2. Termination by the Customer<\/strong><\/h3>\n\n\n\n

    25.2.1.<\/strong> Unless agreed otherwise in writing, the Customer may terminate the general agreement or a separate Module subject to a notice period of six months.<\/p>\n\n\n\n

    25.2.2.<\/strong> The notice period shall begin on the first day of the invoicing period following receipt of the notice of termination.<\/p>\n\n\n\n

    25.2.3.<\/strong> Notice of termination must be given in writing through:<\/p>\n\n\n\n

    a. the relevant functionality provided in the Platform;
    b. email;
    c. registered letter;
    d. another written channel for which Canyon Clan confirms receipt.<\/p>\n\n\n\n

    25.2.4.<\/strong> The notice must clearly state:<\/p>\n\n\n\n

    a. which agreement or Module is being terminated;
    b. the Customer on whose behalf notice is being given;
    c. the requested end date, where applicable.<\/p>\n\n\n\n

    25.3. Consequences during the Notice Period<\/strong><\/h3>\n\n\n\n

    25.3.1.<\/strong> The agreement shall remain fully in force during the notice period.<\/p>\n\n\n\n

    25.3.2.<\/strong> The Base Licence Fee, Initial Module Fees, Maintenance Fees, usage costs and other Recurring Fees shall remain payable during the notice period.<\/p>\n\n\n\n

    25.3.3.<\/strong> The Customer shall retain access to the active services during the notice period, except where access is validly suspended in accordance with Article 26.<\/p>\n\n\n\n

    25.3.4.<\/strong> Canyon Clan is not obliged to accept new substantial Requests where it can reasonably be expected that they cannot be performed or supported before the Effective End Date.<\/p>\n\n\n\n

    25.4. Modules within the Initial Module Period<\/strong><\/h3>\n\n\n\n

    25.4.1.<\/strong> Where a Module is still within its Initial Module Period on the Effective End Date, the remaining balance of the Initial Module Fee shall remain payable in accordance with Article 9.<\/p>\n\n\n\n

    25.4.2.<\/strong> This balance shall be included in the Final Settlement and may be collected through the payment mandate.<\/p>\n\n\n\n

    25.4.3.<\/strong> Approved One-off Fees, ongoing Tickets, work already performed and other amounts due shall also remain payable.<\/p>\n\n\n\n

    25.5. Ending by Canyon Clan<\/strong><\/h3>\n\n\n\n

    25.5.1.<\/strong> Canyon Clan may terminate an agreement for an indefinite period subject to a notice period of six months, unless agreed otherwise in writing.<\/p>\n\n\n\n

    25.5.2.<\/strong> Canyon Clan may end or suspend the agreement or any part of it with immediate effect in the event of:<\/p>\n\n\n\n

    a. a serious contractual breach;
    b. non-payment;
    c. fraud or misuse;
    d. a serious security risk;
    e. infringement of intellectual property rights;
    f. breach of confidentiality;
    g. unlawful use;
    h. bankruptcy, liquidation or manifest insolvency, to the extent permitted by law;
    i. repeated non-compliance following a warning.<\/p>\n\n\n\n

    25.5.3.<\/strong> Where ending results from a breach attributable to the Customer, the remaining balance of the Initial Module Fees shall remain payable.<\/p>\n\n\n\n

    25.5.4.<\/strong> Where Canyon Clan ends the agreement without any breach by the Customer, future Initial Module Fees for the period following the Effective End Date shall not be charged, unless:<\/p>\n\n\n\n

    a. the parties agree otherwise in writing; or
    b. the Customer can continue using the relevant Module after the Effective End Date.<\/p>\n\n\n\n

    25.6. End of the Maintenance Phase<\/strong><\/h3>\n\n\n\n

    25.6.1.<\/strong> The Maintenance Phase of a Module shall end where:<\/p>\n\n\n\n

    a. the Module is validly terminated;
    b. the general agreement ends;
    c. the Module is permanently deactivated;
    d. Canyon Clan discontinues the Module for a valid reason.<\/p>\n\n\n\n

    25.6.2.<\/strong> Maintenance Fees shall remain payable until the Effective End Date of the relevant Module or agreement.<\/p>\n\n\n\n

    25.7. Transition Period<\/strong><\/h3>\n\n\n\n

    25.7.1.<\/strong> Following the Effective End Date, the one-month Transition Period provided for in Article 20 shall in principle apply.<\/p>\n\n\n\n

    25.7.2.<\/strong> Limited access during the Transition Period does not constitute continuation or tacit renewal of the agreement.<\/p>\n\n\n\n

    25.8. No Refund<\/strong><\/h3>\n\n\n\n

    25.8.1.<\/strong> The Customer shall not be entitled to a refund of fees already paid, except where:<\/p>\n\n\n\n

    a. required by law;
    b. agreed by the parties in writing;
    c. Canyon Clan has demonstrably charged an amount incorrectly.<\/p>\n\n\n\n

    25.8.2.<\/strong> Non-use of the Platform or a Module does not release the Customer from its payment obligations.<\/p>\n\n\n\n

    Article 26. Suspension<\/strong><\/h2>\n\n\n\n

    26.1.<\/strong> Canyon Clan may temporarily suspend all or part of the access to the Platform or the performance of services in the event of:<\/p>\n\n\n\n

    a. non-payment;
    b. misuse;
    c. a security risk;
    d. excessive usage;
    e. incomplete or inaccurate Customer information;
    f. a missing or withdrawn payment mandate;
    g. disputed authorisations;
    h. a breach of these terms and conditions;
    i. a legal or judicial obligation.<\/p>\n\n\n\n

    26.2.<\/strong> When imposing a suspension, Canyon Clan shall, where reasonable, take account of the seriousness, urgency and consequences of the situation.<\/p>\n\n\n\n

    26.3.<\/strong> Where the situation allows, the Customer shall first be given the opportunity to remedy the breach within a reasonable period.<\/p>\n\n\n\n

    26.4.<\/strong> No prior cure period is required in the event of urgent security risks, fraud, clear misuse or other circumstances requiring immediate action.<\/p>\n\n\n\n

    26.5.<\/strong> Suspension does not release the Customer from existing payment obligations.<\/p>\n\n\n\n

    26.6.<\/strong> Recurring Fees shall remain payable during a lawful suspension where the cause of the suspension is attributable to the Customer.<\/p>\n\n\n\n

    26.7.<\/strong> Canyon Clan shall not be liable for loss arising from a lawful suspension.<\/p>\n\n\n\n

    Article 27. Amendments to these Terms and Conditions<\/strong><\/h2>\n\n\n\n

    27.1.<\/strong> Canyon Clan may amend these terms and conditions where necessary or useful as a result of changes to:<\/p>\n\n\n\n

    a. the Platform;
    b. legislation or case law;
    c. commercial terms;
    d. technical operation;
    e. payment and invoicing processes;
    f. privacy obligations;
    g. security;
    h. third-party services.<\/p>\n\n\n\n

    27.2.<\/strong> Amendments shall be communicated through the Platform, email, invoice, website or another suitable communication channel.<\/p>\n\n\n\n

    27.3.<\/strong> Where reasonable, Canyon Clan shall state the effective date of the amended terms and conditions.<\/p>\n\n\n\n

    27.4.<\/strong> Where the Customer continues to use the Platform after the announced effective date, it shall be deemed to have accepted the amended terms and conditions.<\/p>\n\n\n\n

    27.5.<\/strong> Where an amendment is materially detrimental to the Customer, the Customer may terminate the agreement before the effective date of the amendment.<\/p>\n\n\n\n

    27.6.<\/strong> The right under Article 27.5 shall not apply where the amendment:<\/p>\n\n\n\n

    a. is legally required;
    b. is necessary for security or continuity;
    c. is necessary to prevent serious misuse;
    d. concerns only an administrative or non-material change.<\/p>\n\n\n\n

    27.7.<\/strong> Approved and due Initial Module Fees and services already performed shall remain payable, unless the specific amendment directly affects Canyon Clan\u2019s ability to continue providing the relevant service.<\/p>\n\n\n\n

    Article 28. Assignment<\/strong><\/h2>\n\n\n\n

    28.1.<\/strong> The Customer may not assign its rights and obligations under the agreement to a third party without the prior written consent of Canyon Clan.<\/p>\n\n\n\n

    28.2.<\/strong> Canyon Clan may assign its rights and obligations to:<\/p>\n\n\n\n

    a. an affiliated company;
    b. a legal successor;
    c. an acquirer;
    d. a third party in the context of a restructuring;
    e. a party acquiring the activities or Platform.<\/p>\n\n\n\n

    28.3.<\/strong> In the event of an assignment, Canyon Clan shall respect the reasonable interests and applicable data protection rights of the Customer.<\/p>\n\n\n\n

    Article 29. Severability<\/strong><\/h2>\n\n\n\n

    29.1.<\/strong> If any provision of these terms and conditions is wholly or partly invalid, void or unenforceable, the remaining provisions shall remain in full force.<\/p>\n\n\n\n

    29.2.<\/strong> The parties shall replace the invalid, void or unenforceable provision with a valid provision that corresponds as closely as possible to:<\/p>\n\n\n\n

    a. the original intention;
    b. the economic objective;
    c. the contractual balance.<\/p>\n\n\n\n

    29.3.<\/strong> A failure or delay in exercising a right shall not constitute a waiver of that right.<\/p>\n\n\n\n

    Article 30. Governing Law and Competent Courts<\/strong><\/h2>\n\n\n\n

    30.1.<\/strong> These terms and conditions and every agreement between Canyon Clan and the Customer shall be governed by Belgian law.<\/p>\n\n\n\n

    30.2.<\/strong> Disputes shall fall within the exclusive jurisdiction of the competent courts of the judicial district in which Canyon Clan\u2019s registered office is located, unless mandatory law provides otherwise.<\/p>\n\n\n\n

    30.3.<\/strong> The parties shall first attempt in good faith to resolve any dispute amicably before commencing legal proceedings.<\/p>\n\n\n\n

    30.4.<\/strong> Article 30.3 does not prevent a party from seeking urgent, protective or interim measures.<\/p>\n\n\n\n

    Appendix 1. Data Processing Clause<\/strong><\/h2>\n\n\n\n

    B1.1. Scope and Roles<\/strong><\/h3>\n\n\n\n

    This Appendix applies to the extent Canyon Clan processes personal data on behalf of the Customer within the meaning of the General Data Protection Regulation.<\/p>\n\n\n\n

    The Customer shall in principle act as controller and Canyon Clan as processor.<\/p>\n\n\n\n

    B1.2. Subject Matter of the Processing<\/strong><\/h3>\n\n\n\n

    The subject matter of the processing is the provision of the Platform, Modules and related services, including:<\/p>\n\n\n\n

    a. hosting;
    b. support;
    c. monitoring;
    d. invoicing and payment follow-up;
    e. logging;
    f. security;
    g. maintenance;
    h. back-ups;
    i. integrations;
    j. further development.<\/p>\n\n\n\n

    B1.3. Duration<\/strong><\/h3>\n\n\n\n

    The duration of the processing shall correspond to the duration of the agreement, extended by the necessary retention periods for:<\/p>\n\n\n\n

    a. back-ups;
    b. legal obligations;
    c. security;
    d. evidentiary purposes;
    e. the handling of disputes;
    f. the Transition Period.<\/p>\n\n\n\n

    B1.4. Nature and Purpose of the Processing<\/strong><\/h3>\n\n\n\n

    The processing may include:<\/p>\n\n\n\n

    a. collection;
    b. storage;
    c. consultation;
    d. structuring;
    e. modification;
    f. securing;
    g. transmission;
    h. deletion;
    i. export;
    j. analysis.<\/p>\n\n\n\n

    The processing shall take place solely for the purposes of the agreed services.<\/p>\n\n\n\n

    B1.5. Categories of Personal Data<\/strong><\/h3>\n\n\n\n

    The categories of personal data depend on the Customer\u2019s use and may include:<\/p>\n\n\n\n

    a. identification data;
    b. contact details;
    c. account details;
    d. professional data;
    e. log and usage data;
    f. communication data;
    g. financial or invoicing data;
    h. data entered into the Platform by the Customer.<\/p>\n\n\n\n

    B1.6. Categories of Data Subjects<\/strong><\/h3>\n\n\n\n

    The categories of data subjects may include:<\/p>\n\n\n\n

    a. employees;
    b. customers;
    c. suppliers;
    d. prospects;
    e. end users;
    f. contact persons;
    g. subcontractors;
    h. other persons whose data is processed by the Customer.<\/p>\n\n\n\n

    B1.7. Customer Instructions<\/strong><\/h3>\n\n\n\n

    Canyon Clan shall process personal data solely in accordance with:<\/p>\n\n\n\n

    a. this agreement;
    b. the configuration and use of the Platform by the Customer;
    c. additional documented instructions from the Customer;
    d. legal obligations.<\/p>\n\n\n\n

    Where Canyon Clan is legally required to process personal data otherwise, it shall inform the Customer in advance, unless the law prohibits such notification.<\/p>\n\n\n\n

    Canyon Clan shall inform the Customer where, in its reasonable opinion, an instruction conflicts with applicable data protection legislation.<\/p>\n\n\n\n

    B1.8. Confidentiality<\/strong><\/h3>\n\n\n\n

    Canyon Clan shall ensure that persons authorised to process personal data:<\/p>\n\n\n\n

    a. only receive access where necessary;
    b. are bound by confidentiality;
    c. receive appropriate instructions or training.<\/p>\n\n\n\n

    B1.9. Security Measures<\/strong><\/h3>\n\n\n\n

    Canyon Clan shall implement appropriate technical and organisational measures, taking account of:<\/p>\n\n\n\n

    a. the risks of the processing;
    b. the nature of the personal data;
    c. the state of the art;
    d. implementation costs;
    e. the specific services.<\/p>\n\n\n\n

    These measures may include:<\/p>\n\n\n\n

    a. access management;
    b. authentication;
    c. logging and monitoring;
    d. encryption where appropriate;
    e. back-ups;
    f. security updates;
    g. incident management;
    h. recovery capabilities;
    i. availability and integrity.<\/p>\n\n\n\n

    B1.10. Subprocessors<\/strong><\/h3>\n\n\n\n

    The Customer grants Canyon Clan general written authorisation to engage subprocessors.<\/p>\n\n\n\n

    Canyon Clan shall ensure that subprocessors are contractually bound by appropriate data protection, security and confidentiality obligations.<\/p>\n\n\n\n

    Canyon Clan shall remain responsible to the Customer for the performance of its obligations by the subprocessors it engages, within the limitations of the main agreement.<\/p>\n\n\n\n

    Upon request, Canyon Clan shall provide information on the categories or main subprocessors relevant to the Customer.<\/p>\n\n\n\n

    Where Canyon Clan engages a material new subprocessor that creates a significant additional privacy risk, the Customer may raise a substantiated objection.<\/p>\n\n\n\n

    The parties shall attempt to find a reasonable solution. Where no reasonable solution is possible, Canyon Clan may modify the relevant functionality or the Customer may terminate the directly affected part.<\/p>\n\n\n\n

    B1.11. Assistance to the Customer<\/strong><\/h3>\n\n\n\n

    Taking account of the nature of the processing and the information available, Canyon Clan shall, where reasonably possible, assist the Customer with:<\/p>\n\n\n\n

    a. data subject requests;
    b. security obligations;
    c. investigation and notification of personal data breaches;
    d. data protection impact assessments;
    e. consultations with supervisory authorities.<\/p>\n\n\n\n

    Additional work falling outside the standard services may be charged separately.<\/p>\n\n\n\n

    B1.12. Personal Data Breaches<\/strong><\/h3>\n\n\n\n

    Where Canyon Clan becomes aware of a security incident involving the Customer\u2019s personal data, it shall inform the Customer without undue delay.<\/p>\n\n\n\n

    To the extent available and relevant, the notification shall include:<\/p>\n\n\n\n

    a. the nature of the incident;
    b. the likely consequences;
    c. the measures taken or proposed;
    d. available information that may assist the Customer in complying with its legal obligations.<\/p>\n\n\n\n

    The Customer remains responsible for determining whether notification to data subjects or a supervisory authority is required.<\/p>\n\n\n\n

    B1.13. International Transfers<\/strong><\/h3>\n\n\n\n

    Where personal data is processed outside the European Economic Area, Canyon Clan shall ensure that an applicable transfer mechanism or other appropriate safeguard is used, where legally required.<\/p>\n\n\n\n

    B1.14. Information and Audits<\/strong><\/h3>\n\n\n\n

    Canyon Clan shall make available reasonable information necessary to demonstrate compliance with its obligations as processor.<\/p>\n\n\n\n

    An audit or inspection:<\/p>\n\n\n\n

    a. must be requested in writing in advance;
    b. must be reasonable and proportionate;
    c. may not unnecessarily disrupt security or services;
    d. must respect the confidentiality and rights of other customers;
    e. shall preferably first be conducted on the basis of existing documentation and reports.<\/p>\n\n\n\n

    On-site audits shall only take place where existing information is reasonably insufficient and shall be agreed in advance in practical terms.<\/p>\n\n\n\n

    Audit costs may be charged to the Customer where the audit does not reveal a material breach by Canyon Clan or falls outside the standard services.<\/p>\n\n\n\n

    B1.15. Deletion and Return<\/strong><\/h3>\n\n\n\n

    Following the end of the agreement, Canyon Clan shall delete or return personal data in accordance with the provisions concerning export, back-ups, the Transition Period and the end of access.<\/p>\n\n\n\n

    Canyon Clan may retain personal data for longer where necessary due to:<\/p>\n\n\n\n

    a. a legal obligation;
    b. the normal back-up cycle;
    c. security and fraud prevention;
    d. evidentiary purposes or a dispute;
    e. other legitimate interests.<\/p>\n\n\n\n

    During any further retention period, the personal data shall not be used for incompatible purposes.<\/p>\n\n\n\n

    B1.16. Customer Obligations<\/strong><\/h3>\n\n\n\n

    The Customer warrants that:<\/p>\n\n\n\n

    a. the processing is lawful;
    b. appropriate information is provided to data subjects;
    c. valid legal bases or consents are in place;
    d. its instructions to Canyon Clan are lawful;
    e. no personal data is processed in the Platform that is clearly unsuitable or unnecessary for the agreed purpose;
    f. Canyon Clan receives in a timely manner all information it reasonably requires to comply with its obligations.<\/p>\n\n\n\n

    <\/p>","protected":false},"excerpt":{"rendered":"

    Deze algemene voorwaarden zijn een uitbreiding op onze standaard Algemene Voorwaarden met betrekking tot onze Workhub tool. Dit betreft de Engelstalige versie. Op verzoek kan een Nederlandstalige versie bezorgd worden. GENERAL TERMS AND CONDITIONS FOR WORKHUB Canyon Clan VOF Version: 26 July 2026 Table of Contents Article 1. Definitions 1.1. \u201cCanyon Clan\u201d or \u201cSupplier\u201d: Canyon […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2741","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/pages\/2741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/comments?post=2741"}],"version-history":[{"count":9,"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/pages\/2741\/revisions"}],"predecessor-version":[{"id":2783,"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/pages\/2741\/revisions\/2783"}],"wp:attachment":[{"href":"https:\/\/www.canyonclan.com\/en\/wp-json\/wp\/v2\/media?parent=2741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}