Contracts for websites and apps: code rights
Every project runs on an order that sets out the scope, dates and fee, and once paid in full the code is yours: with the repository, the documentation and the full economic copyright to what we made for you.
The documents a project can rest on
The order is written for each project on its own, while the terms and the privacy policy are shared by all of them. The rest joins only when it is needed.
Before we discuss the details
NDAWhat stays between us before there is an order.Signed at your request.When the project starts
orOrderWhat we do, by when and for how much, written for each project on its own.Binding once confirmed or once the advance is paid (cl. 3.1).Your templateYour own clauses in place of our order, when your company requires its own contract.We read it before the quote.When we have access to your customers' data
Data processing agreementA separate agreement for when we process your customers' personal data (Article 28 GDPR).On your template or our draft.
Shared by every order
Terms of service
The rules every order shares, from making the contract to confidentiality.
Version effective from: 10 October 2026.
- 1General provisions
- 2Definitions
- 3Formation of contract and scope of work
- 4Delivery and acceptance
- 5Remuneration and payment
- 6Copyright and licences
- 7Warranty and support
- 8Liability
- 9Confidentiality
- 10Personal data
- 11Maintenance and service levels
- 12Third-party services
- 13Security and backups
- 14Force majeure
- 15Termination
- 16Consumers and sole traders with consumer rights
- 17Complaints
- 18Website, client panel and communication
- 19Amendments to the Terms
- 20Final provisions
Privacy policy
How we handle your company's data as our client.
Last updated: 18 May 2026.
Client data (in connection with the performance of Orders): for the duration of the contract and 5 years after its termination (tax and accounting requirements).
What the order contains
This is an order in short. Next to each of its parts stands what that part means for you.
- Basis
- the terms and this offer
- Made
- confirmation or the advance
The agreement is made when we confirm the order in writing, including electronically, or when you pay the advance (cl. 3.1).
The agreement is made when we confirm the order in writing, including electronically, or when you pay the advance (cl. 3.1).
What is in scope decides the price and what you accept, and both sides confirm any change in writing (cl. 3.3).
What is in scope decides the price and what you accept, and both sides confirm any change in writing (cl. 3.3).
Dates from a call are estimates; they become binding only in the order (cl. 4.4).
Dates from a call are estimates; they become binding only in the order (cl. 4.4).
Most often three equal parts, as described on our payments page.
Most often three equal parts, as described on our payments page.
You check the project on the test version before it goes live.
You check the project on the test version before it goes live.
90 days as standard; how long for your project is shown on our warranty page.
90 days as standard; how long for your project is shown on our warranty page.
The key clauses of our terms
Every clause that decides what you can and must do in a project: word for word, with the core highlighted, and one sentence in plain words.
Any changes to the scope of an Order require the written consent of both parties and may result in an adjustment of the remuneration and delivery timeline.
Adding a feature midway is a scope change both sides confirm in writing, together with the new price and date.
The Client is obliged to provide, within the agreed time, all materials, content, access credentials, and information necessary for the execution of the Order. Delays attributable to the Client shall not be charged to VulCode.
If content or access arrives later than scheduled, the project date moves by that delay.
In the event that the Client withdraws from the Order after work has commenced, VulCode is entitled to retain the advance payment and any remuneration for work already performed.
If you withdraw after work starts, you pay for the work done so far and we keep the advance.
Upon full settlement of remuneration, the Client acquires full economic rights to the code, graphics, and other materials created specifically for the Client within the scope of the Order.
The code, graphics and materials made for you are yours after the last payment.
VulCode retains the right to present completed work in its portfolio, unless the Client has required confidentiality.
The project goes into our portfolio only if you do not ask for confidentiality.
Open-source libraries, frameworks, and tools used in the execution of an Order are subject to their own licences, which the Client accepts as part of the project.
Libraries do not become anyone's property: you use them on the terms of their licences.
VulCode's total liability for non-performance or improper performance of an Order is limited to the amount of remuneration paid by the Client for that Order.
The ceiling of our liability is the amount paid for that order.
The Client bears sole responsibility for the content, data, and materials provided to VulCode in the course of executing the Order.
You are responsible for the texts, photos and data you give us for the project.
Both parties undertake to maintain the confidentiality of all confidential information obtained in connection with the execution of the Order.
Confidentiality binds both sides, except for information that is public, required by law or known before (cl. 9.2).
VulCode reserves the right to amend these Terms of Service. Clients will be notified of material changes at least 14 days in advance.
You hear of a material change to the terms at least 14 days before it takes effect.
Both parties shall endeavour to resolve any disputes arising from the provision of services amicably. In the absence of agreement, disputes shall be submitted to the court competent for the registered place of business of VulCode, and disputes with Consumers and Sole Traders with Consumer Rights to the court competent under the general rules.
We first try to settle a dispute amicably, and without agreement it goes to the competent court.
What you own
Once paid in full, the project does not depend on us. We hand over the code without licence locks or dependence on our infrastructure.
With the most common split into thirds, the code rights stay with us until the last payment (cl. 6.4).
- Advancebefore work starts1/3
- Stage paymentonce you accept the stage on the test version2/3
- Final paymentafter final acceptance3/3
The rights pass to you
cl. 6.1- Code: a private repository with the full change history
- Documentation: setup from scratch, architecture and deployment
- Materials: the graphics, design and content made for you
- Access: accounts, the domain and outside services in your company's name
You can then change the code yourself or with another team, and we remove our access and confirm it in the panel.
Our order or your contract template
We work either way. The choice depends on whether your company requires a contract on its own template.
Our order and terms
- Scope: features, pages, integrations
- Dates: stages and the whole
- Fee: most often three equal parts
- Warranty: from final acceptance
- You have no contract template of your own.
- You want to start quickly.
We write the scope, dates and payment stages under our terms, straight from the quote.
Your template
- Subject of the contract
- Dates and acceptance
- Copyright
- Data and securityto discuss
- Your company requires its own contract, e.g. via a legal team.
- You need specific clauses on data or security.
We read it before quoting and tell you which clauses need a conversation.
Data processing agreement (Article 28 GDPR)
It joins either variant when we have access to your customers' personal data, for example in a store migration. We work on your template, and without one we draft one for your approval.
Code rights and confidentiality
The key terms that apply to every project.
Hosting where you like
- The code does not depend on our infrastructure, so you can move the project whenever you want.
- With us the project runs under a subscription, with monitoring, and the hosting cost depends on the project.
- On your account, for example on AWS, GCP or Vercel, we deploy the project and hand you full access. We remove our own access when you ask.
- An overdue invoice may pause the work or access to what we have already delivered (cl. 5.3).
Libraries on their own licences
- ReactMIT
- ViteMIT
- highlight.jsBSD-3-Clause
- TypeScriptApache-2.0
- Frameworks and libraries keep their own licences, which become part of the project (cl. 6.3).
- The economic rights you receive cover the code, graphics and materials made for you, not other people's libraries (cl. 6.1).
- MIT, BSD-3-Clause and Apache-2.0 allow commercial use, as long as the authors' notice and the licence text stay in place.
- Licences read from the package files of this site's code.
Confidentiality from the first call
- We sign an NDA before discussing details, when even the first call touches on confidential things.
- We show the project in our portfolio only if you do not ask for confidentiality (cl. 6.2).
- Some work is done by subcontractors, such as Aphrodi for visual design, while responsibility and contact with you stay with us.
- Confidentiality does not cover what is public, required by law or known before the contract (cl. 9.2).
Common questions about contracts
Answers based on our terms and on how we make orders.
Read next
What to read alongside the contract rules.
A question about the contract?
Tell us what it is about and we will answer concretely, usually within an hour.