Warranty, terms & privacy

1. Requirements, specification and scope changes

The scope of the work or service is based on written requirements approved by both parties, such as a specification, backlog or quotation with an appendix. Requests beyond the approved specification, including added features, integrations or changes after acceptance, are additional work. They are carried out after agreement on the price or hourly rate and estimate, unless otherwise agreed.

In iterative development, scope is usually managed in stages, each ending with approval of the agreed deliverables. The customer provides timely feedback, system access and materials. Delays on the customer’s side may affect the schedule and costs under the contract.

2. Pricing, invoicing and payment

The price may be fixed for a defined scope, hourly, or a combination of both. Invoices are issued according to the contract, for example as deposits, milestones or monthly billing. Typical B2B payment terms are 14 days from issue unless the contract states otherwise.

In the event of a substantial payment delay, the contractor may suspend work or withhold further deliverables until the overdue amount is paid, unless expressly restricted by the contract. Late interest and collection costs are governed by applicable law and the contract.

3. Intellectual property, licences and third-party components

Any transfer of copyright or grant of a licence to the resulting work is governed exclusively by the contract, including any deferral until full payment. The solution may contain third-party libraries, frameworks or services subject to their own licences, which the customer must respect.

Source code, configuration and documentation are handed over in the scope and format specified in the contract. Without an agreed transfer of rights, use remains within the licence terms.

4. Delivery, acceptance and operating environment

Delivery takes place by making the work available or installing it in the agreed environment, followed by written or implied acceptance that it meets the contract and approved specification. Rejection must be justified by a specific defect or discrepancy with the requirements.

The customer is responsible for the operating environment, including hardware, operating systems, cloud accounts and permissions, as well as data content and lawful use. Environment changes, third-party interventions or code changes without the contractor’s approval may limit warranty coverage under the contract.

5. Defect warranty

A defect is a discrepancy between the work and the contract or approved requirements. It is not a new feature request, an aesthetic design change, or an error caused by misuse, incompatible extensions or an outdated browser, unless otherwise agreed.

The warranty period and claims procedure are specified in the contract. B2B warranty periods are often shorter and more precisely defined than those in consumer relationships, where statutory consumer protection applies within the Civil Code and related legislation.

The contractor remedies defects within a reasonable time after a reproducible report. A temporary workaround by the customer does not remove the right to a remedy unless the contract states otherwise.

6. Support, maintenance and SLA

Support, maintenance or a service-level agreement may be arranged after the warranty period or for production operation, including response times, incident priorities and hours. Work beyond the agreed package is charged according to the price list or agreement. Changes in legislation, security standards or platforms may require a separate quotation.

7. Liability

The contractor is liable for damage caused by a breach of contractual duties to the extent and amount set by the contract and law. The contractor is not liable for lost profit, indirect damage or damage resulting from customer decisions made without consultation, unless the contract expressly provides otherwise. In B2B practice, liability limits are often agreed with reference to the fee for the work. The specific wording is always in the contract.

8. Confidential information

Both parties keep confidential the business and technical information obtained through the collaboration, for the period and subject to the exceptions specified by contract or law, such as mandatory legal or official requests.

9. Personal data in contract performance

If the customer supplies personal data for processing in an application or during the work, the controller–processor relationship is governed by the contract or a data processing agreement in accordance with the GDPR. This website text is not a complete privacy document; details may be provided in a separate document published on request.

10. Cookies and website analytics

This website may use cookies or similar technologies to measure visits, such as Google Analytics, according to the consent banner settings and the user’s preferences.

11. Contact

Questions about this page or business collaboration can be sent through the contact section on the home page.