Privacy Policy

ProxysVPN (in Russian, ПроксисВпнович; the “Service”, “we”) is a VPN service. This policy explains what data the Service handles, why, for how long, who else processes it and how you can have it deleted.

It covers the website proxysvpn.com and its reserve addresses, the Telegram bots @proxysvpn_bot and @proxysvpn_support_bot, the Telegram Mini App, the ProxysVPN apps and our VPN servers. Other VPN apps that you may use with the Service have privacy policies of their own.

The Service is not intended for children. We do not knowingly collect data from anyone under 18; if we learn that a child has created an account, we will delete it.

If you do not agree with this policy, please do not use the Service.

We do not sell or rent your data and do not use it for advertising or profiling. We do not tell anyone which sites and services you open through the VPN, and we do not pass on the content of your traffic; the one exception is a demand from a court or a public authority that the law obliges us to carry out (section 5). Other data about how the VPN works, and data collected through our apps, goes only to those named in this policy and only in the cases it describes: to our service providers, on our instructions, to run the Service (section 6); to the support assistant and the services through which it and our support team work, when you contact support (section 3, section 11); and to a court, a public authority, a bank, a payment provider and our lawyers, in the cases and within the limits set out in section 5.

We ourselves use such data only to provide and protect the Service, as this policy describes.

To carry your traffic, a VPN server necessarily sees your IP address and the addresses of the sites and services you connect to. The server software reads only what it needs to route a connection: its destination, and the domain name and protocol type at the start of the connection (this is how BitTorrent is blocked, as the Terms of Service say). Beyond that we do not examine the content of your traffic, and we do not use any of this to build a profile of you or for advertising.

For each access link the servers keep its device key, the ID of the account it belongs to (for an account created by email the ID contains the email address, for one created through Telegram it is the Telegram ID), its access period, the volume of traffic and the time of the last connection, and some servers also keep the IP addresses the link connects from. We use this to count traffic where a location has a monthly allowance, to notice a link shared among many devices, to find faults and to stop abuse. When you delete a device or your account, we remove it from the VPN servers together with these records.

On some locations a VPN server automatically closes the location to a device for a limited time when the device uploads an unusually large amount of traffic: this is what torrent seeding looks like. This is an abuse-protection measure described in the Terms of Service. The other locations keep working for that device. The server tells our website a shortened hash of the device key, the reason, how much the device uploaded and downloaded over the measured hours, and the time. The website uses the hash to find the account and the device and saves a record in our database (Vercel, Upstash): which device, on which server, when the location was closed and when it opens again. The record is needed to count repeats within 7 days and so that support can explain what happened; it expires by itself 8 days after the last such closure, and when closures repeat, the record of an earlier one is kept for no longer than 15 days. The link between the hash and the account and device is kept for up to 30 days after a closure. The operator receives a message in Telegram: the account ID (which for an account created by email contains the email address), the Telegram name and username if the account has them, the device name, the volumes, the times and the number of repeats; this message stays in the operator’s Telegram chat until the operator deletes it. When you write to support, the record (the device, the location, the start, the end and the number of such closures in 7 days) is part of the summary the assistant receives (section 11). When a device or an account is deleted, these records are not erased at once; they expire by themselves, no later than the periods above. If you think a closure is a mistake, write to support.

The website may tell you about such a closure: by a message in Telegram if Telegram is linked to the account, or, if it is not and the account was created by email, by an email to the account's address (Resend sends the emails). The message names the device, how much it uploaded and downloaded in the measured hours and for how long the location is closed, and says where to write if this is a mistake.

The connection log — a record of who connected, when and to which address — is switched off on our VPN servers: that was the state of every server when we checked on October 5, 2026. The server software keeps a technical error log; a few of its lines, about connections that failed, can contain an IP address or a destination address. We use this log only to find faults and to stop abuse.

On some servers the technical log is kept for at most 7 days; on the others, until it reaches the space set aside for it.

The test servers of our own protocol (in the app their rows are labelled “WataFast protocol”) are an exception. For each session their system log records when it began and ended, how much traffic it carried, why it closed and its technical counters, and with them the first part of the number our site gives the device for this protocol, whether its plan is free or paid, and the kind of network (Wi-Fi, mobile or wired) if the app reports it. By that part of the number we can find a device's sessions, for example when its owner reports a problem. These records contain no IP address and no addresses or names of the sites and services you open. They are kept for at most 7 days; we use them only to find faults in the protocol and to stop abuse.

