🏠 Izba VPN

Русский

Privacy Policy

Revision of 14 October 2026

This is a translation for convenience. If it differs from the Russian version, the Russian version prevails.

This Policy describes what data the Izba VPN browser extension for Google Chrome (the "Extension") processes, why it is needed, how it is stored and with whom it is shared. By using the Extension, the user agrees to this Policy and the Terms of Use.

1. Purpose of the Extension

The Extension's single purpose is to route Chrome browser traffic through an HTTPS proxy server in the Russian Federation so that Russian websites can be accessed from abroad. The Extension does not read or modify the content of web pages and does not inject code into them.

2. Data we process

• Email address — to sign in to the account. The address is confirmed with a 6-digit code sent by email. The password is stored on the server only as a cryptographic hash.
• Telegram data — only if the user chooses to sign in with Telegram: the user ID, username and name provided by Telegram.
• Installation ID — a random identifier generated by the Extension itself and kept in browser storage (chrome.storage, including Chrome sync storage). It is used to limit free trials.
• IP address when the Extension contacts the service API — to prevent trial abuse. It is stored in truncated form, down to the subnet.
• Device record: device ID, platform ("Chrome") and time of last activity.
• Subscription status of the account in aggregate form (whether a subscription is active and until what date).

3. Data stored only on the device

• Access tokens (access and refresh) and Extension settings, including the interface language, are stored locally in browser storage (chrome.storage).
• Diagnostic log — connection events, error codes and hostnames of requests that failed. The log is stored only on the user's device and leaves it only if the user copies it and sends it to support themselves.

4. What we do not collect

We do not collect or store browsing history, page content, traffic content or DNS queries. The proxy server does not log visited websites.

5. Extension permissions

• proxy — to route browser traffic through the server;
• webRequest and webRequestAuthProvider — to supply proxy credentials automatically and to detect proxy errors;
• privacy — to change the WebRTC policy while connected so that the real IP address does not leak past the proxy; the original setting is restored on disconnect;
• storage — to store settings, session data and the selected language;
• alarms — for keepalive and periodic checks;
• access to all sites (<all_urls>) — required for the proxy to work on any website. The Extension does not use this access to read or modify page content.

6. How we use data

• providing access to the proxy server and managing the subscription;
• signing in to the account and sending confirmation codes;
• preventing abuse, including repeated free trials;
• user support and fixing errors.

The use of information received by the Extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the Extension's single purpose described in section 1; it is not used for advertising, not sold and not transferred to third parties except as described in section 7.

7. Who receives data

Data is shared only to the extent necessary for the Extension to work:

• hosting providers whose servers run the API and the proxy server;
• email service (Resend) — to send confirmation codes by email;
• Telegram — only if the user chooses to sign in with Telegram;
• payment agent (Platega) — to process payments. Bank card data is processed by the payment agent; we do not receive it.

We do not sell data, do not show ads and do not use analytics or trackers in the Extension. Data may be disclosed upon a lawful request from competent authorities.

8. Storage and security

8.1. Data is stored on secured servers with restricted access. Passwords are stored only as a hash; connections to the API and the proxy server are encrypted.

8.2. Data is kept for as long as the user has an account. Payment records may be kept longer where required for accounting.

9. User rights and data deletion

9.1. The user may request information about their data, its correction or deletion of the account by contacting support. After the account is deleted, access to the Extension ends.

9.2. Signing out removes the access tokens from the device. Uninstalling the Extension from the browser removes all of its local data.

10. Changes to this Policy

This Policy may be updated. The new revision is published on this page and takes effect upon publication.

11. Contact

Support: @izbavpn_support on Telegram.