Privacy Policy
Unfilter VPN Last updated: 24 August 2026
Unfilter VPN is operated by an individual, not a company. Contact for any question or request in this document, including the rights described in section 7: t.me/unfilter_VPN
This policy describes exactly what the service stores. It was written against the source code rather than from a template, and every retention period below is enforced by a scheduled job — not a promise to delete things later.
1. What we do not collect
There is no account beyond a key. Specifically, we do not ask for or store:
- your name, email address, phone number or postal address
- a password (there is none — the key is the only credential)
- payment details (payment is arranged over Telegram and no card data reaches us)
- your browsing history, DNS queries, or the addresses or contents of anything you connect to through the VPN
- analytics or telemetry of any kind
The website sets no cookies and loads no third-party scripts — no analytics, no tag managers, no fonts or assets from other domains. Your access key is held in your browser's sessionStorage, which the browser discards when you close it; it is never written to a cookie and never sent anywhere except to our own API as an Authorization header.
The desktop application contains no analytics or crash reporting. It talks to our API and to VPN servers, and to nothing else.
2. What we store, and why
Your account
| Data | Why | Kept for |
|---|---|---|
| A SHA-256 hash of your key, plus its first 11 characters in clear | To recognise your key without being able to reproduce it, and so support can identify an account from a prefix | Life of the account |
| A label, if you or an operator set one | To tell accounts apart in the admin list | Life of the account |
| Your tier and expiry dates | To decide what you may use | Life of the account |
| Account creation time | Support, and abuse investigation | Life of the account |
| The IP address you created the account from | To rate-limit automated signups | 30 days, then erased |
| When the account was last seen | To identify dormant accounts | Life of the account |
Your key itself is stored only as a hash. This has a consequence we cannot work around and want you to know before you rely on it: nobody, including us, can recover a lost key. It is shown once, at creation. If you lose it, the account is gone.
Your devices
Nothing. There is no device limit and no device registration. We do not generate or store a device identifier, your computer's hostname, or any per-device record. Earlier versions of this service did all three, to count installations against a limit; the limit was removed and the records it existed for were deleted from the database, not merely left unused.
A consequence worth stating plainly: your key works on as many of your own computers as you like, and we have no way to tell them apart.
Web server logs
The web server that fronts both the site and the API writes a conventional access log line for every request: the source IP address, the time, the path, the response code and the user agent. This is the standard log of a web server and it is how the service is operated and debugged.
| Data | Why | Kept for |
|---|---|---|
| Source IP, time, path, status, user agent | Operating and debugging the service; investigating abuse | 14 days, rotated daily, then deleted |
These logs are not joined to accounts. They are the only place a per-request IP address is recorded — the account API itself no longer stores one for authorization checks.
Administrative log
Actions taken by an operator (creating, editing or disabling an account) are recorded with the operator's key prefix, the action, and a timestamp. Kept for 90 days, then deleted.
3. What we can see about your VPN use
Your connection is not routed through the machine that runs this API. The API answers two questions — is this key valid, and which servers may it see — and it is contacted at launch, before a connection, and periodically while connected.
From those requests we can see that a key was active at a particular time. The authorization check itself stores no IP address: the only reason it used to read one was to stamp it on a device record, and there are no device records any more. The request still passes through our web server, whose access log holds the source IP for 14 days as described above. We do not receive, and therefore cannot store, which server you chose, when you connected, how long for, or how much data you moved.
Servers reachability is measured by our own infrastructure connecting to the VPN servers directly. Your client also measures speed itself, locally; those measurements stay on your computer and are never sent to us.
Third-party infrastructure. The VPN exit servers are not operated by us. We
cannot inspect or make commitments about what an operator of a server you connect
through may record. Please do not read anything in this policy as a statement about
their systems — it describes only ours.
4. Where the data is
One server, in the European Union, which we administer. The database is not shared with, sold to, or processed by any third party. There is no advertising network, no data broker and no affiliate tracking involved in this service.
5. Retention, in one place
| Data | Kept for |
|---|---|
| The signup IP address | 30 days |
| Web server access log | 14 days |
| Administrative log | 90 days |
| Account record | Until you ask us to delete it, or the account is deleted |
Deletion is performed by a job that runs daily. Our own admin tooling reports whether any data is currently older than the periods above, so this is something we check rather than assume.
6. Legal basis (GDPR Article 6)
- Contract (Art. 6(1)(b)) — the account record and its tier. Without these the service cannot be provided at all.
- Legitimate interests (Art. 6(1)(f)) — IP addresses, for rate-limiting signups, operating the web server, and investigating abuse. We have limited this to the minimum we could find a use for, and expire it within 30 days.
We do not rely on consent for anything, because we do not do anything that would require it: no marketing, no profiling, no automated decision-making, no advertising.
7. Your rights
Under the GDPR you may ask us to:
- confirm what we hold about you, and give you a copy (Art. 15)
- correct it (Art. 16)
- delete it (Art. 17) — we will delete the account and its log entries. Note that this makes the key permanently unusable.
- restrict or object to how we use it (Art. 18, 21)
- export it in a machine-readable form (Art. 20)
Contact t.me/unfilter_VPN with your key prefix — the first 11 characters, e.g. uv_AbCdEfGh. Do not send us your whole key; we do not need it to identify your account, and anyone who has it can use the account.
We will respond within 30 days. There is no charge.
One limit worth stating honestly: because we hold no name, email or address, we cannot verify that a requester is the account holder by any means other than knowledge of the key prefix. This protects you from someone else deleting your account, but it also means we cannot help if you have lost the key entirely.
8. Security
- Keys are stored on our server as SHA-256 hashes, so a copy of the database does not yield working accounts.
- All traffic to the API is over HTTPS.
- The API is not reachable from the internet except through the reverse proxy, and administrative endpoints re-check the caller's role on every request.
- On your own computer, your key is stored in a file readable only by your user account (mode
0600on Linux; your user's private application-data folder on Windows). It is not encrypted at rest — anyone with administrator access to your machine, or with your logged-in session, can read it. Protect your computer accordingly. - The application's local control interface is bound to
127.0.0.1and requires a token that is generated fresh on every launch, so another program on your machine cannot drive it or read your key out of it.
If you believe you have found a security problem, please report it to t.me/unfilter_VPN.
9. Children
This service is not directed at children and we do not knowingly create accounts for them. We hold no age information, and cannot, because we hold no personal information.
10. Changes
If this policy changes materially, the updated version is published here with a new date. Because we have no email address for you, we cannot notify you individually — please check this page if it matters to you.
11. Complaints
If you are in the EU or UK and are unhappy with how we have handled your data, you may complain to your national data protection authority. We would rather you told us first, at t.me/unfilter_VPN.