1. Scope and core principles
This policy applies to static pages provided by V2Ray Official Site under v2ray1.com, including the home page, download pages, configuration reference, tutorials, technical notes, and legal pages. The site provides client information and configuration documentation. It does not offer account registration, comments, paid transactions, or email subscriptions, so visitors are not asked to submit their name, email address, phone number, payment details, or account password.
Visitors do not need to create a personal profile to read these pages. If you use a browser, network provider, or download service to access resources provided by another party, that party’s published rules govern the relevant processing activities. This policy does not cover applications, network services, or external pages that the site cannot control.
2. Access data and analytics
When responding to requests normally, the server may generate necessary access logs, including the request time, page visited, referring page, browser type, device category, language setting, network address, and request status. This information is used to keep pages available, investigate unusual requests, analyze compatibility issues, and handle basic security incidents. It is not used to build user profiles that identify personal interests or identities.
The site uses analytics tools to understand page-view trends, commonly used device types, entry pages, and content navigation paths. The results help determine whether download instructions are clear, tutorials are easy to find, and mobile layouts need adjustment. Analytics is primarily used in aggregated form; where system settings permit, network addresses are truncated, and raw logs and aggregated data are retained only for as long as needed for operation and maintenance.
3. Cookies and local storage
The main site functions generally do not depend on persistent identity information. Analytics tools may use Cookies to distinguish repeat visits and reduce duplicate counts. Language selection, tab state, or interface preferences may also be stored in the browser’s local storage. Such data is generally limited to language codes, page state, visit identifiers, and timestamps. It does not include client subscription URLs, node configurations, imported content, or system proxy rules.
You can use your browser settings to view, restrict, or delete Cookies and local storage data. After restricting them, static text and primary navigation will remain available, but language state, tab restoration, or analytics deduplication may not persist. Disabling browser storage does not automatically delete necessary access logs previously generated by the server.
4. Download links and third-party services
The download pages read current client versions and file paths from a same-origin version manifest, then direct visitors to the relevant file distribution service. When you click a download button, your browser sends a request to that file service, which may record the network address, request time, file name, browser information, and transfer status as required for its operation. The site does not receive subscription content imported into clients or read local configurations created after download.
Technical articles may mention projects or clients such as Project V, V2Fly, Xray, v2rayN, v2rayNG, and v2flyNG. These names are used to explain ecosystem relationships and software choices; they do not mean that the site controls their release schedules, file contents, or subsequent data handling. Before visiting a third-party page or using its services, review its privacy notice and terms separately.
5. Data security, policy updates, and feedback
The site limits data processing to what its static-site functions require and reduces misuse risks through access controls, log-permission management, software updates, and unusual-traffic checks. Internet transmission and browser environments may still be affected by device settings, network links, and third-party services. Visitors should manage client configurations, subscription URLs, and locally exported files carefully, and should not submit sensitive configurations on public pages.
This policy will be updated on this page when analytics methods, download procedures, site features, or applicable rules change, and the Last updated date at the top will be adjusted accordingly. Continuing to visit the site after an update means that you have read the revised version. If you have questions about client settings, subscription imports, or page operations, visit the configuration tutorial to check the steps. Policy-related questions can also be handled through the feedback path listed in the site documentation; the site does not require you to leave personal contact details on a public page.