The table lists every kind of data we keep: where it comes from, why we need it, how long we keep it and who else processes it. The providers are described in section 6.

We do not ask for passport data, document scans, phone numbers, your contacts, precise location or card details.

The ProxysVPN apps connect your device to our VPN servers. In addition to what is described above:

• On first launch the app creates a random install ID. It is not derived from your hardware and carries no information about your device. The app sends it when it downloads your settings, so that one access link works on one device.
• Requests from the app to our website carry the app’s name and version, the operating system (for example, iOS, macOS or Android) and whether the app was installed from the App Store or Google Play — no device model or serial numbers.
• The apps contain no advertising, analytics or crash-reporting code and do not track you across other apps or websites. If you allow your device to share analytics with app developers (on Apple devices) or usage and diagnostics data with Google (on Android), Apple or Google may pass us crash reports under their own rules.
• The app’s technical log stays on your device. It leaves the device only as part of a problem report, and a report goes to us only when you press “Send report” yourself: the app shows you its whole text first (section 3).
• DNS. By default the app resolves site names through the VPN server, by asking Cloudflare (1.1.1.1) or Google Public DNS (8.8.8.8), so these resolvers see the server’s address rather than yours. When Russian sites are routed around the VPN, their names may be resolved directly from your network, by Yandex public DNS or by your system resolver. Where the app offers the choice, you can switch to your system resolver or enter your own.
• Connectivity checks. To find out whether your network works at all, the app may briefly connect to Cloudflare (1.1.1.1) and Google (8.8.8.8); these connections carry no information about your account. The app also checks that our website and servers respond.
• To download your settings, the app contacts our website or, if it is unreachable, one of the website’s reserve addresses (section 7).
• On iPhone and iPad the app registers for silent push on its own, without asking for permission, and after sign-in sends the push token to our website (section 3). Such a push wakes the app in the background with a signed list of our website’s current addresses and shows nothing. The app asks for the notification permission in one case only: when you turn on the mobile data threshold; that notification is made on the device.
• Some functions work on the device only and send us nothing: the offline chat over Bluetooth (device to device, with no server of ours; a message to one person is encrypted for them, and blocking and reporting act on the device), “Hand over to a phone” and “Internet from a neighbour” over the local network (encrypted, and only while you have started them), the month recap, saved to Photos only when you tap the button, the camera, used only to scan a connection QR code, the Safari content blocker with its bundled filter lists and your own rules, and the widgets, Shortcuts and the Apple Watch app, which only show the VPN state and switch it.

The VPN permission you grant lets the app route your device’s traffic through our servers; the app uses it for nothing else.

Proxys Browser for Android is a separate app of ours. Its reader mode, page translation and read aloud work on the phone: the browser does not send the text of a page to us or to anyone else. Pages are translated on the device by Google’s translation library (ML Kit). When a translation needs a language pack, the browser asks you first. Only after you agree does the library download the pack (about 40 MB per language) from Google’s servers and start fetching its own settings from Google. These connections are the library’s own and do not pass through the browser’s protected connection. With them Google receives the IP address your phone connects from, a random identifier the library creates for this installation of the browser, the browser’s name and version, the Android version, the device model, and the phone’s language, region and time zone (section 6). We do not receive this data. Until you agree, the library contacts no one. Clearing the browser’s data removes the identifier and the language packs. Read aloud hands the article’s text to the speech engine installed on your phone and uses only voices that work on the phone itself.

We use data only to:

• provide the Service: create access links, deliver settings, count usage and charge for it;
• answer your requests to support;
• take payments through the provider you choose;
• protect the Service and other users from fraud and abuse;
• tell you about your account, your balance and the state of the Service;
• improve the support assistant, using conversations without the email address, the account ID and images (section 11);
• keep records of payments, answer claims and defend our rights in disputes, including confirming to a bank or a payment provider that a payment was made and the service was used;
• comply with the law;
• send news and offers: in the bot at most once a week (turn them off with the “No more offers” button under such a message or with the /offers command) and occasionally by email, with an unsubscribe link in every letter.

We do not sell data and do not use it for advertising profiles. We may disclose data to anyone other than the service providers and services named in this policy in three cases only. To a court or a public authority: on a binding legal demand that we are obliged to carry out, and only the data it covers. To a bank or a payment provider: when a payment is disputed — information about the payment itself and about the fact that the service was used (the date of registration, top-ups, devices and the time of the last connection), without the addresses of sites and without the content of traffic. To a court and to our lawyers: to the extent needed for a dispute with you or to defend against a claim. We can disclose only what we keep; what that is, is listed in section 3.

