Updated · May 11, 2026

Terms of service

These terms govern the contractual relationship between DevFlowCollective ApS ("the collective") and the entity engaging the collective's services ("the client"). The collective provides business-to-business services; consumers in the meaning of the Danish Consumer Contracts Act (Forbrugeraftaleloven) are outside the target audience and should reach out before contracting.

1. Contract formation

A contract is formed when the client signs a written proposal, or when the client completes the checkout flow on this website and receives a written confirmation from the collective. Scope, schedule, and price are recorded in the signed proposal — or, failing that, on the Stripe receipt and the matching invoice.

2. Scope and deliverables

Each engagement covers only the scope described in the proposal or on the pricing page. Anything outside scope is handled through a written change-order, with agreed effort and price, before the work begins. A sprint is our unit of work; sprint deliverables are demonstrated on the Friday of the second week.

3. Pricing and VAT

All prices are stated in euros and exclude Value Added Tax. Customers resident in Denmark are invoiced with Danish VAT at 25%. EU business-to-business customers with a valid intra-EU VAT number are invoiced under the reverse-charge mechanism in accordance with Article 196 of Directive 2006/112/EC. Customers outside the EU are not charged Danish VAT.

4. Payment and late interest

Sprint packs are charged when the engagement is confirmed. Continuity plans are billed monthly in advance. Hour packs are paid up front and the hours expire twelve months after purchase if unused.

For invoices issued after checkout, payment terms are fourteen calendar days. Overdue amounts accrue late-payment interest under the Danish Interest Act (Renteloven), at Nationalbanken's reference rate plus eight percentage points, together with a fixed compensation of DKK 310 per Article 9a of the Interest Act and EU Directive 2011/7/EU on combatting late payment in commercial transactions.

5. Continuity plans and cancellation

Continuity plans run as a monthly subscription with no minimum term. Either party may cancel with thirty days' written notice. The current month is billed in full; unused hours during the notice period can be used for handover work.

6. Schedule and dependencies

Published schedules are reasonable estimates. Where a delivery depends on information, accesses, or materials from the client, any days lost on the client's side roll into the collective's schedule without penalty.

7. Intellectual property

Code and deliverables created specifically for the client are assigned in full to the client once the engagement has been paid in full. The collective reserves the right to reuse — in future engagements — its internal tools, generic libraries, snippets, and know-how acquired during the work, provided they do not contain client-confidential information.

8. Confidentiality

Information identified by either party as confidential is treated as such for three years following the end of the engagement. The obligation lifts for information that passes into the public domain without the collective's fault, or that the collective demonstrably knew prior to the engagement.

9. Warranty and liability cap

The collective warrants that its work will conform to the proposal and be free of material defects for ninety days following delivery. After that window, defect correction is billed at the prevailing engineering-hour rate. The collective's aggregate liability is capped at the amount actually paid by the client in the twelve months preceding the event giving rise to the claim, save in case of proven wilful misconduct or gross negligence.

10. Use of AI

The code and copy we deliver are written by humans on our payroll. We may use AI assistants as supporting tools — for autocomplete, mechanical refactoring, or documentation search — but we do not deliver AI-generated artefacts without human review, and we do not use client data to train any third-party model.

11. Force majeure

Neither party is liable for breaches caused by reasons outside its reasonable control (extended provider outages, generalised labour conflicts, administrative decisions). Dates are rescheduled by mutual good faith.

12. Sub-processors and on-site presence

The collective does not subcontract engineering work. All hands on the keys are on the collective's payroll. Where on-site presence is required, the engineer concerned will travel to the client at the client's reasonable expense, by prior agreement in writing.

13. Governing law and jurisdiction

These terms are governed by Danish law. For any dispute, the parties submit — expressly waiving any other jurisdiction — to the courts of first instance in Aalborg (Retten i Aalborg).