Terms and conditions for Flows Systems ApS

Senest opdateret: 4. September 2026
These terms and conditions (“Terms”) apply to all offers, orders, subscriptions, deliveries and other services from Flows Systems ApS, CVR no. 44369842 (“Flows”), to business customers (“Customer”). Flows and the Customer are each referred to as a “Party” and collectively as the “Parties”.
The terms and conditions have been drawn up with inspiration from general Danish standards for IT deliveries and IT operations, including relevant principles from the IT industry's standard contracts. However, the terms and conditions are Flows' own and independent terms and conditions and do not constitute the IT industry's standard terms and conditions. The IT industry's standard terms and conditions, contracts, guidelines or other material are not part of the agreement between Flows and the Customer, unless this has been expressly agreed in writing.
The terms and conditions apply unless otherwise expressly agreed in writing in an order, offer acceptance, project description or separate agreement signed by both Parties.
Important: The terms and conditions are only aimed at business customers and do not apply to consumers.

1. Flows Systems ApS

Flow Systems ApS
CVR No.: 44369842
Vesterbrogade 74
1620 Copenhagen V
Denmark
Email: support@flows.systems
Flows provides integration, automation, software development, consulting, support and managed services, including via Flows Forge iPaaS, Make.com and relevant third-party platforms.
Flows Systems ApS is a member of IT-Branchen, the industry association for Danish tech companies.

2. Basis of agreement and precedence

2.1 The Terms and Conditions, together with the Customer's accepted order, quotation or project description, constitute the basis of the agreement between the Parties.
2.2 The customer's own terms and conditions of purchase, standard terms and conditions, portal terms and conditions or similar do not apply unless Flows has expressly accepted them in writing.
2.3 In the event of a conflict, the documents have the following priority:
A separate, written, signed agreement between the Parties.
A concretely accepted order, offer acceptance or project description.
A possible data processing agreement, but only for the processing of personal data.
These Terms.
2.4 Oral agreements, expectations, specifications or statements are only binding on Flows if they are confirmed in writing by Flows.

3. Services and delivery model

3.1 Flows delivers services as described in more detail in the specific order, offer acceptance, project description or subscription description.
3.2 Services may include, among other things:
Flows Forge iPaaS, integration platform and associated standard functionality.
Integrations, data exchange, automations, workflows, scenarios, mappings, API setup and monitoring.
Consulting, analysis, solution design, implementation, troubleshooting and support.
Development of scripts, software, connectors, API clients, reports, dashboards, documentation and customer customizations.
Setup, administration or provision of third-party services, including, for example, Make.com, OpenAI, Microsoft, Shopify, Uniconta, ERP, POS, WMS, payment and logistics systems.
3.3 Flows does not provide financial systems, payment processing, legal advice, accounting advice or other regulated advice, unless this has been expressly agreed in writing.
3.4 Flows may use employees, freelancers, subcontractors and third-party services for delivery.
3.5 Unless otherwise agreed in writing, all services are provided as an ongoing service or on a “best efforts” basis. Flows does not guarantee a specific business result, a specific savings, a specific revenue, full automation or error-free and uninterrupted operation.
3.6 Documentation, including technical documentation, solution architecture, data models, API documentation, mapping specifications, operations manual, runbooks, training material, handover material and user guides, is only included in the delivery if explicitly stated in the specific order or project description. Documentation that is not explicitly included is only delivered by separate agreement and for a fee.

4. Order, scope and changes

4.1 An order is binding when Flows has confirmed it in writing, commenced work upon the Customer's acceptance or made the subscription service available to the Customer.
4.2 The scope of delivery is only that which is specifically described in the accepted order or project description. Anything not expressly stated as included is considered not included.
4.3 The Customer is responsible for providing correct, complete and timely information, test data, access information, API keys, system access, decisions, approvals and other material necessary for the delivery.
4.4 Changes in scope, requirements, data basis, third-party systems, APIs, security requirements, legislation, schedule or Customer's circumstances may result in changed price, delivery schedule and resource consumption. Flows may invoice such changes based on time spent at the applicable hourly rate or by separate agreement.
4.5 Flows is not obliged to commence or complete modification work until the modification has been agreed in writing or the Customer has accepted that the work will be carried out after the time has elapsed.

