Privacy policy
Veto holds an account number, its plan, a paid until date and one key for each device. It holds no name, no email address and no record of what you do online.
This page lists every item Veto holds, why, where it lives, for how long and who else gets it. It keeps six things apart: this website, the account system, the New York server, the Pro locations, the Windows app and payment.
- Last updated
- 15 November 2026
- Covers
- This website, the account system, the VPN servers, the Windows app and payment
- Run by
- Outline Technologies LLC
- Postal address
- 30 N Gould St, Ste R, Sheridan, WY 82801, United States
- Contact
- info@vetovpn.com
Written from the running systems.
Every table on this page was written from the systems as they run: the website's code, the account database, the VPN server in New York, the Windows app's code and the payment code. Each line was checked on them on 15 November 2026.
A rule we hold ourselves to: the service never records more than this page says. If something new has to be kept, this page changes first, and the change is listed at the bottom with its date.
What this website keeps.
Checked on the live site on 15 November 2026.
| What | Why | Where it lives | How long | Shared with |
|---|---|---|---|---|
| Your choice of the dark or the light look | So the site opens the way you left it | In your own browser | Until you clear your browser data | Nobody. It is never sent to us |
| A mark that this browser has been here before, and a mark for the current visit | So the team gets one note per visit, saying new or returning | In your own browser | The first until you clear your browser data; the second until you close the tab | Only the words new or returning go into the note |
| Your address and rough place, shown on the home page | To show you what any site can read about you | Read from your request and sent straight back to your browser | Not kept | Nobody |
| Counts of requests from your address, one count for each kind of request | To stop guessing of account numbers and bulk use | In the web server's memory | Until the window of that limit ends: 1 minute, 10 minutes or 1 hour | Nobody |
| One line in the error log when a request fails | To find and fix faults | A log file on the web server | 14 days, then the server's log rotation deletes it | Nobody |
| A short note to the Veto team for each page you open and each action listed below, with your address and its internet provider, the place it points to, your device, browser and language | So the team can see that the site and the service are used, and by whom | Sent to the team's chat through a messaging service. Not stored on our server | Kept in the team's chat. No period has been set | The messaging service that carries it |
| Email you send us | To answer you | In our mailbox, which is hosted by a mail provider | No period has been set | Nobody |
The limits on requests
With no password, a number is the only proof that an account is yours, so someone could try to guess numbers. To stop that, and to stop one machine from making accounts in bulk, the server counts requests per address. Each count lives in memory and is dropped when its window ends.
| What you do | Limit for one address |
|---|---|
| Open an account in the panel | 10 tries in 10 minutes |
| Make a new account number | 5 an hour |
| Add or remove a device | 30 an hour |
| Ask for a Pro location | 60 an hour |
| Open the payment page | 10 an hour |
| Stop or restart the renewal | 10 in 10 minutes |
| Delete an account | 5 an hour |
| Page view notes | 40 a minute. Past that, no note is sent |
The notes to the team
The Veto team gets a short note when something happens on the site or in the account system. Unless the table says without who, a note holds who it came from: your address and the internet provider it belongs to, the city, region and country that address points to, your system and browser, such as Windows 10/11 and Chrome, and your language. The provider is found on our own server in a public list of address blocks, so your address is not sent anywhere for it. A note never holds an account number or a key.
| When | What the note says |
|---|---|
| A visit starts | Where you came from, the first page, any campaign tags, the width of your window, your time zone, new or returning, and who it came from, as above |
| An account number is made | That one was made |
| A device is added or removed | The plan, the server, and whether it took the place of an older device |
| The account panel is used | Whether the number was found, and its plan |
| A limit is reached | Which limit |
| The payment page is opened | Monthly or yearly |
| A payment, renewal, refund or dispute arrives | The kind and the amount, without who |
| A renewal is stopped or restarted, or an account is deleted | Which one |
| A Pro location fails to connect | The city, without who |
The error log, in plain words
The web server writes no line for a normal visit. It does write one when a request fails, for example when someone asks for a file that does not exist. That line holds the time, what went wrong, the address that was asked for and the address the request arrived from.
For a visitor, that last address belongs to the delivery network and not to you, because every visit passes through that network before it reaches our server. The log is rotated daily and a file is deleted after 14 days.
The account panel
The account panel takes a 15 digit number and shows the plan, the paid until date and the number of devices. The number travels in the body of an encrypted request. It is not put in the address bar, not saved in your browser by the site and not written to any log.
What we receive whether we want it or not.
Any site on the internet receives some things by the nature of how the internet works. Here is each one and what happens to it.
- The delivery network. This site sits behind a content delivery network, and every visit passes through it first. Like any such network, it sees your address, the page you ask for and the details your browser sends, and it keeps its own records under its own terms. It passes your address and a rough place on to our server with each request. We use them for three things: the panel on the home page that shows you your own address, the limits on requests, and the notes to the team.
- Reports of failed requests. The delivery network asks your browser to tell it when a request to this site fails. Those reports go to the network, not to our server.
- The web server. It handles your request and writes nothing about it, unless the request fails. Then it writes the one line described above.
- The health check. Every 5 minutes the server checks that the site answers. If it does not, the team gets an alert. The alert says the site is down and holds nothing about any visitor.
- Email. If you write to us, we get what every email carries: your address, your name if your mail app adds it, your words and the technical headers. Nothing is added to a list.
- Payment messages. When you pay, the payment company sends the site a message about it. What that message holds and what is kept from it is in Part 6.
What the account system keeps.
The whole record, item by item. The account database is hosted by a database company in Stockholm, Sweden, and only the website's server can reach it.
| What | Why | Where it lives | How long | Shared with |
|---|---|---|---|---|
| The 15 digit account number | It is the account | The account database | Until you delete the account | Nobody |
| The plan, Free or Pro, and a paid until date | So Pro starts and ends on the right day | The account database | Until you delete the account | Nobody |
| A payment reference: a random code made with the account | It is the only thing the payment company is told about the account | The account database | Until you delete the account | The payment company |
| The payment company's customer and subscription codes | To stop or restart the renewal with the account number alone | The account database | The subscription code until the subscription ends; the customer code until you delete the account | Nobody. They are the payment company's own codes |
| One entry for each device: its public key, its server and its place on that server | So the server lets the device in | The account database | Until the device is removed or replaced, or the account is deleted | Nobody |
| For each Pro device, the code of its Pro login | To delete that login when it is no longer needed | The account database | Until the device is removed or the account leaves Pro | Nobody |
| One line for each payment event: the payment company's event code, the payment reference, the kind, the amount and the time | So each payment is applied once, and for the books | The account database | No period has been set | Nobody |
What is missing on purpose
The record has no date the account was made, no date it was last used and no field for a name, an email or a phone number. The device entries have no name and no type of device, just a key, a place on a server and an order number that shows which entry is oldest.
The free plan holds one device at a time and Pro holds three. When a new device would go over that, the oldest entry is deleted and the new one takes its place.
Deleting the account
Open the account panel with the number and choose Delete this account. In this order: a renewing Pro plan is ended so no further charge can be made, each device is taken off the servers, each Pro login is deleted, and the account record is deleted. It happens at once and cannot be undone.
What stays: the payment lines in the table above, which hold a payment reference and no number, so nothing ties them to the account once it is gone, and the payment company's own record of what you paid, which its own policy covers.
What the New York server keeps.
The free plan runs on it, and Pro accounts can use it too. Checked on the server on 15 November 2026.
| What | Why | Where it lives | How long | Shared with |
|---|---|---|---|---|
| The public key and tunnel address of each device on that server | So the server lets your device in and can tell it from another | In the server's memory, sent to it by the account system | Until the device is removed. A restart clears it, and the server asks for the list again | Nobody |
| The address you connect from, the time of the last handshake and a byte count | The server needs them to send your packets back to you | In the server's memory | Until the device is removed or the server restarts | Nobody |
| Short counts per tunnel address for the abuse limits | To stop floods, scans and password guessing from inside the tunnel | In the server's memory | 1 to 2 minutes after the last packet that counted | Nobody |
| Totals of packets stopped by each abuse rule, for the whole server | To see abuse such as mail spam without looking at any one user | In the server's memory. An alarm sends the team the totals when they jump | Until the server restarts | Nobody |
| The sites you open, your name lookups, the times you connect | Not collected | Nowhere | Never recorded | Nobody |
Why the server holds your address at all
A tunnel has two ends. To send a packet back to you, the server has to know where you are, so it holds the address you connected from, the time your device last shook hands with it and a running count of bytes. Every VPN does this, because a tunnel cannot work without it.
On Veto these three things stay in memory. They are never written to a disk, they are not copied anywhere, and they are gone when the device is removed or the server restarts.
How the never lines were checked
- The firewall rules were read in full. None of them writes a log, and the counters hold totals for the whole server.
- The resolver that answers name lookups has its query log switched off.
- The tunnel software keeps no history. It holds the current state of each device and nothing older.
- The program that gives the server its list of devices keeps the list in memory and writes nothing to the disk.
The tests behind this are listed on the home page. One of our guides shows what each side of the tunnel can read during a page load.
What the Pro locations hold.
Pro adds 95 servers in 55 countries. A Pro device reaches them with a login of its own, kept apart from the account.
| What | Why | Where it lives | How long | Shared with |
|---|---|---|---|---|
| A random login for each Pro device, made by Veto | So a Pro location lets the device in | On the Pro network, and its code in the account database | Until the device is removed or the account leaves Pro. Then it is deleted | No one outside the Pro network |
| The key for that login | It is the device's key on the Pro network | On the Pro network, and on your PC while connected | Until the login is deleted | No one outside the Pro network |
A login of its own for each device
When a Pro device first asks for a Pro location, Veto makes a login for that device with a random name and a random password, and the Pro network makes the key for it. The account number, the payment details and anything else from the account record never reach a Pro location.
Each login is deleted when its device is removed, when the account leaves Pro or when you delete the account.
While you are connected
Like every VPN server, a Pro server has to know the address you connect from while you are connected, so it can send your packets back to you. The app sends your name lookups through the tunnel to the location's own resolver, and it blocks IPv6 on Pro locations so that nothing can slip around the tunnel.
What the Windows app keeps on your PC.
Read from the app's code, version 1.0.1. Nothing in this table leaves your PC except the public half of the device key.
| What | Why | Where it lives | How long | Shared with |
|---|---|---|---|---|
| The account number | So the app connects without asking again | %APPDATA%\Veto\account.json, in your Windows profile | Until you choose Take the number off this PC in the app, or delete the file. Removing the app leaves it in place | Nobody |
| Your settings: Open with Windows, Connect on open and the location you chose | So the app opens the way you left it | %APPDATA%\Veto\settings.json | Until you delete the file. Removing the app leaves it in place | Nobody |
| The device's own private key | It lets this PC into the tunnel. It is made on the PC and never leaves it | C:\ProgramData\Veto\device.key, readable only by Windows itself and administrators | Until the app is removed | Nobody |
| The tunnel settings, including the Pro key when you use a Pro location | The tunnel service of Windows reads them | C:\ProgramData\Veto\veto.conf | Deleted when you disconnect | Nobody |
| A start entry, only while Open with Windows is on | So Windows opens Veto when you sign in | Your Windows profile's list of programs to run at sign in | Until you switch the setting off or remove the app | Nobody |
Who the app talks to
Two places: vetovpn.com, to get the settings for a server and to check that the tunnel works, and the VPN server you connect to. It carries no ads, no trackers, no analytics and no crash reports, so it reports nothing about how you use it.
The checks it runs after each connection ask vetovpn.com which address it sees. That request travels through the tunnel, and the site keeps no record of it.
Removing the app
Removing Veto in the Windows settings stops the tunnel, removes both of its services and deletes the folder C:\ProgramData\Veto with the device key in it. It leaves your account number and settings in %APPDATA%\Veto, so a new install can use the same account. Delete that folder too if you want nothing left.
What happens to your payment details.
Pro is paid on a page hosted by a payment company. Your card never reaches Veto.
- What the payment page asks for. Your card details and an email address for receipts, and it may ask for the name on the card, a country and a postal code. The payment company keeps these under its own privacy policy, and it sends the receipts.
- What the payment company is told about you. A random payment reference, the plan and whether it is monthly or yearly. Never the account number.
- What comes back to Veto.A message that a payment was made for that reference, with the amount, the paid until date and the payment company's customer and subscription codes. The message can also carry the email you gave the payment company. Veto's code reads the reference, the codes, the amount and the dates, and writes nothing else anywhere.
- What is kept. The codes on the account record and one line for each payment event, as listed in Part 2.
- Stopping the renewal. The account panel stops or restarts the renewal with the number alone. Veto asks the payment company to change the subscription and keeps nothing new.
Eight things Veto does not do, and how each was checked.
A privacy page is easy to write and hard to trust. So each line in this table was checked on 15 November 2026 before it was written, and the second column says how.
What loads from this site
Every page is built from files on vetovpn.com: the page, its styles, a few small scripts, two fonts and the images. Nothing is loaded from another host.
The server also sends a content policy with every page. It tells your browser to refuse scripts, styles, fonts and images from anywhere else, so a mistake on our side could not quietly add one.
| We do not do this | How it was checked |
|---|---|
| No cookies | The answer of every page was read. None of them sets a cookie. |
| No tracking scripts from other companies, and no ads | The source of every page names no host other than this site, and a recording of everything a browser loads showed requests to this site only. |
| No account number or key in any note | The code that writes the notes was read: it never uses the account number or a key. |
| No note for a VPN connection | The code that hands out Pro locations was read: it sends a note only when a location fails, naming the city and nothing else. |
| No email, name or password for an account | There is no sign up form anywhere. The panel and the app take a number only. |
| No chat tool, no contact form, no newsletter | None is on any page. Contact is by email, started by you. |
| No sale or sharing of data | There is no data set to sell. The tables on this page are the whole of it. |
| No analytics or crash reports in the app | The app's code was read: it talks to vetovpn.com and to the VPN server it connects to, and to nothing else. |
On a shared computer
Your choice of look, and the mark that the browser has been here before, stay in that browser until its data is cleared. The account panel does not save the number you type, and it asks the browser not to remember it. The Windows app keeps the number in your own Windows profile, so another person who signs in to Windows with a different profile does not see it. Anyone who uses your profile can open the app.
Links that leave the site
No page on this site links to another site today. If that changes, each outside link will open in a new tab, and this section will say where the links go.
If an authority asks us for data
We can only give what exists: the account record in Part 2. A name, a browsing history or a list of connections cannot be handed over, because none is kept. The payment company holds the card and the email of a paying customer, and answers requests for those under its own rules. No request had been received as of 15 November 2026.
Seeing what we hold about you
Open the account panel with your number: it shows the plan, the paid until date and the devices, which is the whole record apart from the codes. You can also write to info@vetovpn.com with the number. An email shows that number to your mail provider and to ours, so weigh that before you send it.
When this page changes
The date at the top is set by hand each time the text changes, and each change is listed below with its date. If a change means more is kept than before, it is made on this page before it is made on the servers.
Changes so far
- 15 November 2026. First version, written from the running website, account system, VPN server, Windows app and payment code.
Privacy questions, answered directly.
Does VetoVPN keep logs of what I do?
No. Veto keeps no record of the sites you open, your name lookups or the times you connect. On the New York server this was checked on 15 November 2026: no firewall rule writes a log and the resolver's query log is off.
What does VetoVPN know about me?
An account number, its plan and a paid until date, plus one public key for each device. There is no name, email address, phone number or password, because the sign up never asks for them.
Does this website use cookies?
No. No page on vetovpn.com sets a cookie. Your browser keeps three small things for the site: your choice of the dark or the light look, a mark that it has been here before, and a mark for the current visit, which goes when you close the tab.
Can VetoVPN see my address?
While you are connected, yes. The server holds the address you connect from in its memory, because it has to send your packets back to you. It is not written to a disk, and it is gone when the device is removed or the server restarts.
Is my card stored by VetoVPN?
No. A payment company runs the checkout and holds the card and the email you give it. Veto is told that a payment was made for a random payment reference, and puts a paid until date on the account that holds that reference.
How do I delete my account?
Open the account panel with your number and choose Delete this account. The renewal ends, the devices are taken off the servers, the Pro logins are deleted and the account record goes, at once. It cannot be undone.
What would VetoVPN hand over if ordered to?
The account record: the number, the plan, the paid until date, the device keys and the payment codes. There is no browsing history, connection list or name to hand over. No request from any authority had been received as of 15 November 2026.
What does a Pro location learn about me?
A random login made for your device and the key that goes with it, never your account number. While you are connected it also knows the address you connect from, as every VPN server must.