General Terms
A plain-language project framework. The signed proposal controls where it differs.
Last updated: 9 August 20261. Scope and contract
A contract is formed only when both parties accept a written proposal or order confirmation. Demo pages and published prices are invitations to request a proposal, not binding offers.
2. Scope and client responsibilities
Deliverables, milestones, content responsibilities, languages, integrations and acceptance criteria are stated in the proposal. The client must provide lawful content, licences, feedback and access reasonably required for delivery.
3. Prices and payment
Prices are stated before work begins and indicate whether VAT applies. Payment may be made by agreed bank transfer, SEPA, PayPal or supported card method. Larger projects may use deposits and milestone invoices. Payment-provider terms may also apply.
4. Changes and delays
Work outside the agreed scope requires written approval and may change price or timing. A timetable may move when required content, access or feedback is delayed.
5. Intellectual property
Ownership and usage rights transfer only as described in the proposal and normally after full payment. Third-party software, fonts, stock media and open-source components remain subject to their respective licences.
6. Acceptance, warranty and liability
The client should test deliverables during the agreed review period. Mandatory statutory rights remain unaffected. Any contractual limits of liability must be adapted to applicable law and the customer category.
7. Cancellation and consumer rights
If services are sold to EU consumers remotely, mandatory pre-contract information and withdrawal rights may apply. Work should not begin during a withdrawal period without the required express request and acknowledgements. Confirm the exact workflow with qualified counsel.
8. Governing law
The governing law and competent venue must be specified in each proposal without excluding mandatory consumer protections.