1. Agreement structure, acceptance, and order of precedence

The agreement between Hubhus and the customer consists of the documents listed below. In the event of conflict, they apply in the following order of precedence, with the highest-ranking first:

the individually agreed Cooperation Agreement (also referred to as the Software License Agreement), order confirmations, and statements of work

the Data Processing Agreement, including its referenced security documentation

these Terms of Use

the Service & Support Policies

the Customer-specific Code and Custom Logic policy

Hubhus' applicable published pricing

The customer's current, signed Cooperation Agreement, Data Processing Agreement, and related security documentation (including any ISAE assurance report, security environment description, and the Hubhus Business Continuity and Exit/Fallback Plan) are available under Account & Organization → Legal & Contracts in the customer's Hubhus account. The general policy documents listed above are published at hubhus.com/policies.

The customer accepts a specific, identified version of the Cooperation Agreement and of these Terms as then in effect by confirming acceptance in writing - including by replying to Hubhus' written proposal with a clear confirmation such as "We accept the Cooperation Agreement" - or by signing where a signature is required. Hubhus retains that confirmation as evidence of acceptance of the referenced version and makes it available to the customer on request.

These Terms apply to the customer and to all authorized users acting under the customer's account. The customer is responsible for ensuring that its authorized users comply with them.

2. Use of Hubhus

Hubhus provides software and related services for managing business processes, including leads, bookings, communication, automation, webpages, integrations, and other functionality made available through the platform.

The customer is responsible for ensuring that Hubhus is suitable for its intended use and for configuring and using the platform appropriately for its business.

Hubhus may add, change, improve, replace, or discontinue functionality as the platform evolves. Section 9 governs the limited case of removing core functionality without a replacement.

Hubhus does not guarantee that individual features, interfaces, workflows, or integrations will remain unchanged indefinitely.

3. Customer responsibility

The customer is responsible for:

information and data entered into Hubhus

configuration of campaigns, forms, automations, communication, and workflows carried out by the customer or its users

testing configurations before putting them into production

ensuring that users have appropriate access

maintaining secure login credentials and appropriate access control

ensuring that its use of Hubhus complies with applicable law, including data protection law and the rules on electronic marketing in section 10 of the Danish Marketing Practices Act (markedsføringsloven) and equivalent legislation in other relevant jurisdictions

obtaining and documenting any consent required before sending e-mail or SMS communication through the platform

reviewing automated actions and communications where appropriate

maintaining appropriate internal procedures for business-critical processes

Hubhus is not responsible for consequences resulting from incorrect configuration, incorrect or incomplete data, customer actions, or use of the platform in a way for which it was not intended.

This section does not apply to configuration, automations, code, or other work performed by Hubhus for the customer as a paid or agreed deliverable. Responsibility for such work is governed by section 15.

4. Subscription and ordinary termination

Unless otherwise agreed in writing, Hubhus subscriptions have no minimum binding period.

A subscription may be terminated for convenience by either party with notice equal to the remainder of the current calendar month plus three full calendar months. For example, if notice is given during September, the subscription will normally continue through October, November, and December.

For customers exercising the right to switch under Chapter VI of Regulation (EU) 2023/2854 (the Data Act), section 6 governs the notice period, transitional period, and data handling for that purpose, and takes precedence over the notice period above to the extent the two are inconsistent. The ordinary termination notice above does not delay termination where section 6 provides that the service agreement ends upon successful completion of a Data Act switching process. Any fixed commitment period or proportionate early-termination payment expressly agreed in writing applies only to the extent permitted by applicable law.

Any individually agreed commitment period, termination period, pricing agreement, or other commercial condition takes precedence over this standard term.

Notice of termination must be given in writing in accordance with section 26 and must clearly identify the customer account concerned. Hubhus confirms receipt in writing within 5 business days and states the effective termination date.

Access to Hubhus remains available during the notice period. Suspension for overdue payment under sections 8 and 24 is subject to the safeguards set out in those sections.

5. Termination for cause

Either party may terminate the agreement for cause where the other party materially breaches it and fails to remedy the breach within 30 days of receiving a written notice that describes the breach and requires it to be remedied.