5. Prices, invoicing and payment

5.1 All prices are stated excluding VAT, taxes, fees, third-party licenses, consumption, transaction costs and expenses, unless otherwise expressly stated.
5.2 Subscriptions and ongoing services are invoiced in advance per subscription period. Setup, development, consulting, support beyond the included level and other project deliveries may be invoiced in advance, on an ongoing basis, at milestones or by time spent, at Flows' option or as specified in the specific order.
5.3 The payment deadline is 8 days from the invoice date, unless otherwise stated in the invoice or agreed in writing.
5.4 Payment can be made via invoice, Fenerum, Stripe or other payment solution designated by Flow. When paying by card, the Customer accepts that Flow or Flow's payment provider stores the payment information necessary for recurring payments, in accordance with the payment provider's terms.
5.5 In the event of late payment, Flows may charge interest, reminder fees, compensation amounts and collection costs in accordance with applicable law. Reminder fees and other collection costs may be charged per overdue invoice or reminder, where this is legal.
5.6 Flows may adjust prices for subscriptions and ongoing services with at least 30 days' written notice. Price adjustments may occur one or more times a year and may be due to, among other things, changed labor costs, product development, capacity, inflation, changed third-party prices, changed exchange rates, new taxes, changed security requirements or changed scope of the Customer's use.
5.7 Price changes due to third-party suppliers' changed prices, fees, consumption, exchange rates, taxes or terms may be passed on to the Customer by Flows with the notice that Flows itself receives from the third-party supplier, or without notice if the change takes effect with immediate effect for Flows.
5.8 The Customer may not withhold, set off or reduce payments due to counterclaims unless the claim has been acknowledged in writing by Flows or established by final judgment.

6. Customer responsibility and participation

6.1 The customer is responsible for:
To have all necessary rights, consents, permissions, licenses and processing bases for data, systems, APIs, content and instructions that the Customer makes available or instructs Flows to use.
To ensure that the Customer's use of the services is lawful, including in accordance with data protection rules, marketing rules, accounting rules, sector-specific regulation and third-party terms.
To protect your own user accounts, passwords, API keys, tokens and other access information.
To perform your own backups, checks, reconciliations, approvals and tests, especially before automations are put into production.
To review and validate output from integrations, automations, AI features, reports, analytics, and data processing.
To keep Flows informed of relevant changes in the Customer's systems, processes, data, contacts and security requirements.
6.2 The Customer must appoint a decision-making contact person with the necessary knowledge and competence to represent the Customer in relation to the delivery. The Customer is responsible for coordinating its own employees, advisors, system suppliers and other stakeholders.
6.3 The Customer shall respond to Flows' inquiries, provide information and materials and make necessary decisions without undue delay. If the Customer's circumstances delay, increase the cost or otherwise affect the delivery, Flows may move the schedule and invoice the additional time, resources and documented external costs incurred by the circumstances.
6.4 If Flows has allocated employees or subcontractors for an agreed activity and the activity cannot be completed due to the Customer's circumstances, Flows may invoice the allocated time and reasonable, non-avoidable costs. Flows will make reasonable attempts to reallocate the resources.
6.5 The Customer may not use the Services for illegal purposes, security testing without permission, violation of third party rights, distribution of malicious code, unauthorized data collection, or actions that may harm Flows, other customers, or third party platforms.
6.6 Flows may suspend or limit a service immediately if Flows reasonably determines that the Customer's use poses a security risk, is illegal, violates third-party terms, or may harm Flows' systems, reputation, or other customers.

7. Delivery, testing and approval