The grounds on which we process data: the contract with you (the account, access, payments, support); our legitimate interests (protecting the Service from abuse, records and disputes, website statistics, improving the assistant); your consent where the law requires it (newsletters — you can opt out at any time); and legal obligations.

Our service providers process data only on our instructions, only to the extent their task requires and with protection at least equal to this policy:

• Vercel Inc. (USA): hosting of the website, its API and our bots, and cookie-free visit statistics; it handles every request to the website.
• Upstash, Inc. (USA): our database of account, service, payment and support records.
• Resend, Inc. (USA): sending emails, that is, sign-in codes, service letters and newsletters.
• Cloudflare, Inc. (USA): the DNS of our domains; it receives letters sent to our addresses and forwards them to our mailbox.
• GitHub, Inc. (USA): the private repository where problem reports sent from the apps are kept.
• Hosting companies that rent us servers for the VPN and for the website’s reserve proxy. We do not name them, so as not to make it easier to block our servers. The servers are located in: Austria, Finland, France, Germany, Kazakhstan, Netherlands, Poland, Russia, Sweden, Türkiye, United Kingdom, and United States.

The following services are independent: they receive data because you use them or because the task requires it, and they process it under their own privacy policies:

• Telegram (UAE): our bots, the Mini App and signing in with Telegram; everything you send to the bots passes through Telegram. A conversation with the assistant that is handed to an operator from the chat in the personal account or the Mini App also reaches the operator through Telegram (section 11).
• Payment providers: YooKassa, Cashera, Enot and lava.top (cards and fast payments), NOWPayments and CryptoBot (cryptocurrency). We pass them the amount and an order number. All of them except Cashera also receive your account ID, sometimes inside the order number: for an account created by email the ID contains your email address, for one created through Telegram it is your Telegram ID. YooKassa, Enot and lava.top also receive the email address of your account, if it has one, for the receipt. What you enter on their payment page (card or wallet details) goes to them, not to us.
• OpenRouter, Inc. (USA) and the language-model provider it passes the request to (USA): answers of the support assistant (section 11). They may keep requests under their own terms.
• Yandex (Russia): Yandex Metrika web analytics on the public pages of the website in Russian (section 10).
• DNS resolvers of Cloudflare, Google and Yandex, used by the apps as described in section 4.
• Apple Push Notification service (Apple Inc., USA): carries the silent push to the ProxysVPN app on iPhone and iPad and sees the push token, not your account.
• Google (USA): in Proxys Browser for Android, the language packs and the settings of the page translator. Google receives data only after you agree to download a language pack (section 4).

The website, the database and email run on servers of Vercel, Upstash and Resend in the European Union and the USA. The VPN servers are located in: Austria, Finland, France, Germany, Kazakhstan, Netherlands, Poland, Russia, Sweden, Türkiye, United Kingdom, and United States. Some reserve addresses of the website pass through our own proxy server in Russia, which forwards requests to Vercel. Yandex Metrika processes data in Russia; Telegram and the payment providers process data where they operate.

Data-protection law in these countries may differ from the law of your country. By using the Service you understand that data is processed outside your country, including in the USA. Wherever the data is, we protect it as this policy describes.

The period for each kind of data is in the table in section 3.

When your account is deleted, we remove its devices from the VPN servers and delete the account, its devices, balance and settings from our database at once. What support may still need for an open request (the support chat, the payment history, the traces of your apps) is deleted automatically 7 days later.

A few records stay longer, each for its own reason: a one-way hash of the account ID with the time of deletion (180 days, so that a late payment is not credited to a deleted account); records of refunds (up to 1 year); the promo codes the account has used and the personal offers made to it (up to 1 year, against abuse); records of payment orders (up to 180 days) and of credited payments (up to 90 days), so that a late payment or a refund can be matched; records of requests in the support bot, with the text of their messages (180 days from the last change to the request) and their copies in the support team’s working chat in Telegram (until an operator deletes them); the copy of a conversation with the assistant handed to an operator, in the operator’s chat in Telegram (until the operator deletes it); a record of a removed device whose removal a VPN server has not yet confirmed: the device key and the name of its entry on the server (until the server confirms, 30 days at most, so that the removal is carried through); and a ban from support, if one was imposed. These records carry the account ID, which for an account created by email contains the email address. Other technical records that name the account, such as rate limits and marks against sending a message twice, expire on their own within 180 days at most. Payment providers keep their own records of your payments under their rules.

