Terms and conditions

1. Scope and parties

caadoo is a brand of dionics media UG (haftungsbeschränkt), Birkhuhnweg 8, 31303 Burgdorf, Deutschland, registered at Amtsgericht Hildesheim, HRB 205032, "we" below. The customer's contracting party is that company.

These terms apply to every membership contract. The customer's own terms and conditions do not apply, even if we do not expressly object to them. Individual agreements in text form take precedence over these terms.

2. Businesses only

We contract only with businesses within the meaning of section 14 of the German Civil Code, meaning persons and companies acting in the course of their trade, business or profession when they conclude the contract. We do not contract with consumers. By ordering, the customer confirms that it acts as a business.

3. How the contract is formed

The plans shown on this website are not a binding offer. The customer orders by completing the payment step in Stripe's checkout. We accept the order by confirming it by email or by starting work, whichever comes first. A contract is also formed when both sides confirm it in text form, for example by email.

We serve at most 6 members at the same time, because one person does the work. When that number is reached we do not accept an order. We put the customer on a waiting list instead and refund any payment already made in full. A place on the waiting list gives no right to a contract.

4. Services and plans

We build solutions in artificial intelligence, automation and digitalization for the customer, such as AI assistants, automated workflows and connections between software systems. On both plans the customer can add as many requests to the queue as it likes. The scope depends on the plan:

• Operator: EUR 3,990 net per month. One active request at a time.
• Officer: EUR 6,990 net per month. Two active requests at a time, a weekly call, an AI roadmap each quarter and a 60-minute team training each month.

5. What is not included

Not included are round-the-clock on-call support, lengthy ERP migrations and legal advice. The customer decides whether a solution is lawful, in particular under data protection law. Approval comes from its data protection officer or another person it appoints.

6. Nature of the contract

The contract is a contract for services under sections 611 et seq. of the German Civil Code. We owe careful, competent work on the customer's requests, not a particular result and not a defined deliverable. Whether an automation holds up in operation also depends on the customer's systems, data and decisions.

7. Requests and the board

The customer adds and orders its requests on a shared board. Whether that is Trello or Notion is agreed at onboarding. A request is a self-contained task. We split larger projects into several requests together with the customer.

We work on as many requests at once as the plan allows active requests, in the order on the board. When an active request is done, the next one moves up. The customer can change the order at any time.

There is no formal acceptance, because we do not owe a deliverable. We report on the board when a request is implemented. The customer checks the result and reports errors or change requests on the board. We fix errors in our own work first. Changes that go beyond the original request join the queue as a new request. A request is done when the customer closes it on the board or uses the result in operation.

8. The customer's cooperation

The customer cooperates as described below. While a contribution is missing, the request concerned is on hold, and the delay is not our responsibility.

• It sets aside about ten minutes a week to describe requests, answer questions and check results.
• It gives us timely access to the systems and accounts we are to work in, with the permissions needed.
• It names a contact person who can make decisions or obtain them quickly.
• It backs up its data to the current state of the art before we work in systems it uses in production.
• It checks results, especially those produced by AI systems, before using them in operation. AI systems can produce wrong results.

9. Timing and updates

On every active request we post an update on the board at least every 48 hours. This is a service level target, not a promised completion date. How long a request takes depends on its scope, on third-party systems and on the customer's cooperation. A binding date for a single request exists only if we promise it in text form.

10. Third-party tools and costs

We build in the customer's accounts, not in ours. The customer contracts with providers of software, AI models and APIs itself and pays licences, usage fees and API costs directly to the provider. These costs are not included in the membership price. We tell the customer in advance which services a solution uses and where costs can arise.

The provider's own terms apply to these services. The providers are not our vicarious agents. We are not responsible for their availability, their prices or changes to their services.

11. Rights of use

Once the customer has paid in full for the period in which a work result was created, it receives the exclusive, transferable right to use that result in all forms of use, unlimited in time, territory and content. This includes the right to modify the result and to grant rights in it to third parties. Until full payment the customer may use the results on a revocable basis.

