Privacy Policy

Only what the service cannot run without. For signing in: your email address, name, a hashed password and the site language; if you sign in with Telegram or use the bot, your Telegram id, username, language and the time you last used the bot. To protect signing in: the IP address and user agent of the browser or app behind each session; a session is deleted when you sign out, and an unused one stops working after 30 days. For the subscription: the plan, its expiry, your payments, the promo codes and discounts you applied, the gift codes you bought and their status and, if you were invited or invited someone, the link between those accounts, so the bonus days can be credited. So that the free day and promo codes do not go to one person twice: hashes of your email address and Telegram id. For connecting: your routing settings (whether Russian sites open directly, whether ads are blocked), and the platform and time of the last subscription refresh. For devices: the device identifier (HWID) your VPN app sends (unrelated to any advertising ID), the device model, platform, system version and app name; the time each device was last active, which the VPN node reports once a minute; and for WireGuard configs, the country you picked. For support: the messages you send to support through the Telegram bot.

We keep no logs of your traffic: no connection history, visited addresses, DNS queries or connection contents. For each device we keep only the time it was last active — a single value that is overwritten, not a log. Nodes also count transferred bytes to show your usage in the app. The web server keeps a technical log of requests to the site, the API and the bot: the IP address in it is truncated — an IPv4 address keeps its first two numbers of four, an IPv6 address its first two groups — one-time codes and tokens are stripped from page addresses, and the app’s requests to your subscription link are not logged at all. The log is capped in size and overwritten as it fills.

Payments are handled by YooKassa. You enter the card number, expiry date and CVC on the YooKassa page — we never receive or store them. Our side keeps the amount, date and status of each payment, its YooKassa id, what was paid for (a plan, extra device places or a gift code), the promo code and discount if one applied, and, if a payment method is saved for auto-renewal, its YooKassa id and a label for your account page: the card type and last four digits, or the name of another method.

Account data is stored on servers in Russia. Passwords are kept as irreversible hashes. A device record is kept while the device is in your list, and you can remove it in your account at any time. When a subscription ends, devices stay in the list so nothing has to be set up again after you pay — except WireGuard configs over the base limit, which are deleted. While the account exists we keep the record of your consents: what you agreed to (personal data processing, discounts and offers), the version of the text, and when and where you gave or withdrew it — the proof that consent was given. We also keep a log of the service notices already sent, so the same reminder does not arrive twice, and an audit log of what an administrator did with the account (extending access, refunds, messages — without the text of the messages). Expired sessions, with their IP address and browser data, are deleted 7 days after they expire; verification codes and one-time sign-in links, a day after. Deleting your account deletes its profile, sessions, devices, configs, subscription link, settings, Telegram link, consent records and notice log. What stays, no longer tied to the account: payment records (amount, plan, date, promo code, the YooKassa ids of the payment and the payment method) — for accounting and in case of a refund; hashes of your email address and Telegram id if you used the free day or promo codes — the address cannot be read from them, but it is recognised if it signs up again, so the free day and promo codes are not given twice; gift codes you bought, which may already be in someone else’s hands; and the entries of the administrator audit log. Deleted data leaves the database backups as they rotate — within 30 days at most.

We do not sell your data. Part of it is processed by services the product cannot run without: YooKassa, to process payments; the email provider, to deliver emails to your address; and Telegram, if you sign in with Telegram or use the bot. Telegram’s requests to our bot — your messages to the bot and your Telegram profile data — pass through Cloudflare’s network, which forwards them to our server. If you write to support through the bot, your message and its attachments are forwarded to the support chat in Telegram together with your name, username and Telegram id, your account’s email address, language, device count and subscription state; the link between a message in the support chat and your chat is kept for 90 days so the answer can reach you, and the messages themselves stay in the support chat’s history. The same chat receives notices of payments, refunds and failed charges with the account’s email address and Telegram details. Staff of the service with access to the admin panel can see account data in order to help users. When routing is on in INCY, the app looks up site addresses at public DNS resolvers: for sites opened through the VPN, at Cloudflare — or at AdGuard DNS if you turned ad blocking on — and those lookups go through our server, not from your address; for Russian sites, at Yandex DNS, directly from your device. On the server status page, and only when you press “Check connection”, your browser asks ipify (api.ipify.org) for its IP address: ipify receives nothing but that request and the address it comes from, and we compare the address with our servers’ addresses without storing it. There are no other recipients, except where disclosure is explicitly required by law.

You can request a copy of your data, correct it, withdraw your consent to its processing, or delete your account entirely. Email us at the address below — we answer within 10 working days of receiving the request. If more time is needed, the term can be extended by no more than 5 working days: we will tell you so in advance and explain why.

The service is not intended for anyone under 14, and we do not knowingly collect their data. Users aged 14 to 18 use and pay for the service with the consent of a parent or legal guardian.

If this policy changes, the date at the top of the page is updated. Material changes are additionally announced by email to the address on your account or through the Telegram bot.

For questions about personal data and this policy, write to the address below.