7.1 Delivery times stated are indicative, unless a specific delivery time is expressly stated as binding in a written agreement. Delay does not entitle the Customer to compensation, penalty, proportionate reduction or termination, unless this results from mandatory legislation.
7.2 When Flows announces that a project delivery, customer adaptation or change is ready for testing or production, the Customer must, without undue delay and no later than 10 calendar days after the announcement, carry out relevant testing and report any significant, reproducible errors in writing.
7.3 An error report must at least contain a clear description of the error, information about the time, affected process and data, and a reasonable description of how the error can be reproduced. Flows may reject error reports that do not provide a sufficient basis for investigation.
7.4 If the Customer does not notify significant, reproducible defects in a timely manner, the delivery shall be deemed approved. Minor defects, cosmetic conditions, requests for changes or conditions that do not significantly hinder the agreed use shall not postpone approval.
7.5 Flows may choose to remedy a justified error by correction, workaround, redelivery, change of configuration or other reasonable solution. Remedy is the Customer's sole remedy for defects, unless otherwise provided by mandatory law.
7.6 If the Customer reports an error and the investigation shows that the error is wholly or partly due to the Customer's circumstances, the Customer's data, the Customer's configuration, the Customer's employees, a third party, Third Party Services or circumstances beyond Flows' control, Flows may invoice the time and reasonable external costs spent on troubleshooting, analysis, support, coordination and possible remediation at Flows' current hourly rate.
7.7 If the cause of an error cannot reasonably be attributed to one Party, Flows may invoice 50% of the time spent on investigation and troubleshooting, unless otherwise agreed in writing.

8. Support, service and maintenance

8.1 Flows provides support in accordance with the support package, subscription description or specific agreement that the Customer has chosen.
8.2 Unless otherwise agreed, support is provided on weekdays during normal Danish working hours. Flows does not guarantee specific response times, resolution times or uptime unless expressly agreed in a separate SLA.
8.3 Support does not include development, changed scope, new integrations, data correction, Customer’s internal training, third party errors, errors in Customer’s systems or changes necessary due to third party supplier changes. Such work will be invoiced at the applicable hourly rate unless included in a written agreement.
8.4 Flows may make updates, security fixes, maintenance, changes and technical adjustments to the Services, including changes to functionality, design, infrastructure, integrations and supported third-party platforms. Flows strives to limit significant operational disruptions, but is not responsible for the consequences of necessary or reasonable changes.

9. Third Party Services, AI and Open Source

9.1 The Services may depend in whole or in part on third-party services, including, for example, Make.com, OpenAI, Microsoft, cloud providers, ERP, POS, WMS, e-commerce, payment, logistics and API providers (“Third-Party Services”).
9.2 Customer’s use of Third Party Services is subject to the terms, prices, usage restrictions, data processing terms and technical limitations of the relevant third party providers. Customer is responsible for accepting and complying with such terms when required.
9.3 Flows is not responsible for any Third Party Services, including downtime, errors, data loss, API changes, changed prices, limitations, account closure, delays, security incidents or cessation of functionality. If a Third Party Service is changed or discontinued, Flows may change, limit or discontinue the affected portion of the delivery.
9.4 AI-based features may generate incomplete, inaccurate, misleading or out-of-date results. Customer may not rely on AI output as the sole basis for making significant decisions without appropriate human professional review. Flows is not responsible for Customer’s use of AI output.
9.5 Solutions may contain open source components. Such components are provided under the license terms applicable to the individual component. Flows cannot transfer rights that Flows does not itself possess.
9.6 An integration, automation or other technical delivery is based on the system versions, APIs, documentation, access options, data formats and third-party terms available at the time of Flows' commencement of the work, unless otherwise expressly agreed in writing.
9.7 Changes at the Customer or third parties, including changed APIs, versions, access rights, data models, rate limits, security requirements, license terms, endpoints, authentication methods or phasing out functionality, do not constitute a defect in Flows' delivery. Analysis, adaptation, debugging, reimplementation and testing resulting therefrom are invoiced at Flows' current hourly rate, unless explicitly included in a subscription or a separate SLA.
9.8 Flows may use, modify, replace or discontinue using Third Party Services, subcontractors, infrastructure, hosting environments, technologies and technical components when this is reasonably necessary or appropriate for reasons of security, operation, price, performance, supportability, legislation, supplier changes or technological development.
9.9 Flows will endeavour to provide the Customer with reasonable prior notice of any material changes that may reasonably be expected to adversely affect the Customer's use of the Service. However, Flows is entitled to implement the change without prior notice if this is necessary for security, operational, regulatory or third party reasons.
9.10 To the extent that a Third Party Service is provided to Flows on an “as is” basis, or with limited warranties or limitations of liability, the corresponding portion of Flows’ service is provided to the Customer on the same basis and with the same limitations, to the extent permitted by law.

