Veltrionex

Terms

The terms ofan engagement.

These terms cover the Veltrionex website and the start of a conversation. The product we build for you is governed by the agreement we both sign.

Updated 30 September 2026

01

Using the website

You may read this site, share links to it, and use the contact form to tell us about a project. You may not scrape it in a way that degrades the service, misrepresent yourself, or attempt to break the site.

The writing, the mark, and the images on this site belong to Veltrionex unless a caption says otherwise. You may not copy them for your own commercial use.

02

Starting a project

An email, a call, or a proposal is a conversation, not a contract. Work begins when both sides agree in writing on the scope, the fee, and the timeline.

Until that agreement exists, either side can stop the conversation. We will say so plainly, and we ask the same of you.

03

Scope and changes

A first release is defined so it can ship. Work outside that definition is a change. We will price and schedule a change before we build it, unless a smaller fix is already covered.

You will have a named point of contact. Feedback that arrives after a review window may move the date. We would rather move the date than ship something neither side has seen.

04

Your materials

You are responsible for the copy, data, and brand material you give us, and for having the right to let us use them on the project. We will use them only for that work.

Tell us if something you share is confidential, export-controlled, or not meant for a vendor. We will treat it that way or we will decline it.

05

Intellectual property

Once the agreed fees are paid, you own the product we built for you under the agreement: the interface, the application code written for the engagement, and the deliverables named in the scope.

Veltrionex keeps its pre-existing tools, libraries, know-how, and anything we built before the project or outside it. Where a deliverable depends on those, you receive the license you need to run and maintain the product. Third-party software stays under its own license.

06

Confidentiality

Each side keeps the other’s non-public information private and uses it only for the project. That duty does not cover information that is already public, already known, or independently developed.

We may describe the engagement in general terms — the kind of product and the discipline — unless the agreement says the work is unnamed. We will not publish your numbers or your unreleased product without permission.

07

Payment

Fees, expenses, and the payment schedule live in the agreement. Invoices are due on the date printed on them. We may pause work if a payment is late, after we have written to you.

A deposit, when the agreement asks for one, is applied to the first phase. It is not a retainer for open-ended support unless the agreement says it is.

08

Liability

The website is provided as a studio introduction. We do not promise that it is free of errors or that it will be available without interruption.

For a project, the liability terms in the signed agreement control. If there is no signed agreement yet, neither side is liable to the other for lost profit or for indirect damage arising from the conversation.

09

Ending the work

Either side may end an engagement as the agreement describes. We will hand over the work completed and paid for, including the repository access the agreement promises.

Sections that should survive — confidentiality, ownership of what was paid for, and payment for work already done — survive the end of the engagement.

PrivacyHow we handle what you share.CookiesWhat this site keeps.