Back home

Deliverable Rights and Intellectual Property

Version 2.0 · effective 25 August 2026

This page explains Velira’s default approach to rights in a website, bot, automation, design and related deliverables. The exact file list and the assignment or licence granted are always recorded in the individual proposal before work begins.

1. Custom deliverables

After full payment for the relevant stage, the client receives the agreed source files and an assignment or licence for elements created by Velira specifically for that project, to the extent stated in the individual proposal. Where law requires, an assignment identifies the specific works, permitted uses, territory and duration in a written/electronic record.

Moral rights remain with the author where they cannot lawfully be transferred. The client may change and develop the handed-over deliverable itself or through another supplier, but third-party changes are outside Velira’s warranty.

2. Velira’s pre-existing tools

Frameworks, modules, libraries, templates, methods, design systems, scripts, know-how and other materials created before the project or capable of reuse remain with Velira. Where embedded and necessary to use the paid deliverable, the client receives a non-exclusive, perpetual, worldwide licence to use them as part of that deliverable unless the proposal states otherwise.

3. Open-source, stock, fonts, platforms and AI

4. Client materials

Client-supplied text, logos, photos, video, databases, trade marks and other materials remain the client’s property. The client confirms that it holds the rights and permissions needed to use and provide them. The client grants Velira a limited permission to use them only to deliver, test, hand over and provide agreed support for the project.

5. Files, accounts and access handoff

The proposal lists the source-file formats, documentation, repository, configurations, accounts and credentials included in handoff. Where technically possible, domain, hosting, analytics, CRM and other key services are registered directly to the client. Passwords are never published in project documents and are transferred through a separate secure channel.

6. Hosting, domain and availability

Hosting and domain arrangements are chosen per project. Cost, account ownership, migration, backups, domain renewal and support level are set out in the proposal. Velira cannot guarantee a third-party platform’s or registrar’s uninterrupted availability; our responsibility is limited to the agreed setup and handoff work.

7. Portfolio and confidentiality

Velira may show the name, public link and images of a completed project only after public launch, unless the proposal or an NDA prohibits this and provided the client has not raised a reasonable objection. Non-public drafts, metrics, personal data, credentials and commercial information are not published without separate written permission.

8. Warranty fixes and support

The individual proposal defines the warranty period, support, response time and supported environments. Velira does not promise indefinite maintenance unless expressly agreed. The warranty excludes client or third-party changes, licence breaches, third-party outages and use outside agreed conditions.

9. Infringement notice

If you believe material used by Velira infringes your rights, contact Telegram @madbod_77 and identify the work, evidence of rights, exact URL and contact details. We will review the notice, temporarily restrict access where justified and report the outcome.