10. Intellectual property rights and rights of use

10.1 Flows' background IP and general rights. Flows owns and retains all intellectual property rights, including copyrights, rights to source code, object code, software, scripts, connectors, API clients, libraries, frameworks, workflows, scenarios, mappings, data models, templates, prompts, instructions, configurations, dashboards, designs, documentation, methods, processes, tools, security measures, know-how, ideas, concepts, experiences and improvements, such as:
Was developed, owned, licensed or used by Flows prior to the collaboration with the Customer.
Developed independently of the Customer or without the use of the Customer's confidential information.
Are generic, reusable or suitable for use by multiple customers.
Is included in or used to deliver a customer-specific delivery, including when such material is adapted to the Customer's needs.
10.2 Customer customizations and project development. All rights to customer customizations, development, integrations, automations, mappings, workflows, scripts, configurations, documentation and other deliveries that Flows develops or configures for the Customer belong to Flows, unless a specific and separate written agreement expressly states that more specifically defined economic rights are transferred to the Customer.
10.3 Payment for development, setup, consulting or another delivery does not in itself imply transfer of copyright, ownership of source code or other intellectual property rights to the Customer.
10.4 Customer's right of use. Once the Customer has paid all amounts due, the Customer obtains a limited, non-exclusive, non-transferable, non-sublicensable and revocable right to use the delivered solution, but only in the Customer's own internal business and only for the purpose agreed with Flows.
10.5 The Customer's right of use lasts as long as the relevant subscription or service agreement is in force and the Customer meets its payment and other obligations. For one-off deliveries without an ongoing subscription, the right of use applies indefinitely, but only in accordance with this clause 10 and subject to full payment.
10.6 The customer must not, directly or indirectly:
Copy, distribute, sell, rent, lend, transfer, sublicense or otherwise make Flows' material or the solution available to third parties.
Modify, decompile, reverse engineer, attempt to derive source code or create derivative works based on Flows' software, platform, configurations or materials, unless such restriction is invalid under mandatory law.
Remove or alter any copyright, ownership, trademark or other rights notices.
Allow a third party to copy, take over, imitate, maintain or further develop Flows' material, other than the Customer's own data and material, without Flows' prior written consent.
Use Flows' material to develop or support a competing solution, service or platform.
10.7 Customer data and material. Customer retains all rights to Customer's own data, trademarks, logos, documents, product data, business rules, instructions and other material that Customer lawfully makes available. Customer grants Flows a non-exclusive, royalty-free right to use such material to the extent necessary to provide, operate, maintain, support, secure and improve the Services.
10.8 General know-how. Flows may freely use general ideas, experiences, methods, techniques, concepts and know-how developed or obtained during the collaboration, provided that Flows does not thereby disclose or use the Customer's confidential information in violation of these Terms.
10.9 Full transfer of rights. If Customer wishes to transfer specific source code or other economic rights, a separate written buy-out agreement is required. Such agreement must precisely identify the transferred material, the price, the scope of the transfer, and any restrictions. Flows' background IP, generic components, platform, tools, methods, third-party software, and open source components are always excluded, unless otherwise expressly agreed in writing.
10.10 A transfer of rights or extended right of use only comes into effect when Flows has received full payment for all amounts relating to the delivery and transfer of rights in question.

11. Confidentiality