Copies may remain in backups of our database and of the VPN servers until those backups are deleted; the VPN servers' daily backups are kept for up to 16 days. Backups are used only to restore the Service after a failure. Messages you exchanged with our bots stay in your Telegram until you delete them there.

At any time you can:

• ask what data we hold about you and get a copy: write to support;
• ask us to correct inaccurate data;
• delete your account on the account deletion page or by asking support; this also withdraws your consent to the processing of your data;
• turn off news and offers with the “No more offers” button or the /offers command in the bot, or with the unsubscribe link in an email;
• delete the support chat with the “Clear” button and ask for a human operator instead of the assistant;
• block cookies and analytics in your browser; the website works without them.

If you ask support to delete your account, we do it within 30 days. You can also complain to the data-protection authority of your country.

Before we provide, correct or delete data, we make sure the request comes from the owner of the account: we reply to the account's email or in the same Telegram. We may refuse requests that are repeated without reason or are clearly excessive.

The website sets these cookies of its own:

• “sid” keeps you signed in: 1 hour, or 7 days if you tick “Remember for 7 days”;
• “tg_bind” ties a Telegram sign-in code to your browser for 10 minutes;
• “lang” remembers the language you chose: 1 year;
• “attr” remembers how you found us (section 3): 30 days.

Your browser’s storage also keeps the theme, the language, the random ID for guide votes and the campaign tags of your first visit; in the Telegram Mini App it keeps the sign-in for the current session.

Yandex Metrika runs on the public pages of the website in Russian. It does not run on pages in other languages, on the sign-in and registration pages, in the personal account, in the Telegram Mini App or on device connection pages. Where it runs, it sets its own cookies, records visits, clicks and scrolling and may record a replay of how the page was used (Webvisor). Yandex processes these data in Russia. We use them to see how people find us and how many of them sign up.

Vercel Web Analytics and Speed Insights count visits and measure page speed without cookies; they see the page address, the referring site, the browser, the device type and the country.

You can block these tools in your browser settings or with a content blocker; the website works without them.

Requests in the support chat are answered by an automated assistant: in the personal account on the website, in the Telegram Mini App and in the support bot after you press the ⚡ button. In the support bot the assistant may also answer a request that no operator has answered for a while. To prepare an answer, the text of your request, attached images and, if you have an account, a summary of it are sent to OpenRouter, which passes them to a language-model provider.

The summary includes your balance and currency; your devices with their names, types, plans and terms, the app used on each; when an app last downloaded the settings; whether a location’s monthly traffic allowance is used up; whether the account is linked to Telegram; recent top-ups (date, amount and method); and the result of an automatic connection check. Your email address, Telegram ID and password are not sent, and we do not have card details at all. If a VPN server has recently closed a location to one of your devices because of an unusually large upload, the summary also includes the record of it (section 2).

