Legal

Terms & Conditions

January 2026

1. Definitions

"No Box Dev" (also "we", "us", "our") refers to NoBoxDev OÜ, a private limited company registered in the Republic of Estonia under registry code 17471005, VAT number EE102976786, with its registered address at Lasnamäe linnaosa, 11415 Tallinn, Harju maakond, Estonia.

"Client" (also "you", "your") refers to the individual or entity that has accepted a Proposal issued by No Box Dev.

"Proposal" refers to the project proposal document describing scope, timeline, deliverables, and investment, signed by both parties.

"Deliverables" refers to all work products described in the Proposal, including but not limited to source code, designs, documentation, and deployed applications.

"Agreement" refers to the signed Proposal together with these Terms and Conditions.

"Feature" refers to a distinct function of the product: an action, screen or user flow that does something when a user or the system triggers it, as described in the Proposal.

"Acceptance Criteria" refers to the written conditions a Feature must meet to count as done, as set out in the Proposal or agreed in writing.

"Bug" refers to an agreed Feature that does not work according to its Acceptance Criteria.

"Change Request" refers to any new Feature, any change to an agreed Feature or its Acceptance Criteria, or any other change to the scope.

2. Scope of Work

The scope of work is defined exclusively by the signed Proposal. Any work beyond the agreed scope is a change request and will be quoted separately before it is carried out.

We reserve the right to determine the technical approach, tools, and architecture used to deliver the agreed functionality, unless specific technologies are stipulated in the Proposal.

3. Payment Terms

Unless stated otherwise in the Proposal, payment is structured as follows:

  • 50% upfront — due upon signing, before work commences.
  • 50% on delivery — due upon delivery of the final Deliverables.

All invoices are payable within 14 days of the invoice date. Amounts are in euros and exclusive of VAT, which is charged where applicable under Estonian and EU VAT rules. Late payments incur late payment interest at the rate set out in the Estonian Law of Obligations Act (Võlaõigusseadus).

4. Timeline & Delivery

Estimated timelines in the Proposal are provided in good faith but are not binding deadlines unless explicitly marked as such. We will communicate proactively if delays arise.

Timely delivery depends on the Client providing required materials, feedback, and approvals within reasonable timeframes. Delays caused by the Client may shift the project timeline accordingly.

5. Client Responsibilities

The Client agrees to:

  • Provide all necessary content, assets, credentials, and access required for the project.
  • Designate a single point of contact for project communication.
  • Test each delivery and send feedback and Bug reports within 5 business days, unless otherwise agreed.
  • Ensure that any materials provided do not infringe on third-party rights.
  • Engage in the collaboration in good faith, working with us towards the shared goal described in the Proposal.

The Client is also responsible for knowing what they want built. Features and Acceptance Criteria are agreed before development starts, and the Client sticks to them while they are being built (see section 6).

6. Features, Bugs & Changes

Bugs are fixed in up to 3 rounds per delivery. In each round, the Client tests the delivery and sends all Bugs found in one list. We fix them and deliver again. After the third round the delivery is accepted, except for reported Bugs we have not yet fixed, which we still fix at no extra cost. Bugs found after acceptance are covered by the support period in section 8.

What is not a Bug. A request to change how an agreed Feature works or looks, behaviour that is not in the Acceptance Criteria, or a new Feature is not a Bug. These are Change Requests.

New Features only by written agreement. New Features and changes to agreed Features are only added after both parties agree in writing, including the effect on cost and timeline.

Extras we choose to offer. Sometimes we build something beyond the agreed scope at no charge, for example to help a new company get started. This is a goodwill gesture. It does not become part of the scope, is not covered by warranty or support, and does not create an obligation to offer it again. We may change, stop supporting or remove these extras in later versions when that is better for the product or the collaboration. We will tell the Client in writing beforehand.

Stable scope. Once a Feature and its Acceptance Criteria are agreed, they stay fixed while the Feature is being built. Changing direction on an agreed Feature during development is not allowed; any change goes through a Change Request. When we notice this happening, we will point it out in writing.

Pausing development. If changes, unclear requirements or missing feedback keep happening after we have pointed them out, and this makes the collaboration ineffective or adds more than 30% to the estimated time, we may pause development. We resume once the Client has delivered clearly defined Features with Acceptance Criteria in writing. During a pause the timeline is on hold. Time spent beyond the estimate because of these changes is charged at the hourly rate in the Proposal.

7. Intellectual Property