11.1 The Parties shall treat the other Party's confidential information confidentially and may not disclose it to third parties or use it for purposes other than fulfillment of the agreement.
11.2 Confidential information includes, among other things, business relationships, prices, customer data, access information, technical information, source code, architecture, documentation, product plans, security information and know-how.
11.3 The confidentiality obligation does not apply to information that the receiving Party can document:
Were publicly available without breach of agreement.
Was lawfully known to the receiving Party prior to receipt.
Has been received legally from a third party without an obligation of confidentiality.
Must be disclosed in accordance with law, regulatory requirements or court order, provided that the other Party is notified in advance, if possible.
11.4 The confidentiality obligation applies during the collaboration and for 5 years after the termination of the agreement. For trade secrets, the obligation applies as long as the information legally constitutes trade secrets.

12. Personal data and data processing

12.1 To the extent that Flows processes personal data on behalf of the Customer, the Customer is the data controller and Flows is the data processor, unless otherwise provided for by applicable data protection law.
12.2 A separate data processing agreement or Flows' data processing agreement in force at any time shall apply to such processing. The data processing agreement shall prevail in the event of a conflict, but only for matters concerning the processing of personal data.
12.3 The Customer is responsible for ensuring that the processing of personal data, instructions to Flows and the Customer's use of the services is carried out with a valid processing basis and in accordance with applicable data protection law.
12.4 Flows may use sub-processors as specified in Flows' current list of sub-processors. Flows will notify significant changes in the use of sub-processors in accordance with the applicable data processing agreement.
12.5 The Customer may not use the Services for processing special categories of personal data, information about criminal offences, CPR numbers or other sensitive or highly regulated information, unless this has been expressly agreed in writing and necessary technical, organisational and contractual measures have been established.

13. Limitation of liability

13.1 Total liability ceiling. Flows' total liability to the Customer, regardless of the basis of liability and including contract, tort, product liability, advice, data processing, breach of contract or otherwise, may not in any context exceed an amount corresponding to the subscription payments excluding VAT that the Customer has actually paid to Flows for the affected service in the 3 months immediately prior to the event giving rise to the claim.
13.2 If the claim only concerns a one-off delivery or project delivery without an associated subscription, Flows' total liability cannot exceed the amount excluding VAT that the Customer has actually paid to Flows for the specific delivery affected in the 3 months immediately prior to the incident. If the Customer has not paid subscription payments or payment for the specific delivery during this period, Flows' total liability is limited to DKK 0, to the extent this is legal.
13.3 Flows is under no circumstances liable for indirect losses, consequential damages or operating losses, including loss of revenue, profit, profit, goodwill, expected savings, data, databases, production, customers, business opportunities, third-party claims, losses resulting from interrupted operations or costs of restoration, manual processing or acquisition of replacement systems.
13.4 Flows is not responsible for any error, delay, data loss, loss or damage caused in whole or in part by:
Customer's circumstances, Customer's data, Customer's employees, Customer's subcontractors or Customer's lack of cooperation.
Errors, limitations, changes or downtime of Third Party Services.
Errors, incompleteness or delays in data from the Customer's or third party's systems.
Internet connection, telecommunications, power supply, browser, operating system, hardware, network or other infrastructure beyond Flows' reasonable control.
Unauthorized access, cyberattacks, malware, or security incidents that Flows could not reasonably have prevented.
Customer's use or lack of control of automations, integrations, AI output, reports, or data.
Suspension, closure, limitation, deletion or reopening of services in accordance with these Terms, including as a result of Customer's default in payment.
Circumstances covered by force majeure.
13.5 The Customer must limit its loss, including by performing relevant backup, testing, reconciliation, monitoring and manual control of critical processes. Flows' potential liability is reduced to the extent that the Customer has contributed to the loss or failed to take reasonable loss-limiting measures.
13.6 Any claim against Flows must be made in writing without undue delay and no later than 3 months after the Customer became or should have become aware of the circumstances giving rise to the claim. Claims made later shall lapse to the extent permitted by law.
13.7 The limitations in this clause 13 shall apply to the fullest extent permitted by applicable law. Nothing in the Terms shall limit any liability that cannot be lawfully limited or excluded, including liability for intent or gross negligence, to the extent such limitation would be invalid.

