Terms of Use
Last updated:
1. Scope and purpose of this documentation
These terms apply when you visit V2Ray Config Guide, read its documentation, or use the client download links provided here. Our installation instructions, configuration examples, and troubleshooting guidance are for educational and technical reference only. They are not legal advice and do not replace documentation published by software projects or the terms of service set by service providers.
Menus, permission prompts, and results may vary by client version, operating system, and network environment. Before following an example, check the software’s documentation and the interface you see. Before changing system proxy, routing, or network permissions, consider recording your existing settings so you can restore them if the change disrupts your connection.
2. Lawful use and authorization
When using a client, subscription link, or example from this site, comply with the laws and regulations that apply where you are and to your activities, as well as any rules governing the devices and networks involved. Do not use this site’s materials, software download links, or related configurations for illegal purposes. Get permission before accessing or changing devices or networks managed by another person or organization, and stay within the scope of that permission.
You are responsible for your client configuration and how you use it. Keep subscription links, node credentials, and access tokens secure. Before quoting logs, submitting screenshots, or sharing a configuration, remove sensitive information that could identify an account, device, or network environment, and comply with applicable personal data protection requirements.
3. Third-party software and liability
v2rayN, v2rayNG, and v2flyNG are provided and maintained by their respective open-source projects. This site curates download links and usage guides; it is not affiliated with the project maintainers and does not operate third-party subscription or node services. Fees, refunds, service periods, privacy practices, and dispute resolution for third-party services are governed by the terms published by each provider.
To the extent permitted by applicable law, this site does not guarantee that software, download links, or third-party services will remain available, or that configuration examples will work in every environment. This site is not liable for losses such as data loss or interrupted connections resulting from software installation or updates, settings changes, third-party service outages, or reliance on examples published here. Nothing in this section excludes or limits liability that cannot legally be excluded or limited.
4. Intellectual property and open-source licenses
The code and attribution for each open-source project belong to their respective rights holders. Use, modification, and redistribution are subject to the applicable open-source licenses and notices. Providing download links or mentioning software names does not alter the original licenses or grant any rights to use trademarks, logos, or other materials. When redistributing software, follow the license and notices distributed with it.
The site’s tutorials and open-source software are licensed separately. Unless permitted by law or expressly authorized, you must obtain permission from the relevant rights holder before reproducing, translating, or adapting original text or illustrations from this site. When quoting, credit the source. Do not excerpt or rewrite material in a way that suggests it was published or endorsed by a project maintainer.
5. Updates and feedback
Revised terms will be published on this page, and the date at the top will be updated. Unless stated otherwise or required by law, changes take effect when published. For material changes to the scope of use or allocation of responsibility, this page will describe what changed and when the changes apply.
If a menu label, procedure, or troubleshooting step no longer matches the current version, first check the relevant section in the Quick Start Guide. When reporting an issue, include the client name, operating system version, steps taken, and redacted error details to help distinguish documentation differences from software or service problems.