Terms and Conditions

Scope and contract documents

Every engagement should be defined by a written proposal, statement of work, service order or agreement stating the responsible company, scope, deliverables, assumptions, commercial terms and relevant milestones. This page is a general explanation, not a substitute for a signed project agreement.

A brief, statement of work, service-level agreement, data-processing agreement or other attachment may supplement the contract.

Starting a project

An enquiry is not an order. A project starts when the relevant provider and client accept an offer or agreement and any agreed start conditions (such as access, content and an advance) are met. Work allocation depends on capacity and the actual statement of work.

Milestones, review and acceptance

Projects may include discovery outputs, interface designs, code repositories, working website environments, audit reports, campaign assets, dashboards or support tasks. The contract should state which deliverables are included, how reviews take place and any acceptance criteria and response windows.

Changes that materially alter features, platforms, content volume, integrations or timelines should be approved through a revised scope or change request before new work begins.

Client responsibilities

Clients normally supply accurate objectives, lawful materials, timely feedback, authorised approvals and access needed for delivery. Access should follow the least-privilege principle; passwords and sensitive material should be shared by agreed secure channels rather than unsecured enquiry forms.

Clients retain responsibility for the legality of business claims, products, advertising claims, consent collection and materials they submit, while the provider remains responsible for obligations it accepts and those imposed by law.

Fees, third-party costs and changes

The applicable quote defines currency, invoicing company, tax treatment, milestones, payment due dates and whether work is fixed-fee, time-based or recurring. Domains, hosting, paid tools, stock media, advertising spend, licences and third-party API usage are identified separately unless expressly included.

Out-of-scope work, late-stage scope changes and extra revisions should be priced and approved before performance. Non-payment consequences, pauses or termination follow the agreed contract and mandatory law.

Handover, intellectual property and maintenance

Ownership or licensing of custom deliverables, access to source code, third-party components and reusable provider tools depend on the accepted agreement and applicable intellectual-property law. Client-owned materials remain client-owned. Open-source software and third-party services retain their own licence terms.

Support, hosting, maintenance, monitoring, backup scope and response windows apply only if specifically included in an agreement or support plan.

Data access and confidentiality

Confidential information should be protected within the agreed project workflow. Where the provider processes personal data on behalf of the client, a suitable data-processing agreement should be established before that processing, where required by GDPR Article 28.

Delays, risks and project issues

Both sides should promptly communicate dependencies, blockers and material schedule risks. Third-party outages, provider changes, data quality, review cycles and client-requested changes can affect schedules. Remedies, termination rights and dispute arrangements depend on the signed contract and non-excludable legal protections.