Terms & AgreementsGeneral Terms

Terms of Use

Terms of Use for Veap - a free and open-source framework for building modern web applications.

Updated September 20, 20265 min read1,088 words
doc:/termsEffective as of September 20, 2026
Markdown

1. About Veap#

Veap is a free and open-source framework for building modern web applications.

These Terms of Use ("Terms") apply to the Veap website, documentation, source code, packages, CLI tools, and other materials distributed as part of the Veap project.

By accessing or using Veap, you agree to these Terms.

If you do not agree with these Terms, you should not use the Veap website or project services.

2. Open-Source Software#

Veap is open-source software.

The Veap source code and individual packages are made available under the license specified in the relevant repository or package.

The applicable open-source license governs your rights to:

  • use Veap;
  • copy Veap;
  • modify Veap;
  • distribute Veap;
  • create derivative works.

Where a specific component is distributed under a different license, the license included with that component takes precedence for that component.

Nothing in these Terms limits rights granted to you by an applicable open-source license.

3. Use of Veap#

You may use Veap for personal, commercial, educational, research, or other lawful purposes, subject to the applicable software licenses and these Terms.

You are responsible for:

  • how you use Veap;
  • applications you build with Veap;
  • content processed by those applications;
  • complying with applicable laws and regulations;
  • securing your own applications and infrastructure.

Veap does not control applications built using the framework.

4. Applications Built with Veap#

Veap is a development framework and does not operate or control applications created by its users.

The developer or operator of an application built with Veap is solely responsible for that application, including:

  • its functionality;
  • its content;
  • its security;
  • its data processing;
  • its compliance with applicable laws;
  • its interactions with end users.

Using Veap does not create any relationship between Veap and the users of applications built with Veap.

5. No Warranty#

Veap is provided "as is" and "as available", to the maximum extent permitted by applicable law.

We do not guarantee that:

  • Veap will always be available;
  • Veap will be free of errors or bugs;
  • Veap will meet your specific requirements;
  • every release will be compatible with your application;
  • documentation will always be complete or current;
  • security vulnerabilities will never occur.

You use Veap at your own risk.

6. Limitation of Liability#

To the maximum extent permitted by applicable law, the Veap project and its contributors shall not be liable for any indirect, incidental, special, consequential, or other damages arising from or related to the use of Veap.

This includes, without limitation:

  • loss of data;
  • loss of profits;
  • loss of business;
  • service interruption;
  • application failures;
  • security incidents;
  • compatibility issues;
  • problems caused by third-party software or services.

Nothing in these Terms excludes or limits liability that cannot legally be excluded or limited under applicable law.

7. Security#

Veap is developed as an open-source project and security issues may be reported by the community.

Users are responsible for evaluating the security of Veap and the applications they build with it.

Security vulnerabilities should be reported through the security reporting mechanism described in the Veap repository.

Do not publicly disclose an undisclosed security vulnerability before the project has had a reasonable opportunity to investigate it.

8. Contributions#

Contributions to Veap are welcome.

By submitting code, documentation, bug reports, suggestions, or other contributions, you confirm that:

  • you have the right to submit the contribution;
  • the contribution does not knowingly violate the rights of others;
  • you understand that contributions to public repositories may become publicly available.

Contributions are subject to the contribution and licensing requirements specified by the relevant Veap repository.

Where a repository contains a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), those requirements also apply.

9. Community Conduct#

When participating in Veap community spaces, including GitHub issues, discussions, pull requests, or other official communication channels, users are expected to behave respectfully and professionally.

The project may moderate or remove contributions that are:

  • abusive or harassing;
  • discriminatory;
  • threatening;
  • intentionally disruptive;
  • fraudulent;
  • malicious;
  • unrelated to the relevant project space;
  • in violation of applicable law.

These rules exist to maintain a constructive open-source community.

10. Third-Party Services#

Veap may reference or integrate with third-party software, packages, hosting providers, repositories, or other services.

Third-party services are operated independently from Veap.

Veap is not responsible for:

  • the availability of third-party services;
  • their content;
  • their security;
  • their privacy practices;
  • changes to their terms;
  • their compatibility with Veap.

Your use of third-party services is subject to their respective terms and policies.

11. Intellectual Property#

Except where otherwise stated, the Veap project and its original materials are protected by applicable intellectual property laws.

Open-source licenses grant specific rights to use and distribute the software.

The Veap name, logo, trademarks, and other branding elements may be subject to separate trademark rights and are not necessarily covered by the software license.

Use of Veap branding must not falsely imply endorsement, sponsorship, or affiliation with the Veap project.

12. Forks and Derivative Projects#

Because Veap is open-source, anyone may create forks and derivative projects in accordance with the applicable software license.

Forks and derivative projects are independent projects unless explicitly stated otherwise.

The Veap project is not responsible for software, services, or modifications distributed by third parties.

13. Changes to Veap#

Veap is an actively developed open-source project.

Features, APIs, documentation, packages, and project structure may change over time.

We may:

  • add or remove features;
  • change APIs;
  • release new versions;
  • deprecate functionality;
  • modify documentation;
  • change project structure.

No particular feature, API, or release schedule is guaranteed unless explicitly stated otherwise.

14. Changes to These Terms#

These Terms may be updated from time to time to reflect changes to the Veap project or applicable legal requirements.

The latest version will be published on the Veap website.

The date of the latest update is shown at the top of this document.

15. Governing Law#

These Terms shall be governed by the laws applicable to the entity or individual operating the Veap project, subject to any mandatory provisions of applicable law.

If Veap is operated by an entity established in Poland, Polish law shall apply, subject to mandatory provisions of applicable law.

16. Contact#

Questions regarding these Terms can be directed to:

Email: hello@veap.pl

Veap - Open-source framework for modern web applications.

This document is an integral component of the Veap open-source governance and legal framework. For questions, licensing verification, or security inquiries, please contact the Veap Core Team at contact@veap.pl.

veap
Preparing0%