In effect from 6 August 2026

No-logs policy

We keep no record of what you do through the tunnel. Not a shortened record, not an anonymised one, not one held briefly and discarded. This page says exactly what that covers, and — just as importantly — what it does not.

1. What is never recorded

None of the following is written to disk, held in a database, or retained anywhere:

• Websites, services or IP addresses you connect to
• DNS queries you make
• The contents of your traffic, in any form
• Your originating IP address
• The IP address we assign you
• Connection or disconnection timestamps
• Session duration
• Per-session, per-server or timestamped data volume — see §3 for the one number we do count
• Which servers or countries you use
• Your device, operating system or client version tied to a session

There is no exception list. The above is not "not normally recorded" or "recorded only for troubleshooting". It is not recorded.

2. How that is possible

A VPN server has to know where to send your packets while it is sending them. That is unavoidable physics, not a policy choice. The distinction is between handling data in memory for as long as a connection lasts and keeping it afterwards. We handle; we do not keep.

• Servers write no session data to persistent storage. There is no log file to rotate, archive, seize or subpoena, because none is created.
• Users share exit IP addresses. An outbound connection cannot be traced back to one account by IP alone — the address you appear from is the same address many other people appear from.
• Authentication is separated from routing. The system that decides whether your subscription is valid is not the system that carries your traffic, and neither one holds both halves of the picture.

3. What does exist

Saying "we log nothing" and leaving it there would be neat, and it would be a lie. We run a business, and a business leaves records. None of these describe your activity, but you should know they exist:

• Your account — an identifier, a hashed password, your plan, and its expiry date. An email address only if you chose to give one; it is optional.
• Payment records — that a payment succeeded, when, for how much, and a processor reference. Required by tax law. We never see your card number.
• Support conversations — if you write to us, that thread exists until we delete it.
• One data-volume counter — a single cumulative figure per account: how many bytes it has moved in the current billing period. It exists because the refund guarantee is conditioned on it. See directly below.

Why a byte counter is not an activity log

Counting is not recording, and the difference is not a technicality. The counter knows that your account has moved 4.2 GB. It does not know — and cannot be made to say — where any of it went, when you moved it, which server carried it, or what was inside. Every byte increments the same integer, and the integer is all that survives. Hand that number to anyone and they can reconstruct exactly nothing about what you did.

We would rather tell you the counter exists than let you find it in the terms of service. It is the one measurement we take, it is a quantity and not a description, and it is covered by the same rule as everything else here: it is never linked to activity, because there is no activity record to link it to.

All of this is covered in detail by the privacy policy. The line we draw is simple: we keep what is needed to sell you a subscription, and nothing at all about what you do with it.

4. When someone asks for your data

We respond to legally valid demands from authorities with jurisdiction over us. We challenge demands that are overbroad or improperly served. We tell you when we are permitted to.

But the honest answer is that this section matters less than it sounds. A demand can only extract what exists. For your VPN activity, we can confirm that an account exists and that it has paid — and that is the end of the list.

5. Where we are, and what that means

AmosVPN Single Member Private Company is established in Greece, in the European Union. That has a real upside: the GDPR gives you enforceable rights over your data, and an EU company cannot be served with a secret order compelling it to lie to you about this page.

It also means we are subject to EU and Greek law on communications data. Our position is that we hold nothing responsive to a traffic-data demand, because we do not create the data in the first place.

6. Independent verification

This policy has not yet been independently audited. We would rather say that plainly than imply an assurance we have not earned. Any VPN can write a page like this one; the only thing that turns it from a claim into a fact is an auditor with access to the systems. When we have commissioned one, the report will be linked here — and if you are reading this sentence, it has not happened yet.

7. Changes

If this policy ever changes in substance, the date at the top changes with it, and we will say what changed. A no-logs policy that quietly weakens is not a policy.

8. Contact

Ask us anything about this page — including the parts you think are too good to be true: [email protected].