Tools, templates, code components and know-how that we developed independently of the engagement or use generally remain ours, and we may keep using them. Where they are part of a work result, the customer receives a simple, non-exclusive and perpetual right to use them, to the extent it needs this to use the result. This right passes with the result if the customer transfers it.

Open-source components are subject to their own licences.

12. Pausing

The customer can pause the membership at any time by email to websites@dionics.ai. During a pause we do no work and nothing is billed. The requests stay on the board.

For the credit we count a billing cycle as 31 days. We credit the unused days of the current cycle. If the customer pauses after 21 days, for example, 10 days remain as credit. When the membership resumes, those days run first, and billing restarts after them. Credited days are not paid out, including on cancellation.

13. Term and cancellation

The membership runs for an indefinite period and renews with each billing cycle. Either side can cancel at any time with effect from the end of the current cycle, in text form, for example by email to websites@dionics.ai, or in Stripe's customer portal. The right to terminate for good cause is unaffected.

When the contract ends, we hand over the status of all open requests on the board. The customer revokes our access to its systems, and we delete any credentials we received from it.

14. Refund in the first 7 days

If the collaboration is not a fit, the customer can ask for a refund in text form within 7 days of the contract being formed. We then refund 75% of the first payment, and the contract ends when the request reaches us. The remaining 25% is full payment for the work done up to that point. This refund is available once per customer.

After the 7 days we refund nothing, including no pro rata refund on cancellation. The pause credit under section 12 and the customer's statutory rights are unaffected.

15. Prices and payment

All prices are net, plus statutory VAT. The price shown in the checkout when the contract is formed applies.

The membership is billed monthly in advance. At the start of each billing cycle Stripe charges the payment method on file and sends the invoice by email. The customer manages invoices and payment methods in Stripe's customer portal, linked from the footer of this website.

If a payment fails, we may put work on hold after a reminder until the payment arrives.

We announce price changes in text form at least one billing cycle in advance. The customer can then cancel with effect from the date the change takes effect.

16. Data protection and processing on the customer's behalf

Where we process personal data on the customer's behalf in the course of the work, the parties conclude a data processing agreement under Article 28 GDPR before that processing starts. The customer remains the controller within the meaning of the GDPR.

How we process personal data on this website and to perform the contract is set out in the privacy notice at https://www.caadoo.ai/en/privacy.

17. Confidentiality

Each side keeps confidential any information about the other side's business that is marked confidential or is recognisably confidential, in particular credentials, trade secrets and customer data. Each uses such information only for this contract. The obligation survives the end of the contract.

It does not apply to information that is public, was already known to the other side, was developed by it independently or must be disclosed by law or by order of an authority.

We name the customer as a reference only with its consent.

18. Liability

We are liable without limit for intent and gross negligence, for injury to life, body or health, under the Product Liability Act, and to the extent of any guarantee we have given or defects we have fraudulently concealed.

For slight negligence we are liable only for breach of essential contractual duties, meaning those whose performance makes proper performance of the contract possible at all and on which the customer may regularly rely, and then only for foreseeable damage typical for this kind of contract. For loss of data caused by slight negligence we are liable only for the cost of restoring it that would have arisen had the data been backed up as section 8 requires. Otherwise our liability is excluded.

These rules also apply to the personal liability of our officers, staff and vicarious agents.

19. Use of this website

The content of this website is general information, not advice for a specific case. We may change it at any time. We do not promise that the site is available without interruption or free of errors.

The text, code, design and images on this site belong to dionics media UG (haftungsbeschränkt) unless marked otherwise. Quoting with a link is allowed. A page or a substantial part of one may be republished only after asking us first.

Do not send credentials or anything under a confidentiality obligation through the contact form. After the contract is formed we exchange access over a secure channel.

The operators of linked third-party sites are responsible for their content. Section 18 applies accordingly to liability for use of this website.

20. Final provisions

German law applies, excluding the UN Convention on Contracts for the International Sale of Goods.

If the customer is a merchant within the meaning of the German Commercial Code, a legal entity under public law or a special fund under public law, the exclusive place of jurisdiction for all disputes under this contract is our seat in Burgdorf.

If any provision of these terms is invalid, the rest remain in force.

These terms exist in German and English. Only the German version is binding. The English version is a reading aid.