Legal Disclaimer and Acceptable Use Notice

This project is provided solely for lawful, authorized, and good-faith research, interoperability testing, personal administration, and defensive network engineering. By downloading, compiling, configuring, deploying, or using Skirk, you agree that you are solely responsible for ensuring that your use complies with all applicable laws, regulations, contracts, account terms, acceptable-use policies, workplace or school policies, and network-owner rules.

Skirk is not affiliated with, sponsored by, endorsed by, approved by, or associated with Google, Google Cloud, Google Drive, Cloudflare, GitHub, Microsoft, Android, or any other third-party provider or trademark owner. All product names, trademarks, and service names are the property of their respective owners and are used only for descriptive compatibility and research discussion.

Skirk is not a tool for unauthorized access, policy evasion, abuse, harassment, spam, fraud, credential misuse, data exfiltration, infringement, or concealment of unlawful activity. Do not use Skirk on networks, accounts, services, devices, or systems that you do not own or lack explicit permission to test. Do not use Skirk to bypass access controls, monitoring, rate limits, payment requirements, sanctions controls, provider restrictions, employer policies, school policies, government controls, or any other rule that applies to you or to the systems involved.

Use of third-party services may consume quotas, create costs, violate account policies, trigger automated enforcement, suspend accounts, delete data, or expose metadata to service providers. You are solely responsible for reading and complying with the current terms, documentation, quotas, billing rules, security requirements, and acceptable-use policies of every service you configure with Skirk. The maintainers do not grant you permission to use any third-party infrastructure and cannot authorize activity on behalf of any provider, network owner, employer, school, government, or other third party.

Skirk configurations can contain sensitive credentials, including OAuth refresh tokens and shared tunnel secrets. You are solely responsible for securing, rotating, revoking, and deleting those credentials and for controlling access to any machine running a Skirk client or exit. A Skirk exit can observe destination metadata and may see plaintext for non-TLS application traffic, like any proxy or VPN exit.

THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, SECURITY, AVAILABILITY, ACCURACY, OR ERROR-FREE OPERATION. TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE AUTHORS, COPYRIGHT HOLDERS, CONTRIBUTORS, AND MAINTAINERS SHALL NOT BE LIABLE FOR ANY CLAIM, DAMAGE, LOSS, COST, EXPENSE, ACCOUNT ACTION, SERVICE INTERRUPTION, DATA LOSS, LOST PROFITS, LEGAL EXPOSURE, OR OTHER LIABILITY ARISING FROM OR RELATED TO THE SOFTWARE, DOCUMENTATION, CONFIGURATION, DEPLOYMENT, OR USE OF SKIRK, WHETHER IN CONTRACT, TORT, STRICT LIABILITY, NEGLIGENCE, OR OTHERWISE.

Nothing in this repository is legal advice, security advice, compliance advice, or professional advice. If you are unsure whether a use is permitted, do not use Skirk until you have obtained written authorization from the relevant account owner, network owner, service provider, employer, school, or other authority, and, where appropriate, advice from a qualified professional.