Terms

These terms apply to CodeOne services unless the parties have agreed otherwise in writing. They set the general collaboration framework, but they do not replace the project-specific proposal, scope description, or agreement.

For each project, at minimum the scope, expected timeline, pricing, delivery format, and key responsibilities are confirmed separately.

Work begins once the parties have confirmed the proposal or agreement in writing. Before that, there may be discovery, review, or preparation work, but this does not automatically mean a full project has started.

The proposal or agreement defines what is included in the scope. Anything outside that agreed scope is treated as additional work or as part of a later phase.

Pricing is defined in the proposal or agreement. Unless stated otherwise, estimates for open-ended work are not fixed final prices, but are based on the known scope and assumptions at that time.

CodeOne may require an upfront payment, milestone-based payments, or staged billing. Invoices are payable by the due date stated on the invoice. In case of payment delay, work may be paused until payment is received.

The client must provide the information, access, approvals, and feedback needed to carry out the work within a reasonable time. Delays in input or approvals may affect scheduling, prioritization, and delivery timing.

CodeOne is not responsible for delays caused by late client input, missing access, delayed materials, or missing confirmations.

Project details often become clearer during execution. If a change affects the agreed scope, priorities, timing, or technical solution, it is treated as a change request that requires separate confirmation.

CodeOne may recommend splitting the work into phases where that helps keep the scope, investment, and decisions under control.

Work is considered delivered once the agreed deliverable has been presented to the client or deployed according to the agreed format. The client is expected to review the work within a reasonable time and either confirm acceptance or point out material issues.

If the client continues using the delivered work or delays feedback without reasonable cause, the delivered scope may be considered accepted to the extent it has been presented.

Unless otherwise agreed, rights to the specifically commissioned final deliverable transfer to the client after full payment of the agreed fees, to the extent necessary for the client to use the work in its business.

CodeOne retains rights to pre-existing methods, components, internal processes, general technical approaches, and tools used during the work, unless otherwise agreed.

Both parties treat business, technical, and other non-public information disclosed during cooperation as confidential and use it only for the purpose of the collaboration.

If the project involves personal data processing, the relevant data protection roles and responsibilities are agreed separately when needed.

CodeOne is responsible for performing the agreed work professionally within the agreed scope, but is not liable for indirect damages, lost profit, campaign outcome, third-party platform changes, or consequences of client-side decisions, unless the law requires otherwise.

For websites, integrations, and automations, outcomes often depend on third-party systems, input quality, data quality, and the client's internal processes. For that reason, project results are always assessed within the actual project context, not as an abstract guarantee.

If one party materially breaches the agreement and fails to cure that breach within a reasonable time after notice, the other party may terminate the collaboration. In that case, work already performed and justified costs incurred remain payable.

If the project is paused or terminated at the client's initiative, this does not automatically cancel payment for work already completed. Billing in that case is based on the actual completed work up to that point.