Terms of Use
Last updated June 21, 2026
These terms govern your use of the pawrly.dev website and its documentation. Use of the Pawrly software itself is governed by its open-source license.
The software is open source
Pawrly is licensed under the Apache License 2.0. Your rights to use, modify, and distribute the software are defined by that license, which controls over these website terms for anything concerning the software. These terms cover the website and documentation only.
Acceptable use
By using this website, you agree not to:
- attempt to disrupt, attack, or gain unauthorized access to the site or its infrastructure;
- scrape or access the site in a way that places an unreasonable load on it; or
- use the site to violate any applicable law.
Intellectual property
The Pawrly name, logo, and the content of this website are the property of the project and its maintainers, except where third-party content is attributed. The open-source code is available under its license; these terms do not grant rights to the name or branding beyond fair, descriptive reference.
No warranty
The website and documentation are provided “as is,” without warranties of any kind, express or implied, including accuracy, fitness for a particular purpose, or non-infringement. The software carries the warranty disclaimer stated in its license.
Limitation of liability
To the maximum extent permitted by law, the project and its maintainers are not liable for any indirect, incidental, or consequential damages arising from your use of the website or documentation.
Third-party links
This site links to third-party resources we do not control. We are not responsible for their content or practices, and a link is not an endorsement.
Changes
We may update these terms from time to time. The “Last updated” date above reflects the current version, and continued use of the site means you accept the latest terms.
Governing law
These terms are governed by the laws of the maintainers' jurisdiction, without regard to conflict-of-law rules.
Contact
Questions about these terms can be raised via the project's GitHub issues.