14. Indemnity

14.1 The Customer shall indemnify Flows against any claim, loss, liability, fine, cost and expense, including reasonable legal fees, arising out of or relating to:
Customer data, content, instructions or use of the Services.
The customer's lack of rights, consents, licenses or basis for processing.
Customer's violation of law, third-party terms or these Terms.
Claims from third parties as a result of the Customer's circumstances.
14.2 Flows shall notify the Customer of any such claim without undue delay and shall give the Customer a reasonable opportunity to assist in handling it. Flows shall not enter into any settlement that imposes non-financial obligations on the Customer without the Customer's prior written consent.

15. Subscription, binding, renewal, termination and suspension

15.1 Subscription period. The Customer subscribes to the subscriptions, service packages, support packages and other ongoing services that appear in the accepted order, offer acceptance, subscription description or invoice (collectively the “Subscription”). The subscription runs for the agreed subscription period.
15.2 If no specific subscription period has been agreed, the Subscription runs monthly and is automatically renewed for one month at a time.
15.3 Annual subscription and minimum period. If the Subscription is stated as an annual subscription, a 12-month agreement, a minimum period or otherwise with a longer commitment period, the Customer is bound for the entire agreed period. The Subscription will automatically renew for a new period of the same length unless terminated in due time in accordance with clause 15.5.
15.4 Setup, onboarding, implementation, project work, customer customization, development, consulting and other one-time services are invoiced separately, unless otherwise stated in the specific order. Such amounts are not refundable upon termination, suspension or termination.
15.5 Termination. Monthly Subscriptions may be terminated by either Party with 1 month's written notice to the end of the current subscription period. Annual Subscriptions and Subscriptions with a minimum term may be terminated at the end of the current period with at least 30 days' written notice.
15.6 Termination must be made in writing to support@flows.systems or another written channel as designated by Flows. The Customer is responsible for ensuring documentation that the termination has been received by Flows.
15.7 The Customer may not terminate a Subscription with effect before the expiry of an agreed binding or minimum period. If the Customer nevertheless ceases to use the service, closes its account, requests that access be removed or otherwise terminates the cooperation before the expiry of the period, the Customer remains liable for payment for the remaining part of the binding or subscription period.
15.8 No refund. Payments for subscriptions, support, implementation, setup, development, consulting, third-party usage and other services are not refunded, unless otherwise required by mandatory law or expressly agreed in writing.
15.9 Upgrade, downgrade and changed consumption. Customer may request a change to subscription, number of users, environments, integrations, workflows, data usage, automation usage, API calls, support level, or other capacity limits. An upgrade may be effective immediately and billed pro rata for the remainder of the term or according to Flows' current price list.
15.10 A downgrade, reduction or removal of functionality may not take effect until the end of the current subscription or binding period, unless Flows agrees otherwise in writing. Downgrading does not entitle the Customer to a refund, credit or proportional discount for amounts already invoiced or paid.
15.11 Consumption limits and excess consumption. If the Subscription is based on or includes limits for, for example, the number of users, companies, environments, integrations, workflows, scenarios, operations, tasks, API calls, data volumes, storage space, support hours or other capacity targets, the Customer may not exceed the agreed limits.
15.12 Flows may record and monitor the Customer's consumption. In the event of excess consumption, Flows may, at its own discretion, limit consumption, require an upgrade to the relevant subscription, invoice excess consumption according to the applicable price list or invoice a reasonable market price if no applicable price list exists. Flows may also invoice excess consumption retroactively from the time the limit was exceeded.
15.13 Automatic payment. If Customer has registered a credit card, debit card, payment service or other automatic payment method, Customer authorizes Flows and Flows' payment provider to collect overdue subscription payments, overages, fees and other amounts in accordance with the agreement. Customer must keep payment information up to date and ensure that there is sufficient coverage.
15.14 Reminders and closure in case of payment default. If the Customer has not paid a due invoice, Flows may send a written reminder (“Reminder 1”). If the full amount due, including any interest and fees, is not received by Flows no later than 8 calendar days after sending Reminder 1, Flows may, without further notice, suspend, close, disable or limit the Customer’s access to the Subscription, support, integrations, automations, workflows, data connections and other services in whole or in part.
15.15 Flows may, at its sole discretion, close the entire solution or only those parts of the solution associated with the defaulted Subscription. Flows is not obligated to maintain data transfers, jobs, automations, monitoring, support, integrations or third-party connections during a payment delay.
15.16 No liability upon closure. Closure, suspension, deactivation or limitation made in accordance with clause 15.14 or 15.15 shall not be deemed a default by Flows. Flows shall not be liable for any direct or indirect loss, consequential damages, operating loss, loss of revenue, loss of data, failure to synchronize, failure to transfer orders, failure to update inventory, delays, third party claims, costs of manual operations, restoration, re-entry, replacement systems or other costs arising from or in connection with the Customer’s default in payment and the subsequent closure or limitation of the Services.
15.17 Reopening and restoration. Flows is not obligated to reopen, reactivate or reinstate a closed or suspended solution until Customer has paid all amounts due, interest, fees, any collection costs and any reopening and restoration fees.
15.18 Reopening, reactivation, reestablishment of integrations, rerunning data, checking synchronization, error handling, data cleanup, documentation, testing, support and other work following a payment-related closure are not included in the Subscription. Such work will be invoiced at Flows' current hourly rate and any applicable reopening or administration fees.
15.19 Flows does not guarantee that a closed or suspended solution can be reopened, restored or returned to the same state as before the closure. Flows is not responsible for any data, transactions, events, queues, automations or changes to third party systems that are lost, failed, expired or altered during the suspension or closure.
15.20 Other suspension. Flows may fully or partially suspend the Customer's access to the Subscription, support, integrations, automations, data connections and other services with immediate effect or upon written notice if the Customer exceeds an agreed consumption limit, uses the services in violation of the agreement, creates a security risk or violates the terms of third-party suppliers.
15.21 Suspension or closure does not exempt the Customer from payment obligations, including payment for the remaining agreed binding or subscription period, if such a period has been agreed.
15.22 Flows' cancellation. Flows may terminate or suspend the agreement in whole or in part with immediate effect if the Customer is in material breach of the agreement and has not remedied the breach within 10 calendar days of written demand, if the breach can be remedied. Flows may, however, terminate or suspend without a remedy period in the event of illegal use, significant security risk, infringement of Flows' or third party's rights, insolvency or serious breach of third party terms.
15.23 Data upon termination. Upon termination of the Subscription, the Customer's access to subscription-based services will cease. Upon the Customer's written request and provided that the Customer has paid all amounts due, Flows will make the Customer's available data available in a commonly used format for up to 30 days after termination, if technically possible.
15.24 Data export, transition assistance, transfer, onboarding of new supplier, documentation, training, special extractions, re-establishment or other work upon termination are not included in the Subscription and are invoiced at Flows' current hourly rate.
15.25 After the period specified in clause 15.23, Flows may delete or anonymize the Customer's data in accordance with the applicable data processing agreement, legislation and Flows' backup and deletion routines. Flows is not obliged to retain the Customer's data after this period.
15.26 Termination of the Subscription does not entitle the Customer to Flows' platform, source code, generic components, workflows, scripts, frameworks, internal tools, documentation, development environments or other material belonging to Flows. The Customer's rights upon termination are solely as described in clause 10 and this clause 15.

