Last updated: October 2026
Privacy Policy
How we handle access logs, browser storage, and download sources.
This policy applies to page views and download links on v2raykey.com. We provide client information and setup guides. Data handling by client apps, subscription services, and external file providers is governed by their respective policies.
1. What data we collect
This is a static content site. We don’t offer account registration or email signup forms. You can read guides and client descriptions without providing your name, phone number, or subscription credentials. Subscription settings shown on these pages are for instructional purposes only: we don’t read your system clipboard or retrieve node configurations from client apps.
When you access pages, images, or download links, our hosting and network providers may process your IP address, request time, URL path, response status, browser type, and referring page. These technical logs help deliver content, diagnose access issues, and handle unusual requests. They are not information you have actively submitted.
Don’t include subscription URLs, passwords, or other sensitive information in page addresses, query parameters, or public screenshots. URL parameters may be included in access logs. Don’t replace sample content in our guides with real credentials and share it publicly.
2. Analytics and how we use data
We use analytics to understand page views, traffic sources, device types, and which platforms visitors choose for client downloads. When you select a download platform, we may record the platform name and other interaction events to see whether download links are easy to find and whether our guides need more detail.
Analytics measure activity at the page and interaction level. They are not used to collect subscription contents, node passwords, proxy traffic, or client logs. A regular webpage visit also doesn’t tell us which node a client app connects to.
Technical logs and analytics data are used only for site maintenance, troubleshooting, and necessary security measures. Retention periods depend on hosting and analytics configurations, so we don’t promise a fixed number of days. Data that is no longer needed should be deleted or retained only in aggregated form.
3. Cookies and local storage
Your browser may cache fonts, stylesheets, and scripts to avoid repeat downloads. Caching is different from cookies and local storage. Whether analytics tools set cookies or other identifiers depends on their deployment settings and your browser permissions. If used, these identifiers should be limited to recognizing visits and measuring site usage.
Platform tabs on a page can restore your selection using a fragment in the URL; this doesn’t require creating a personal profile. If a feature uses local storage to save interface preferences, it should store only those preferences, not subscription credentials.
Use your browser’s site settings to block cookies, clear site data, or restrict scripts. Some analytics or interface states may not work or persist when restricted, but static content will remain available. Clearing browser data does not also delete access logs already stored on our servers.
4. Download sources and third-party services
Client download links use file addresses provided by our deployment services. Files may be delivered through a download relay or redirect to an external source listed in the download manifest. Download requests may send your IP address, request time, and browser information to the service hosting the file. That service’s own rules govern its records.
This site’s policy does not replace the privacy policies of client apps, core developers, or subscription providers. System proxy, network connection, or VPN permissions granted after installation are part of how the local client operates. Providing a download link does not give this site those permissions.
Before opening an external source, check the address and the provider’s privacy information. Import subscriptions into your client app as described in our guides; don’t submit subscription contents to unrelated websites.
5. Policy updates and questions
We’ll revise this page if our data practices, analytics features, or download routes change materially, and update the month shown at the top. The revised policy applies to processing carried out after publication. If a new purpose requires consent, we’ll provide a separate notice; a policy update does not replace any required authorization.
If you have questions about page actions or permissions, check the Getting Started guide to verify the client steps, then see the subscription import instructions to troubleshoot setup. Hide subscription URLs and access credentials when describing an issue, and don’t share logs or screenshots containing sensitive information.