Either party may terminate the agreement with immediate effect where the other party is declared bankrupt, enters into insolvency proceedings, or ceases to carry on business, to the extent permitted by mandatory insolvency law.

Hubhus may terminate for cause without a cure period where the customer's use falls within section 20 (Acceptable use) and the breach cannot reasonably be remedied, or where immediate termination is required to comply with applicable law.

On termination for cause by the customer, Hubhus refunds any prepaid fees covering the period after the effective termination date, on a pro rata basis. Termination for cause does not affect either party's right to claim damages under section 22.

Termination for cause does not remove the customer's right to export and retrieve its data under section 6.

6. Switching, data export, and deletion

The customer is responsible for exporting any data it wishes to keep before its access ends. The self-service export routes in section 6.3 are available throughout the subscription, including during the ordinary termination notice period under section 4.

Sections 6.1-6.5 implement the customer's right to switch to another provider or to its own infrastructure under Chapter VI (Articles 23-31) of Regulation (EU) 2023/2854 (the Data Act), on the basis that Hubhus is a "data processing service" within the meaning of Article 2(8) of that Regulation.

6.1 Right to switch and initiation notice

The customer may at any time submit, by written notice under section 26, a request to switch to another provider of a similar service, to switch to its own IT infrastructure, or to terminate its use of the service and have its exportable data erased without switching to a new provider or infrastructure (each a "switching request"). Hubhus may require no more than two months' notice before starting the process described in this section, regardless of the ordinary termination notice period in section 4.

The service agreement terminates upon the successful completion of the switching process. The customer pays the ordinary subscription fee while Hubhus continues to provide the service during the applicable notice and transitional periods. That subscription fee is separate from switching charges governed by section 6.5. Any fixed commitment period or proportionate early-termination payment expressly agreed in writing applies only to the extent permitted by applicable law.

6.2 Transitional period

The transitional period begins once the notice period under section 6.1 has elapsed. During the transitional period, Hubhus continues to provide the service on the same terms, acts with due care to maintain business continuity, and continues to ensure the availability, integrity, and confidentiality of the customer's data.

Hubhus provides reasonable assistance to support the customer's exit strategy, including access to the export routes in section 6.3 and to relevant documentation, and answers reasonable questions about the switching process. On request, Hubhus informs the customer of any continuity risk Hubhus is actually aware of that could affect the switching process.

The transitional period is a maximum of 30 calendar days. Where completing the switch within that time is not technically feasible, Hubhus notifies the customer in writing within 14 working days of the switching request, states the reasons, and specifies an extended period not exceeding seven months. The customer may in turn require Hubhus to extend the transitional period once, by a period the customer considers more appropriate for its own purposes.

6.3 Exportable data and formats

Hubhus provides the following self-service export routes:

Hubhus maintains an up-to-date online data-portability register at hubhus.com/policies (direct link: https://support.hubhus.com/a/solutions/articles/80001221762), specifying exportable data and digital assets, data structures, formats, interfaces, applicable standards, known technical limits, and any permitted exclusions.

a documented REST API, described in the Hubhus Help Center and API documentation

an "Excel" export function available within each campaign, covering the records and business data held in that campaign (for example leads, bookings, contacts, communication logs, and form submissions)

Files and images attached at lead level can be exported in bulk on request, billable under section 14. The exported files may not preserve a clear association with the specific lead or record each file belongs to; the customer is responsible for reconciling files against its records where that association is required. The customer should verify the completeness of its export.

Export does not extend to Hubhus' own software, source code, or platform-internal data and assets that are not exportable data, or to data that Hubhus is legally required to withhold or is not entitled to disclose. Any exclusion needed to protect Hubhus' trade secrets does not impede or delay the switching process.

6.4 Erasure after termination or switching

Where the customer has made a switching request under section 6.1, Hubhus makes the customer's exportable data and digital assets available for retrieval for at least 30 calendar days after the end of the transitional period. Hubhus then erases those data and assets without undue delay, provided the process completed successfully and subject to applicable retention requirements.

Where the customer has not made a switching request and the subscription simply ends under section 4, 5, 8, or 24, Hubhus retains the customer's data in a non-accessible ("soft-deleted") state for a further 30 calendar days after the termination date before permanent deletion. During that period Hubhus makes standard data retrieval available on request; separately requested migration work beyond that standard process is governed by sections 6.5 and 14.

In either case, deletion is subject to any retention required by applicable law, by the Data Processing Agreement, or by a separate written agreement, and Hubhus confirms deletion in writing on request. For personal data, the customer chooses between return and deletion in accordance with the Data Processing Agreement and Article 28(3)(g) GDPR, which takes precedence over the default in this section.

6.5 Switching charges

Until 12 January 2027, Hubhus may charge a reduced switching charge for the switching process described in this section, limited to the costs Hubhus directly incurs as a result of that process. From 12 January 2027, Hubhus does not charge any switching charge for the switching process, data export, or erasure under this section.

Ordinary subscription charges continue to apply while Hubhus continues to provide the service during the notice and transitional periods. Hubhus does not charge for the standard switching process, export, retrieval, or erasure where section 6.5 prohibits a switching charge. Separately requested migration work is billable only where it goes beyond the standard switching process, has been clearly described, and has been approved in writing by the customer in advance.

7. Fees and payment

Subscription fees and prices for additional services are governed by the customer's agreement and Hubhus' applicable published pricing.

Additional services may include, among other things:

meetings

consulting

setup and configuration

custom work

customer-specific code

technical work

development

Current standard pricing is published in the Pricing section on hubhus.com.

Unless otherwise agreed, invoices must be paid according to the payment terms stated on the invoice. All prices are exclusive of VAT and other applicable duties unless expressly stated otherwise.

7.1 Activation and billing start

The customer is responsible for activating and taking the platform into use in accordance with the agreed Cooperation Agreement, including providing the access, credentials, and information Hubhus needs to complete onboarding (for example third-party API keys and integration details).

Unless otherwise agreed, billing starts exactly 30 days after the customer accepts the Cooperation Agreement, regardless of whether onboarding or configuration has been completed by that date. If the customer is ready to use the platform earlier, that earlier period is provided free of charge and does not change the billing start date.

A delay in onboarding caused by the customer - including delayed provision of access, data, or clarification needed for setup - does not postpone the billing start date.

7.2 Price changes

Hubhus may adjust subscription fees with written notice under section 26 equal to the ordinary termination notice period in section 4 - the remainder of the current calendar month plus three full calendar months - taking effect at the start of the billing period following that notice period.

If the customer does not wish to accept a price change, the customer can give ordinary termination notice under section 4. Regardless of when that notice is given, the customer may also terminate the affected subscription with effect from immediately before the price change takes effect, by giving written notice before that date; in that case Hubhus refunds any prepaid fees covering the period after termination on a pro rata basis. The annual inflation-based adjustment under the customer's Cooperation Agreement is not treated as a price change for the purposes of this paragraph.

Prices individually agreed in writing for a fixed period are not changed during that period.

8. Late or missing payment

If payment is overdue, Hubhus may charge default interest and reminder and collection fees in accordance with the Danish Interest Act (renteloven).

Hubhus may restrict or suspend access to the customer account where an invoice remains unpaid 7 days after Hubhus has sent a written reminder identifying the overdue amount and stating that suspension may follow.

Suspension may include blocking user login while the account and its data remain stored. Suspension does not remove the customer's right to export and retrieve its data; Hubhus provides a controlled export route on request in accordance with section 6.3.

Continued non-payment may result in termination of the subscription and, subsequently, closure of the account. Hubhus gives at least 30 days' written notice before permanent account closure or deletion of customer data, and states the deadline for data retrieval in that notice.

Any deletion is handled subject to applicable legal obligations, agreed retention requirements, and the Data Processing Agreement.

Suspension due to non-payment does not remove the customer's obligation to pay outstanding invoices or fees applicable during an agreed notice or commitment period.

9. Changes to the platform and to these Terms

Hubhus may add, change, replace, rewrite, or discontinue any feature, interface, workflow, or method of performing a function at any time, without prior notice, including where a feature is replaced by an automated or restructured alternative. Hubhus does not guarantee that any specific feature, interface, or workflow will remain unchanged or available indefinitely.

"Core functionality" means the fundamental categories of functionality the customer's subscribed service depends on (for example lead management, booking, communication, and automation) - not any specific feature, interface, workflow, or method of performing that functionality. Permanent removal of core functionality without a reasonably equivalent replacement is treated as a material change.

A material change is notified to the customer in writing under section 26 with notice equal to the ordinary termination notice period in section 4 - the remainder of the current calendar month plus three full calendar months - before it takes effect. If the customer does not wish to accept it, the customer can give ordinary termination notice under section 4. Regardless of when that notice is given, the customer may also terminate the affected subscription with effect from immediately before the change takes effect, by giving written notice before that date; in that case Hubhus refunds any prepaid fees covering the period after termination on a pro rata basis.

Hubhus may also update these Terms as applicable law, pricing structure, or its services change. Material changes to these Terms - including changes that materially increase the customer's obligations or materially limit Hubhus' responsibilities - follow the same notice and exit right described above. Non-material changes, including editorial corrections and changes required to comply with mandatory law, may take effect without advance notice.

The latest version of these Terms is always available through the Hubhus Help Center. Changes do not override individually agreed contractual terms unless separately agreed in writing.

10. Automated workflows and communication

Hubhus allows customers to automate actions such as e-mails, SMS messages, bookings, lead processing, integrations, and other business processes.

The customer is responsible for reviewing and testing automated workflows configured by the customer before relying on them in production, and for ensuring that automated communication complies with applicable marketing and data protection law.

Automation should not be treated as a substitute for appropriate business controls where an error could have significant operational, financial, or legal consequences.

Where an automation has been built or configured by Hubhus as a paid or agreed deliverable, section 15 applies.

11. Service availability

Hubhus uses commercially reasonable efforts to maintain availability and reliable operation of the platform, and provides the service with the care and skill reasonably expected of a professional supplier.

Temporary interruptions may occur due to:

maintenance

updates and deployments

technical faults

infrastructure issues

third-party services

circumstances outside Hubhus' reasonable control

Where planned maintenance is expected to cause material downtime, Hubhus gives advance notice where reasonably practicable.

Unless specifically agreed in writing, standard Hubhus subscriptions do not include a formal Service Level Agreement (SLA), guaranteed uptime, guaranteed response time, or guaranteed resolution time.

The absence of an SLA does not relieve Hubhus of its obligation to provide the agreed service. Any remedies and liability arising from service interruption or unavailability remain subject to section 22.

Current support expectations are described in the Service & Support Policies.

12. Third-party services, integrations, and subcontractors

This section distinguishes between third parties selected by the customer and third parties engaged by Hubhus.

12.1 Third parties selected by the customer

Where the customer connects Hubhus to a third-party product or service of its own choosing - including e-mail and SMS providers, accounting systems, calendar services, external APIs, and integration platforms - Hubhus does not control that service and does not guarantee its availability, performance, continued compatibility, delivery times, API behaviour, or data accuracy.

Hubhus is not responsible for interruptions, changes, errors, or losses caused by such customer-selected third-party services.

12.2 Subcontractors and suppliers engaged by Hubhus

Where Hubhus engages a third party to deliver part of the service - including hosting and infrastructure providers, platform-level e-mail or SMS gateways, and other suppliers Hubhus has selected - Hubhus remains responsible to the customer for that supplier's performance as if Hubhus had performed it itself, subject to sections 22 and 25.

Where such a supplier acts as a sub-processor of personal data, Hubhus remains fully liable to the customer for the sub-processor's performance of its data protection obligations in accordance with Article 28(4) GDPR. Authorisation, notification of changes, and the customer's right to object are governed by the Data Processing Agreement.

A current list of sub-processors is available under Account & Organization → Legal & Contracts.

13. Customer-specific code and custom logic

Hubhus allows customer-specific logic and non-native functionality to be implemented in areas such as webpages, booking forms, campaign forms, and other configurable parts of the platform. Such functionality is governed by the Customer-specific Code and Custom Logic policy.

Customer-specific code is not native Hubhus functionality and is not covered by standard support.

Where such code has been written or implemented by the customer, by an authorized user, or by a third party engaged by the customer, troubleshooting, modification, technical assessment, or rebuilding is billable under section 14.

Where such code has been written or implemented by Hubhus as a paid or agreed deliverable, section 15 applies, and correction of defects in that deliverable is not billable within the period stated in section 15.

For this purpose, a defect means that the delivered code does not do what was agreed in the customer's written brief. Where the code performs as briefed but the customer's brief did not cover a scenario, case, or requirement now raised by the customer, addressing it is additional work billable under section 14, not a defect correction.

The customer is responsible for providing as complete a brief as possible - including edge cases and scenarios the functionality should handle - and for testing delivered code before relying on it in production.

Ownership of and rights to use customer-commissioned code are governed by section 19.

14. Support and professional services

Standard support generally covers:

questions

guidance

clarification

troubleshooting of native Hubhus functionality

Setup, configuration, meetings, custom work, development, and other work carried out by Hubhus at the customer's request is billable at Hubhus' standard rates, published in the Pricing section on hubhus.com, without requiring the customer's prior written approval of scope or price. Work that is part of the standard switching process under section 6 is not billable as professional services.

For work expected to take 1 hour or less, Hubhus does not proactively provide a time estimate. For work expected to exceed 1 hour, Hubhus informs the customer of the expected time before proceeding. The customer may request a time estimate for any piece of work regardless of size; requesting one is the customer's own responsibility.

Billable time is invoiced per commenced half hour. Hubhus records the source of each billable request - a support ticket ID, or a note that the request was received by e-mail - for reference.

Troubleshooting made necessary by the customer's own actions - for example investigating a booking made manually by the customer that conflicts with an existing calendar entry, or issues arising from manual edits to automated bookings or events - is billable, even though it takes the form of troubleshooting.

Time spent correcting defects in Hubhus' own deliverables under section 15 is not billable.

14.1 Support channel

Support requests must be submitted as a ticket via support.hubhus.com so that Hubhus can prioritise and route them correctly. Requests sent by e-mail are also answered, but without a guaranteed response time. The customer must open a new ticket for each new issue rather than replying to a previously closed or resolved ticket.

Current conditions are described in the Service & Support Policies, including Free vs Paid Support, Fair Usage Policy, Response Times and Service Expectations, and Urgent and Business-Critical Issues.

15. Work delivered by Hubhus - defects and remedies

Where Hubhus delivers configuration, automations, integrations, custom code, or other professional services to the customer, Hubhus warrants that the work is performed with the care and skill reasonably expected of a professional supplier and substantially in accordance with the agreed scope.

If the customer notifies Hubhus in writing of a defect in such a deliverable within 30 days of delivery, Hubhus corrects the defect without additional charge within a reasonable time.

If Hubhus fails to correct the defect within a reasonable time, the customer may claim a proportionate reduction of the fee for the affected work or, where the defect is material, a refund of that fee. This is in addition to any claim for damages, subject to section 22.

This section does not apply where the defect is caused by changes made by the customer or a third party after delivery, by incorrect or incomplete information supplied by the customer, or by a customer-selected third-party service under section 12.1.

The general exclusions in section 22 relating to customer configuration and non-native code do not exclude Hubhus' responsibility for work Hubhus itself has delivered under this section.

16. Customer data and data protection

The customer retains ownership of customer data entered into Hubhus.

Hubhus processes personal data on behalf of the customer as a data processor, in accordance with the Data Processing Agreement. The customer is the data controller and is responsible for ensuring that personal data uploaded to or processed through Hubhus has been collected and is processed lawfully.

Hubhus implements appropriate technical and organisational measures in accordance with Article 32 GDPR, including measures to restore the availability of and access to personal data in a timely manner in the event of a physical or technical incident. Those measures, including backup frequency, retention, and restore testing, are described in the Data Processing Agreement and its security annex.

Personal data is deleted from production without undue delay once retention is no longer required. Residual copies in backups are purged automatically as part of Hubhus' standard backup rotation cycle, currently up to 3 months, and are not restored to production except for disaster recovery.

Personal data is hosted within the EU/EEA. Current hosting infrastructure and sub-processors are listed in the Data Processing Agreement. Any transfer of personal data to a third country is governed by the Data Processing Agreement.

Hubhus' notice on ICT infrastructure jurisdiction and safeguards against unlawful international governmental access to non-personal data, required under Article 28 of Regulation (EU) 2023/2854 (the Data Act), is published at hubhus.com/policies (direct link: https://support.hubhus.com/a/solutions/articles/80001221772).

On termination, the customer chooses whether personal data is returned or deleted, in accordance with Article 28(3)(g) GDPR and the Data Processing Agreement. Section 6 sets out the practical procedure.

17. Data availability, backups, and recovery

This section distinguishes between recovery from incidents in Hubhus' own operation and restoration of data affected by customer actions.

17.1 Recovery from incidents in Hubhus' operation

Hubhus maintains backup and disaster-recovery procedures intended to support the continued operation of the platform and recovery from technical incidents affecting Hubhus' infrastructure. Where data is lost or made unavailable as a result of a fault, error, or incident in Hubhus' own operation, Hubhus uses commercially reasonable efforts to restore it in accordance with those procedures and section 16, at no charge to the customer. Any remedies and liability remain subject to section 22.

Actual backup frequency, retention periods, recovery objectives, and restore testing are described in the Data Processing Agreement and its security annex. Hubhus commits only to the measures actually described there.

17.2 Restoration of data affected by customer actions

Backups are not a customer-controlled archive and are not intended to guarantee that individual records, configurations, or historical data can be restored to an arbitrary point in time on request.

Hubhus does not guarantee recovery of data that has been:

deleted, overwritten, or modified by the customer or an authorized user

removed as part of a data retention setting configured by or agreed with the customer

affected by customer-specific integrations or custom logic within the meaning of section 13

lost due to a customer-selected third-party service under section 12.1

otherwise made unavailable by circumstances outside Hubhus' reasonable control

Where technically and reasonably possible, Hubhus may assist with restoring such data. Such assistance is not guaranteed and may be billable under section 14.

17.3 Customer exports

Customers are responsible for maintaining appropriate exports, copies, or other records of business-critical information where independent retention is required, for example for statutory record-keeping. This responsibility does not reduce Hubhus' obligations under sections 16 and 17.1.

Upon termination, the customer should ensure that any data it wishes to retain has been exported using the routes in section 6.3 before the termination date; the 30-day period in section 6.4 is a safety margin, not a substitute for timely export.

Any backup, retention, restoration, and deletion obligations specifically agreed in the Data Processing Agreement or another written agreement take precedence over this general provision.

18. Confidentiality

Each party shall keep confidential all non-public business information received from the other party in connection with the agreement, including pricing, technical information, business processes, customer lists, and security information, and shall use it only for the purpose of performing the agreement.

Confidentiality does not apply to information that is or becomes publicly available without breach of this section, was lawfully known to the receiving party before disclosure, is independently developed without use of the disclosing party's information, or must be disclosed under mandatory law or a binding order from a public authority. The receiving party shall, where legally permitted, notify the disclosing party before such disclosure.

The obligation applies during the term of the agreement and for 5 years after it ends. For information qualifying as a trade secret, the obligation continues for as long as that information remains a trade secret. For personal data, the Data Processing Agreement applies in addition and takes precedence.

Hubhus may name the customer as a reference only with the customer's prior written consent.

19. Intellectual property

Hubhus and its underlying software, platform, design, functionality, documentation, and intellectual property remain the property of Hubhus or its licensors.

The customer's subscription provides a non-exclusive, non-transferable right to use Hubhus during the subscription period. It does not transfer ownership of the platform or underlying technology.

The customer retains all rights to customer data and to content the customer uploads. The customer grants Hubhus a limited right to process that content solely to provide and operate the service.

19.1 Customer-commissioned development

Unless otherwise agreed in writing, intellectual property rights in work developed by Hubhus for the customer remain with Hubhus. For standalone deliverables capable of use outside the platform, the customer receives a perpetual, non-exclusive, non-transferable, irrevocable right to use the deliverable for its own business purposes. For platform-dependent configuration, automations, integrations, and code, the customer receives a non-exclusive right to use the work through the platform during the subscription period; that right ends when access to the platform ends.

Hubhus may incorporate generally useful functionality, concepts, know-how, and improvements into the standard platform, provided that Hubhus does not disclose the customer's confidential information or customer data in doing so.

Exclusivity to the customer applies only where expressly agreed in writing, and may be subject to a separate fee.

20. Acceptable use

Hubhus must not be used:

for unlawful activities

to intentionally distribute malware or harmful content

to gain unauthorized access to systems or data

in a way that significantly disrupts the platform or other customers

to circumvent technical limitations or security mechanisms

for excessive automated activity that creates unreasonable load on the platform

to send unsolicited electronic marketing in breach of applicable law

Hubhus may restrict or suspend access where necessary to protect the platform, other customers, security, or legal compliance, in accordance with section 24.

21. Beta, experimental, and AI-assisted functionality

From time to time, Hubhus may make beta, experimental, preview, AI-assisted, or otherwise unfinished functionality available. Such functionality may change without notice, contain errors, produce unexpected results, be discontinued, or behave differently from production functionality.

Beta or experimental functionality should not be relied upon for business-critical processes unless expressly agreed otherwise. To the maximum extent permitted by law, such functionality is provided "as is" and section 15 does not apply to it.

21.1 AI-assisted functionality

Where the platform includes AI-assisted functionality, output may be inaccurate, incomplete, or unsuitable for the customer's purpose. The customer is responsible for reviewing AI-generated output before relying on it or communicating it to third parties.

The parties shall each comply with their respective obligations under Regulation (EU) 2024/1689 (the AI Act), including the transparency obligations in Article 50 where applicable. Hubhus documents which AI-assisted features are made available, and which transparency measures Hubhus implements at platform level, in the Hubhus Help Center. Where the customer deploys an AI-assisted feature towards natural persons, the customer is responsible for the disclosure and marking obligations that fall on it as deployer.

Unless expressly agreed in writing, Hubhus does not use customer data to train general-purpose AI models. Any use of customer data in connection with AI-assisted features is governed by the Data Processing Agreement.

22. Limitation of liability

22.1 Excluded loss

Subject to sections 15 and 22.3 and to the maximum extent permitted by applicable law, Hubhus is not liable for indirect, incidental, consequential, or special loss, including loss of profit, revenue, business opportunities, anticipated savings, goodwill, production, or customer relationships.

Separately, and regardless of whether the loss is characterised as direct, indirect, consequential, or otherwise, Hubhus is not liable for any financial loss, damage, cost, expense, or claim arising from (a) interruption, outage, unavailability, degradation, or delay of the service, or (b) loss, corruption, deletion, destruction, or unavailability of data. Sections 11 and 17 set out Hubhus' contractual obligations to restore the service and, where applicable, data; this paragraph does not limit remedies that cannot lawfully be excluded or limited.

Hubhus is furthermore not liable for financial loss arising from:

configuration carried out by the customer or its users

incorrect or incomplete customer data

automations or workflows configured by the customer or its users

customer-specific or non-native code within the meaning of section 13, other than code delivered by Hubhus

third-party services selected by the customer under section 12.1

actions performed by the customer's users

circumstances outside Hubhus' reasonable control under section 25

The exclusions in this section apply to loss involving work delivered by Hubhus and suppliers engaged by Hubhus, subject to the express defect remedies in section 15, Hubhus' data protection obligations, and section 22.3. Hubhus remains responsible for the performance of suppliers it selects in accordance with section 12.2, but that responsibility is subject to the exclusions and cap in this section to the extent permitted by law.

22.2 Liability cap

Subject to section 22.3, Hubhus' total aggregate liability arising out of or in connection with the agreement during any rolling 12-month period shall not exceed an amount equal to one month's subscription fee for the affected Hubhus account, calculated using the subscription fee applicable when the event giving rise to the first claim in that period occurred. If the affected work is professional services supplied without a subscription, the cap is the fees paid for that affected work.

A series of connected effects or repeated occurrences of the same underlying fault is treated as one claim for this purpose. The defect remedies in section 15 remain available, subject to this aggregate cap and section 22.3.

22.3 Liability that is not limited

Nothing in these Terms limits or excludes liability for:

death or personal injury caused by negligence

wilful misconduct or gross negligence

fraud or fraudulent misrepresentation

breach of the confidentiality obligation in section 18 caused wilfully or by gross negligence

amounts payable by the customer for the service

any other liability that cannot lawfully be limited or excluded, including under mandatory data protection law and Regulation (EU) 2023/2854

Claims under these Terms must be notified in writing to the other party without undue delay after the claiming party became or should have become aware of the circumstances giving rise to the claim.

23. No guarantee of business outcome

Hubhus is a software platform and does not guarantee any specific commercial, financial, operational, sales, lead-generation, booking, or other business outcome.

The customer remains responsible for business decisions made using information, data, recommendations, AI-generated content, or workflows available through Hubhus.

24. Suspension of access

Hubhus may temporarily restrict or suspend access where reasonably necessary due to:

security concerns

suspected unauthorized access

illegal use

material misuse of the service

significant risk to the platform or other customers

overdue payment in accordance with section 8

material breach of the applicable agreements

Except where immediate suspension is necessary to prevent harm, Hubhus notifies the customer in writing before suspension, states the reason, and states what the customer must do to have access restored.

Suspension is limited in scope and duration to what is reasonably necessary. Hubhus restores access without undue delay once the underlying cause has been resolved.

Suspension does not remove the customer's right to export and retrieve its data under section 6.3.

25. Force majeure

Neither party is responsible for failure or delay in performing its obligations, other than payment obligations, caused by circumstances outside its reasonable control.

This may include infrastructure failures, internet outages, cyber incidents, telecommunications failures, government actions, natural disasters, labour disputes, war, or failures affecting material third-party suppliers.

The affected party shall notify the other party without undue delay and use reasonable efforts to limit the effects. If the force majeure event continues for more than 30 days, either party may terminate the affected part of the agreement with immediate effect, without liability, and Hubhus refunds any prepaid fees covering the period after termination on a pro rata basis.

26. Notices

Notices under these Terms must be given in writing and are considered received when delivered to:

for Hubhus: support@hubhus.com. E-mail to this address is sufficient on its own; the customer may optionally also send a copy to the registered address stated at the top of these Terms

for the customer: the primary administrative contact and billing contact registered in the customer's Hubhus account

The customer is responsible for keeping its contact details in the account current. Notices of termination, material breach, material changes under section 9, and price changes under section 7.2 must be sent by e-mail to the addresses above and are not validly given through in-product messages, chat, or support tickets alone.

27. Assignment and change of control

Neither party may assign the agreement without the other party's prior written consent, which shall not be unreasonably withheld.

Hubhus may, on written notice, assign the agreement to a group company or in connection with a merger, acquisition, or transfer of all or substantially all of its business, provided the assignee assumes the obligations under the agreement. Where personal data is affected, the Data Processing Agreement applies.

28. Severability, waiver, and survival

If a provision of these Terms is held invalid or unenforceable, the remainder remains in force, and the invalid provision is replaced by a valid provision that reflects the original intention as closely as possible.

A party's failure or delay in enforcing a right does not constitute a waiver of that right.

Sections 6 (switching, export, and deletion), 16 (customer data and data protection), 18 (confidentiality), 19 (intellectual property), 22 (limitation of liability), 26 (notices), 28, and 29 survive termination of the agreement, together with any other provision that by its nature is intended to survive.

29. Governing law and disputes

These Terms are governed by Danish law, excluding its conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods.

The parties shall first attempt to resolve any dispute by negotiation between persons with authority to settle it.

If the dispute is not resolved within 14 days, it shall be brought before the Danish courts, with the Copenhagen City Court (Københavns Byret) as the court of first instance, subject to any individually agreed jurisdiction or arbitration clause.

Related policies and documents

These Terms should be read together with the documents listed in section 1. The customer's current, signed Cooperation Agreement, Data Processing Agreement, and related security documentation are available under Account & Organization → Legal & Contracts. The following general policies are published at hubhus.com/policies:

Service & Support Policies

Customer-specific Code and Custom Logic policy

Pricing - hubhus.com/pricing