16. force majeure

16.1 Flows is not liable for failure to perform or delay due to circumstances beyond Flows' reasonable control, including natural disasters, fire, strike, lockout, war, terrorism, cyberattack, epidemic, government intervention, supply failure, widespread internet or telecommunications failure, failure of Third Party Services or other force majeure-like circumstances.
16.2 The obligations of the affected Party shall be suspended during the period of force majeure. If the force majeure situation lasts for more than 60 days, either Party may terminate the affected part of the agreement by written notice, without liability beyond payment for services already provided.

17. References and use of logo

17.1 The Customer grants Flows the right to use the Customer's name and logo as a reference on Flows' website, in sales and marketing material and in presentations.
17.2 The Customer may revoke the permission at any time by written notice. The revocation shall take effect within a reasonable time and shall not affect material already printed or published which cannot reasonably be revoked.

18. Changes to Terms

18.1 Flows may change the Terms with at least 30 days' notice by notification by email, via customer portal or on Flows' website.
18.2 Changes that are solely for the benefit of the Customer, are of no material importance or are necessary due to legislation, security, third-party terms or technical conditions, may be implemented at shorter notice when reasonable.
18.3 If a material change significantly disadvantages the Customer, the Customer may terminate the affected ongoing service with effect from the entry into force of the change by giving written notice before it takes effect. Continued use after the entry into force shall be deemed acceptance.