We keep access links out of what is sent. In the summary each link is replaced by a placeholder; when the assistant gives you the same link on a reserve address because our main address is blocked, our server puts the real link into the answer. In the messages of the conversation, access links and connection lines (such as vless://) that we recognise are replaced by a short note before the text is sent. A key written without a link around it, or visible in an image, is sent as it is, so please do not send access keys to the chat.

The conversation is kept for 180 days from the last message and is then deleted automatically. If you have an account, you see it in the personal account and can delete it earlier with the “Clear” button; otherwise ask support to delete it.

Conversations with the email address, the account ID and attached images removed are used to improve the assistant: to refine its rules and to check that it handles typical cases correctly.

You can ask for a human operator at any time: just say so in the chat. Do not send passwords, confirmation codes or card details to the chat; we never need them.

From the chat in the personal account and in the Telegram Mini App the conversation can be handed to an operator: at your request, or when the assistant itself passes the question to a human. The chat tells you about the handover with a separate line; if the conversation is handed over again within a day, the line may not be repeated. The operator receives in Telegram the last messages of the conversation (up to 12, without images; access links and keys in them are hidden), a short reason for the request, the account ID (which for an account created by email contains the email address), whether the account was created through Telegram or by email and whether Telegram is linked to it, and the language. The operator’s answer appears in the same chat and becomes part of the conversation; we tell you about it in the Telegram bot or by email to the account’s address, and the email contains the text of the answer. Our record of such a request is kept for 14 days from its last change; the copy in the operator’s chat in Telegram stays until the operator deletes it, also after the account is deleted. The “Clear” button does not delete that record or that copy.

Connections between your device and the website, the apps and the VPN servers are encrypted. Passwords are stored only as one-way hashes, access to data is limited to those who run the Service, and we keep the infrastructure up to date.

No transmission over the Internet is completely secure. We are responsible for the security of our own systems. You are responsible for the security of your device, your password and your access links: if the device is compromised or your sign-in details end up with someone else, we cannot prevent that.

We may change this policy. The current revision is always published on this page with its date. We announce material changes — new kinds of data, new recipients, longer retention periods — on the website in advance, and those who have active access or funds on the balance are also told in the Telegram bot or by the account's email. Revision history:

• November 11, 2026: Proxys Browser for Android is now described in the section on the apps: how it shows pages in reader mode, translates them and reads them aloud, and what Google receives once you agree to download a language pack. Google is named among the independent services for the browser’s page translator.
• November 11, 2026: The support bot now keeps the text of the messages in a request in our records, yours and the replies to you, for 180 days from the last change to the request (a new message, closing or reopening); files are not kept, and access links and connection lines that we recognise are replaced by a short note before the text is saved. The term of these records is now stated more exactly: it runs from the last change to the request, not only from the last message.
• November 11, 2026: The section on VPN servers now says that the website may tell you about a location temporarily closed to a device, by a message in Telegram or by an email to the account's address, and what that message contains.
• November 10, 2026: The section on the support assistant now says that access links are not sent to it: the account summary carries a placeholder in place of each link, our server puts the real link into the answer, and access links and connection lines recognised in the messages of the conversation are replaced by a note before the text is sent. The table row on access keys is updated to match.
• November 10, 2026: The section on VPN servers now describes the record of a location temporarily closed to a device because of an unusually large upload (a sign of torrent seeding): what the server tells the website, what is kept and for how long, what the operator receives in Telegram and what the support assistant sees.
• November 10, 2026: The assistant chat in the personal account and in the Telegram Mini App can hand a conversation to an operator. The section on automated processing of support requests and the data table say what the operator receives in Telegram, how long it is kept and how the answer arrives.
• November 6, 2026: In Telegram chats the bot now also looks at photos when mentioned: in the question or in the message replied to (for a video, only its cover frame). The photo goes to the language model only for the answer and is not stored by us. The guest-mode row of the data table says so.
• November 6, 2026: In Telegram chats the bot now also answers general questions when mentioned, including whether a channel post is true; for this the language-model provider searches the web. The guest-mode row of the data table says so.
• November 6, 2026: The data table describes the bot's answers in Telegram chats when it is mentioned (guest mode): what is passed to the language model, the subscription check and how long the short memory of the conversation is kept.
• November 4, 2026: The data table names the push token of the iPhone and iPad app; the section on the apps describes the silent push and the functions that work on the device only; Apple Push Notification service is listed among the independent services.
• November 3, 2026: The data table also names the check of a site you type on the page “Check any site from Russia”: the site name and its result are kept for 24 hours, and the name is sent to the measurement service Globalping.
• November 3, 2026: the data table names the check on the page “Check what opens on your connection”: which sites opened in your browser, counted by day and region without your IP address, and for how long.
• October 13, 2026: the apps can now send us a problem report with a button; the data table and the list of service providers name the report, how long it is kept and where it is kept (GitHub). The VPN section now also says what the test servers of our own protocol record about a session and for how long, and the list of server countries names Austria.
• October 8, 2026: one more record that stays longer is named: the record of a removed device, kept until the VPN server confirms the removal (30 days at most).
• October 5, 2026: the commitment on VPN data is stated more precisely — it names when service providers, the support assistant and public authorities receive data; the policy now says that the connection log on the servers is switched off and gives the periods for technical logs and backups more exactly; Yandex Metrika now runs only on pages in Russian; added the purposes and grounds of processing, the cases of disclosure, the check of who is making a request, and the age requirement.
• October 1, 2026: the section on the apps now also covers the Android app from Google Play.
• September 28, 2026: the policy was rewritten. It now contains the commitment about VPN data, the full table of the data we keep with retention periods, the service providers and the countries where data is processed, a section on the apps, what happens when an account is deleted, and cookies and analytics described as they are.
• September 1, 2026: the section on automated processing of support requests was added.

For any question about your data, write to our support bot @proxysvpn_support_bot or to support@proxysvpn.com.