Upon receipt of full payment, all transferable intellectual property rights in the custom Deliverables transfer to the Client, except for:

  • Pre-existing IP — tools, libraries, and frameworks owned by No Box Dev or third parties before the project. These are licensed to the Client for use within the project.
  • Open-source components — third-party code used under their respective open-source licences, which remain governed by those licences.

No Box Dev retains the right to use general knowledge, techniques, and non-confidential concepts developed during the engagement for future work.

8. Warranties & Support

We warrant that all Deliverables will substantially conform to the specifications in the Proposal at the time of delivery.

A post-launch support period of 2 weeks is included after final delivery, covering fixes for Bugs in the delivered work. Support beyond this period can be arranged under a separate agreement.

We do not warrant uninterrupted operation of third-party services, APIs, app store approval timelines, or infrastructure outside our control.

9. Limitation of Liability

Our total liability under any engagement shall not exceed the total fees paid by the Client for that engagement.

We shall not be liable for indirect, incidental, consequential, or special damages, including but not limited to loss of revenue, data, or business opportunities, even if advised of the possibility of such damages.

These limitations do not apply to damage caused intentionally or through gross negligence, or where Estonian law does not permit liability to be limited.

10. Termination

Either party may terminate the Agreement with 14 days' written notice.

Termination for material breach may take effect immediately upon written notice, provided the breaching party has first been given 7 days to remedy the breach.

Client not doing their part. We are not obliged to keep working when the Client does not fulfil their part of the Agreement, for example by not testing, not giving feedback or approvals on time, not providing what we need, or by repeatedly changing the scope. We will point this out in writing and give the Client at least 7 days to get back on track. If that does not happen, we may end the Agreement in writing with immediate effect.

11. Ending the Collaboration

Good work depends on a working relationship in which both parties move towards the same goal. No Box Dev reserves the right to end the engagement when it has become clear that effective collaboration towards a shared goal is not possible.

This may be the case when, for example, feedback or approvals are repeatedly withheld or contradictory, direction keeps changing in ways that prevent progress, or communication and conduct undermine the ability to deliver the work.

Before ending the engagement on this basis, we will:

  1. Raise the concern with the Client in writing, describing what we observe.
  2. Offer a conversation to look for a way forward together.
  3. Allow a reasonable period, of at least 7 days, for the situation to improve.

If no workable way forward is found, we may end the engagement with 7 days' written notice. This is not a judgement of either party, and the consequences in section 12 apply.

12. Consequences of Termination

When the Agreement ends under section 10 or 11:

  • The Client shall pay for all work completed up to the termination date.
  • No Box Dev hands over the work as described in section 13.
  • Any upfront payment for undelivered work will be refunded proportionally.
  • Intellectual property in the delivered work transfers to the Client in accordance with section 7, once the amounts due have been paid.

13. Handover

When a project ends, for whatever reason, we hand over the code to the Client or to a third party the Client appoints.

Only paid work is handed over. We hand over the work that is part of the agreed scope in the Proposal and that has been paid for. Handover does not happen while payments are still open. A request for handover does not change what is owed: the amounts due under the Proposal are paid first.

What handover includes. The source code of the custom Deliverables and the documentation that already exists. Pre-existing IP and open-source components are handled as described in section 7. Extra handover work, such as writing new documentation, onboarding a third party or migrating systems, is a Change Request.

After handover. From the moment of handover, building, hosting and maintaining the product is the responsibility of the Client and any third party they work with, unless a maintenance subscription has been agreed and paid. We are not responsible for changes others make to the code after handover, and the support period in section 8 does not cover code changed by others.

14. Portfolio & Attribution

No Box Dev may reference the project in its portfolio, website, and marketing materials, including a brief description and non-confidential visuals, unless the Client opts out in writing.

15. Force Majeure

Neither party shall be liable for delays or failure to perform due to circumstances beyond reasonable control, including but not limited to natural disasters, government actions, pandemics, or infrastructure failures.

16. Governing Law & Disputes

Every Agreement between No Box Dev and the Client, including these Terms and Conditions and each Proposal, is governed by the laws of the Republic of Estonia.

The parties will first try to resolve any dispute through good-faith discussion. Disputes that cannot be resolved this way shall be submitted to Harju County Court (Harju Maakohus) in Tallinn, Estonia.

17. Applicable Terms

The terms and conditions published on our website, noboxdev.com, always apply to every engagement. By signing a Proposal, the Client accepts these terms as published there.

18. Language

These terms are drawn up in English. If they are translated, the English version prevails.