19. Applicable law and disputes

19.1 The agreement is subject to Danish law, however, without the application of rules that lead to the application of the legislation of another country.
19.2 The Parties shall in good faith seek to resolve any dispute, disagreement or claim arising out of or relating to the Agreement by direct negotiation between relevant decision-makers of the Parties.
19.3 If a dispute is not resolved through direct negotiation within 30 calendar days after a Party has requested this in writing, the Parties may, if they agree, seek to resolve the dispute through mediation or consultation.
19.4 If the Parties choose mediation and do not agree on the choice of mediator within 14 calendar days, each Party may request Danish Mediator Advocates to propose a mediator. The mediation will be conducted in accordance with the rules applicable to Danish Mediator Advocates at any time.
19.5 If the Parties choose to use a mediator and cannot agree on the choice of an assessor, each Party may request the IT Industry to propose a relevant expert assessor. The Parties shall generally bear the costs of the mediator or assessor equally, unless the Parties agree otherwise or a court decides otherwise.
19.6 Mediation or inspection and assessment does not limit Flows' right to immediately carry out debt collection, suspend or terminate services in the event of non-payment, request injunctions or other interim relief, or otherwise protect Flows' intellectual property rights, confidential information, security or other rights.
19.7 If the dispute is not resolved through negotiation, mediation or inspection and assessment, the matter will be decided by the Danish courts with Flows' home court as the venue in first instance, unless mandatory legislation provides otherwise.

20. Other provisions

20.1 If any provision is wholly or partially invalid or unenforceable, this shall not affect the validity of the remaining provisions. Instead, the parties shall replace the invalid provision with a valid provision that achieves the same commercial purpose to the greatest extent possible.
20.2 The Customer may not assign the Agreement or any rights or obligations under the Agreement without Flows' prior written consent. Flows may assign the Agreement in whole or in part to an affiliated company, a buyer of Flows' business or as part of an internal restructuring.
20.3 Flows' failure to assert a right does not constitute a waiver of that right.
20.4 These Terms and Conditions have been prepared in Danish. In the event of any translation or interpretation discrepancies, the Danish version shall prevail.
20.5 Last updated: September 4, 2026.

Appendix A – Third-Party Services and Technical Dependencies

Flows may use third-party services, subcontractors and technical dependencies in the delivery, including but not limited to:
Make.com and other integration or automation platforms.
Microsoft Azure, Microsoft 365, email, identity and cloud services.
OpenAI and other AI model, AI platform or API providers.
Shopify, Uniconta and other ERP, POS, WMS, CRM, e-commerce, payment and logistics systems.
Stripe, Fenerum or other payment and invoicing providers.
Hosting, database, security, backup, logging, monitoring and communication services.
The customer's own systems, system suppliers, APIs, networks, data and technical environments.
The services and dependencies mentioned may be subject to change, be subject to separate terms, have capacity limitations, be dependent on internet connection or are provided on an “as is” basis. Flows may change, replace or discontinue such services in accordance with Section 9 of the Terms.
The list is indicative and not exhaustive. Flows may use additional or alternative technologies, service providers and subcontractors from time to time in accordance with the Terms and any data processing agreement.