Logging Policy
What we log and why
Last updated: 21 November 2026
This page lists what our VPN servers and our backend record when you use OrbVPN, why we record it, and how long it is kept. We do not record the content of your traffic. We do record connection details, including your IP address, as described below.
1. On our VPN servers
Each VPN server writes an operating log. For each connection, and for each refused connection attempt, a line in this log can contain:
- Your IP address and port, as the server sees them
- The destination of the connection: an IP address or domain name, and a port
- Your account e-mail address (in bridge mode, your account number)
- The date and time
The log also records each request to connect or disconnect, with your account number and e-mail address.
When you use Smart DNS, the server's log can also contain the IP address a DNS query came from and the domain name it asked for, and, for sites reached through Smart DNS, your IP address and the domain of each connection.
Purpose: to operate the service and protect it, for example to find faults and to detect abuse and attacks.
Storage: the log stays on the server's disk. It is rotated automatically by size: when the log files reach a set size, the oldest lines are deleted. How long a line stays therefore depends on how busy the server is, so we do not promise a fixed retention period. The log is also deleted when the server software is reinstalled.
2. What the servers send to our backend
The servers report the following to our backend:
- Connection records: when a connection starts and ends, your account, the server, the protocol, your IP address as the server sees it, the address assigned to you inside the VPN, the start and end time, and the amount of data sent and received.
- Failed connection attempts, for example a sign-in with an unknown or expired key: the protocol, the type of error and the IP address the attempt came from. The backend sends that address to ip-api, an outside geolocation service, to look up its country and network operator, and stores those, not the address.
- Usage counters: the amount of data each account has used, for daily data allowances and plan limits.
- Server health: load, the number of active connections and total traffic.
- Shared connection links: for each connection key (the identity your app or connection link uses), the server counts in its memory how many different client networks use it within a short time window. A network is the range of an address: the first three numbers of an IPv4 address, the first 48 bits of an IPv6 address. When the count goes above what the plan allows, the server reports the number of networks, not the networks or the addresses. We use this to detect connection links shared with others; such a link may be replaced or paused.
- When switched on: counts of incoming connection attempts per client network, with the network shortened to a range of addresses (never a full address), so that we can see which networks can reach the server.
3. What our backend keeps
Our backend keeps these categories of data:
| Data | Purpose | How long |
|---|---|---|
| Account: email address, password (stored as a hash), plan and settings | Providing your account and plan | No fixed period |
| Devices and sign-ins: device name, model, operating system and app version; the IP address and approximate location of each sign-in, and whether it succeeded | Enforcing the device limit and protecting your account | No fixed period |
| Payments: plan, amount, date, payment provider and the provider's reference. Card numbers are handled by the payment provider, not stored by us. | Billing, refunds, fraud prevention and accounting obligations | No fixed period |
| Connection records from the servers (section 2), including your IP address | Operating the service, enforcing plan limits, handling abuse and answering support requests | No fixed period |
| Connection telemetry from the app: platform, app version, protocol, disguise profile, transport, server, session ID, whether the attempt succeeded, how long it took, error category, country, network operator, a one-way network fingerprint, a one-way fingerprint of the DNS resolver, a label for the type of blocking detected, the bridge or CDN domain used (if any) and the approximate time of day; it may be linked to your account when you are signed in | Choosing connection methods that work on your network (Privacy Policy §1.3) | No fixed period |
| Daily usage totals: data used per account per day | Daily data allowances and plan limits | 40 days |
| Reports that a connection key was used from more networks than its plan allows (counts only, no addresses) | Detecting connection links shared with others | 45 days |
| Actions on a connection key: replacement, pause, or the day's data allowance reached, with their dates | Carrying out these checks and answering support requests | 90 days; longer while the action is still in force |
| Request logs: when the app or the website calls our API, the time, the IP address the request came from (and any forwarding addresses), the function called with its parameters (sensitive values removed), the result, the size and duration of the request, the referring page and the app or browser identifier | Running and securing the API and finding faults | No fixed period |
Where our systems delete records after a fixed time, the period is shown in the table. The other records have no automatic deletion period.
You can ask for a copy of your data or for its deletion as described in our Privacy Policy.
4. What we do not record
Our servers forward your traffic without recording its content: what you read, send or download inside the tunnel is not stored. The destination of each connection is recorded as described in section 1.
5. Legal requests
If we receive a legal request, we can provide only data we hold: the data listed on this page, for as long as it is kept. We do not hold the content of your traffic.
See our Transparency Report for statistics on legal requests received.