Skip to main content

Legal

Privacy Policy

Version 1.13, updated 21 November 2026

This notice tells you what personal data we collect when you use our website, our apps, our VPN service and our routers, why we use it, and your rights. It starts with a summary; the full notice follows. What changed in version 1.13, on 21 November 2026: section 9 now names EDIS, which hosts our VPN server in Iceland from 20 November 2026, and says that 1984 Hosting hosted it until then. What changed in version 1.12, on 20 November 2026: section 5 now says that the apps may ask you why when you turn off renewal or cancel, and that your answer is saved without your account, device or IP address. What changed in version 1.11, on 19 November 2026: section 5 now says that, from app version 1.7.19, the apps also send a few anonymous counts once per install, such as whether your first connection worked, and section 11 says how long we keep them. What changed in version 1.10, on 16 November 2026: section 5 now says that the protection counts on the app dashboard stay on your device. What changed in version 1.9, on 15 November 2026: we do not delete accounts automatically, including unused accounts from our old billing system, except an account made at checkout and never paid for, which we delete after about a day; we delete an account when you ask us to (summary, sections 3.5 and 11). Section 11 now lists the records we get from Apple, Google and Amazon, says when we delete payment and app store records and the history of changes to your plan, lists the archive of payment records from our old billing system and our router management records, and says that some backup copies are kept longer than 30 days for now. For Amazon purchases we keep your Amazon user ID, and for PayPal payments your PayPal payer ID (section 3.2). Section 4 now says that on 15 November 2026 we deleted the connection times and data totals from before 12 October 2026 from every device record and the connection records from our old 2018–2019 system, that some backup copies still hold them for now, and that we record when a router's management connection last checked in. Section 7.1 says we have deleted the support tickets, emails and activity logs of our old billing system. Section 12 lists more ways to delete your account. What changed in version 1.7, on 7 November 2026: we now say more exactly what we do not keep. We say we do not keep a history of the websites visited by any account or device, and that our servers' records hold neither your IP address nor your account. What our servers do has not changed (summary and section 4). What changed in version 1.6, also on 7 November 2026: section 15 now says how we tell you about changes to this notice. We update the version number and date, and post the change on this page and on your account page. What changed in version 1.5, also on 7 November 2026: some ticket replies may now be drafted on our own office computer using an AI service, which receives the ticket's messages and basic plan details (sections 7.2, 8, 9, 10 and 11); a person checks each of these drafts before it is sent, and you can object. What changed in version 1.4, on 6 November 2026: section 4 now describes more exactly what the classifier sends to an AI provider and how long records are kept, and the list of unrecognised website names has stopped and been deleted. Earlier on 6 November 2026: we may now ask you once, about 30 days after your first payment on our website, to review us on Trustpilot. To do this we share your name and email address with Trustpilot, with a one-off reference number (sections 8, 9 and 11). You can turn this off in your email preferences. Also on that date, section 4 now describes how our VPN servers recognise the type of traffic on each connection from its first few packets, in memory, keep hourly totals that are not linked to you, and block BitTorrent on every location except Iceland; and how they record technical details of how connections start, to learn to recognise new applications; those records are deleted at the latest 24 hours after the hour they describe.

Summary

  • Who we are: VPNFAST LTD. (“SpiderVPN”, “we”) decides how your personal data is used. Contact: [email protected].
  • What we collect: your account details (email and password, and your name if you give it), billing records, the devices you connect, the date each device last used the VPN, crash reports from the apps, error reports from the website and our servers, your messages to support, and anonymous statistics about how our website and apps are used (sections 5 and 6), which you can turn off.
  • What we do not keep: a history of the websites visited by any account or device, the content of your traffic, or the DNS queries you make. Our VPN servers do look at the first few packets of each new connection, automatically and in memory only, to recognise the type of traffic and to block file sharing where it isn't allowed. They keep hourly totals and short-lived records of how connections start (to learn new applications), that hold neither your IP address nor your account, and, to block file sharing, the addresses of BitTorrent connections in memory for a few minutes (section 4). Our VPN servers do not record your device's IP address. Some older records hold more than this; section 4 says what they are.
  • What we keep about your connections: for each device, the VPN location it uses and the date (not the time) it was last used. We do not record when you connect or disconnect, how long you stay connected or how much data you use, and we do not keep a history. Details in section 4.
  • AI support: our website chat and some ticket replies are answered by an AI assistant (Anthropic's Claude). The chat tells you when you are talking to AI, and a person checks anything important.
  • Free trials: to give each person one trial, we keep one-way codes made from your email, device and card or PayPal account, and we email you before you are charged.
  • Old accounts: we moved every login from our old billing system, including unused ones. We keep them until you ask us to delete them.
  • Why: to provide the service, take payment, stop fraud and abuse, keep the service and our network secure and working (including recognising types of traffic, section 4), and meet our legal duties. Where we rely on our legitimate interests, you can object (section 12).
  • Who else sees it: our service providers (payments, app stores, hosting, email, support, AI support (Anthropic), crash and error reporting, DNS), an AI provider that helps us draft some ticket replies and classify traffic (sections 4 and 7.2), and Trustpilot, which sends you one invitation to review us (section 9). We do not sell your data.
  • Your rights: you can ask for a copy of your data, correct it, delete it, object, and more. You can complain to us, and to the Information Commission (still known as the ICO).

1. Who we are and how to contact us

SpiderVPN is a trading name of VPNFAST LTD., the controller of your personal data. VPNFAST LTD. is registered in England and Wales with company number 15716229. Registered office: Office 12675, 182-184 High Street North, London, England, E6 2JA. Email: [email protected].

We have not appointed a data protection officer. For anything about your personal data, email [email protected].

2. This notice

This notice tells you what personal data we collect when you use our website, our apps, our VPN service and our routers, why we use it, and your rights. It is information for you. You do not need to agree to it, and we never ask you to tick a box to accept it.

3. The data we collect

3.1 Your account

Data
Name
Where it comes from
You, if you add it to your account (optional)
Data
Email address
Where it comes from
You
Data
Password
Where it comes from
You (see the security note in section 10)
Data
If you sign in with Google or Apple: your account identifier and email from Google or Apple
Where it comes from
Google or Apple, when you choose this
Data
Your language choice
Where it comes from
You (website and apps)

3.2 Payments and orders

Data
Plan, price, order and invoice history, payment status
Where it comes from
Us
Data
Card or PayPal details: we receive only a reference, the card type and the last digits, and your PayPal payer ID for PayPal payments; Stripe or PayPal holds the full details
Where it comes from
Stripe, PayPal
Data
Cryptocurrency payment reference and status
Where it comes from
CoinGate
Data
App store purchase records (transaction or receipt identifiers, your Amazon user ID for Amazon purchases, product, status, renewal and cancellation events)
Where it comes from
Apple, Google, Amazon

For routers: the delivery name, address and phone number, which your payment provider (Stripe, including Apple Pay and Google Pay, or PayPal) passes to us when you pay, or which you type in if it doesn't.

Country: only for router delivery.

3.3 Free trial checks

To make sure each person gets only one free trial, we check your account, email address, device and payment method against earlier trials. For a card, we use a code from Stripe that is the same every time the same card number is used (the card “fingerprint”), and we also check the card type (for example prepaid) with Stripe. For PayPal, we use your PayPal account ID. We store all of these only as keyed one-way codes (HMAC hashes). We cannot easily turn them back into the original data, but they are still personal data, because we use them to match new trial requests. When we refund a payment, we also keep the same one-way code for the card or PayPal account used, so it cannot start a new trial. We also keep a record of each trial: your email, account and device identifiers, the plan, its status and its dates. To start a trial on our website, you add a card or PayPal account; we take no money until the trial ends.

Trial emails: when your trial starts, we email you its end date, the price and how to cancel. We email you again 7 days before we charge you. These emails are part of your contract with us.

We do not refund renewal payments. Before renewals we email you reminders with the renewal date, the price and a link to cancel, as described in our Terms of Service, section 8.4, so you can cancel in time (see our Refund Policy).

3.4 Your devices

Data
A random device identifier created by the app
Why
To tell your devices apart and apply the device limit
Data
The device's model name (for example “iPhone 15”) and type (phone, computer, TV, router)
Why
So you can recognise your devices in your account
Data
For routers: board model, firmware and SpiderVPN software version
Why
Support and updates
Data
Your WireGuard public key and the private IP address we give the device inside the VPN
Why
To run the VPN connection

You can see and remove your devices in the app.

3.5 Accounts from our old billing system

When we moved to our new billing system, on the date this notice took effect, we also moved every login from the old system, including logins with no active subscription. We did this so those people can still sign in, and so we can spot and block fake or abusive sign-ups (for example, many accounts made from one network or with throwaway email addresses). We moved only the account's name, email address, password in scrambled (hashed) form, whether and when the email was verified, when the account was made and last changed, its number in the old system and, for a login that belonged to another customer's account, which account that was. If your old password could not be moved safely, you will need to reset it. If you sign in, the account works like any other account. We do not delete these accounts automatically, even if they are never used. You can ask us to delete yours at any time (section 12). We never use these accounts for marketing.

If you asked us to delete your account in the old system, we did not move it, and we will not add it back.

4. Your VPN use

What we never collect

We do not collect or store:

  • a history of the websites visited by any account or device;
  • the content of your traffic;
  • your DNS queries (but see “DNS” below);
  • your device's public IP address against your VPN connections on our VPN servers;
  • when you connect or disconnect, how long you stay connected, or how much data you use.

Our VPN servers need your device's current public IP address, the time of its latest contact and how much data has passed, in memory while you are connected, to send traffic back to you. They do not pass any of these on, and our monitoring receives only totals for each server that are not linked to any device or account. Until 12 October 2026 our monitoring also received each device's connection times and data totals. Our monitoring deletes data after 15 days, so those older records are gone by 31 October 2026.

How our servers recognise traffic

To protect our service and network, and to keep the service working well, our VPN servers automatically recognise what kind of traffic each connection carries, such as web browsing, video calls or file sharing.

Software on each server looks at the first few packets of each new connection (at most about 10 in each direction) as they pass through, in memory. These first packets can include the name of the website or service you are connecting to and, for websites that don't use encryption, the start of the request. The software does not read the rest of the connection, does not store the content of your traffic, and does not record which device or account a connection belongs to. It forgets a connection 30 seconds after it goes quiet. To recognise the connection that follows a DNS lookup, it also remembers, in memory for 60 seconds, which server addresses the DNS answer pointed to; this memory never holds your address. Nobody at SpiderVPN looks at individual connections.

Each VPN server keeps, for each hour:

  • the number of connections and the amount of data for each application and type of application, on that server. These totals are not linked to any device or account. On a quiet server a rarely used application can show a total as low as one;

We delete these totals after 15 days. Traffic recognition has run on all our VPN locations since late October 2026. From 2 to 6 November 2026 each server also kept a list of up to 50 website names it could not recognise; we stopped that list on 6 November 2026 and have deleted it.

Learning to recognise new applications

To teach the software to recognise more applications, each VPN server also records, for each hour, technical details of how connections start, counted together:

  • the full name of the website or service the connection asks for, including parts such as www. (from the secure-connection setup or, for websites that don't use encryption, from the request), and its main domain name;
  • whether the connection uses TCP or UDP, and how our software classified it;
  • the protocol the app asks for, such as HTTP/2 (ALPN), and a fingerprint of how the app sets up its secure connection (JA4);
  • the network block of the server's address (we look up its operator later), and, for connections without a name, the server's port number or “other”;
  • rough sizes and timings of the first few packets of the connection.

Each combination is recorded with how many connections it was seen on in that hour, even if it was seen only once. These records never include your IP address, your device's private VPN address, your VPN key, your account or the time of an individual connection. But a rare combination, such as an unusual website name seen once on a quiet server, describes a single connection. We do not try to link these records to anyone.

The records are sent over encrypted connections to our own services server and to one of our own office computers, which has an encrypted disk; only our administrators' systems can read them. On that computer our automated classifier checks them against our recognition rules. To decide what an unrecognised name or fingerprint is, the classifier uses an AI model service, under that provider's own terms, not as our service provider, and sends it only a short list combined across all our servers and hours, capped in size: main domain names with a total count for each, website names, the server network's operator, ALPN and JA4, and our own list of application names. We have turned off the setting that lets the provider train its models on this data, though it may still use content its safety systems flag. The list does not say which server or hour anything came from, but a rare entry in it can still come from a single connection.

The records are checked automatically; our administrators look at them only to fix a problem with the classifier. We delete each record as soon as it has been dealt with: it matches an existing rule, it led to a proposed new rule, or it was set aside as not useful. Records are deleted at the latest 24 hours after the hour they describe, on the VPN server, our services server and the office computer alike. New recognition rules (for example a website name for an application) are checked before we use them, and we keep the rules.

File sharing: BitTorrent traffic is blocked on all our VPN locations except Iceland. The servers decide this automatically, using the recognition above. When a server recognises BitTorrent traffic, it remembers in memory the addresses involved, including your device's private VPN address, so it can also block your device's encrypted follow-on torrent connections. It stops using these addresses 5 minutes after the last torrent connection. They are never written to disk or sent anywhere, and are overwritten as the memory fills or when the software restarts. While they are in memory they could in principle be linked to your account through your device's private VPN address; we do not do this.

When the app talks to our API (for example to sign in, fetch servers or set up a device), our web servers keep a short technical record of the request: the page address, the response code and size, and how long it took. These records do not include your IP address. Our API's own logs identify you by an internal number only, never by your email or IP address, and are deleted after 7 days. If a request fails, the web server's error log records the IP address it came from. Our web servers keep their access and error logs for 7 days, and we have deleted the older logs that included IP addresses.

What we keep

For each device you set up, we keep:

Data
Your account email, the device identifier, the device's name and type, its VPN key and private VPN address, and the VPN location the device is set up for
Why
To run your connection and apply your plan and device limit
How long
While the device is active (see below)
Data
The date (not the time of day) the device was last used on our VPN servers
Why
To find devices that are no longer used, so we can free up resources and remove old keys
How long
Only the latest date is kept; each new date replaces the old one

Every few minutes, our account system asks each VPN server which devices have been used today. The server works this out in memory and passes on only the list of devices used today. It never passes on your IP address, the time of day or how much data a device used. We do not keep a history of these dates, so we cannot see when you were connected, only the latest day a device was used.

Deletion: if a device has not been used for 7 days, we deactivate it (a device that never connects is deactivated after 1 day). We delete a deactivated device's record, with all the data above, once it has not been used for 30 days. This happens in a weekly job, so the data is gone at the latest about 37 days after the device was last used. If you remove a device in the app, we deactivate it at once and delete it on the same schedule.

We have kept only the date since 12 October 2026. On 15 November 2026 we deleted the older connection times and data totals from every device record. Some backup copies still hold them for now. We have also deleted the connection records from our old 2018–2019 system. Some backup copies still hold them for now.

What this means: we do know which account is set up on which VPN location and the date each device was last used. We do not keep a list of the websites any account or device visits, and we do not know what you do online or when during the day you were connected. Our servers recognise types of traffic as it passes through and keep hourly totals and short-lived learning records that hold neither your IP address nor your account (see “How our servers recognise traffic” above).

DNS

When you are connected and SpiderVPN DNS is on (the default), your device's DNS queries go through the VPN to SpiderVPN DNS, our DNS service for all VPN locations. It blocks known advertising and tracking services. SpiderVPN DNS is run for us by a DNS infrastructure provider; its DNS servers run worldwide. We have turned off query analytics for SpiderVPN DNS, so the DNS queries you make are not stored in our account with that provider.

You can turn SpiderVPN DNS off in the app. Your DNS queries then still go through the VPN, to Quad9, a Swiss non-profit foundation, or to Cloudflare if Quad9 cannot be reached. They handle your queries under their own privacy policies, and we do not see or log them. With SpiderVPN DNS off, advertising and tracking services are not blocked.

Routers

A SpiderVPN router keeps a secure management connection to our servers. Our support team can use it to reach the router's settings to help you, install updates and fix problems. We do not use it to monitor your internet traffic; your router's traffic through the VPN is treated like any other VPN traffic (see “How our servers recognise traffic” above). The router's identifier is based on its network (MAC) address. Every 2 hours the router checks our update server for new firmware.

We record when the router's management connection last checked in (only the latest time), to see whether it is online and to free unused addresses.

The management connection cannot be turned off from the router dashboard; contact support if you want it off. Each time our support team uses it, we log who connected, to which router and when, and keep that log for 2 years.

When the router checks for updates, our update server records the time, the file it asked for and the details its request sends. It does not record the router's IP address.

5. App crash reports, error reports and usage statistics

The apps send crash reports and some performance data to Sentry and to Google Firebase Crashlytics. These reports contain technical details: the app version, the device model and operating system, what happened in the app before the crash, and an installation identifier. We set Sentry not to send personal information such as your IP address or user details, and not to take screenshots. Sentry collects performance data from about 1 in 5 app sessions.

Error reports: when our website or our servers hit an error, we send a technical error report to Sentry (EU data region). A report contains the error message with email addresses, access tokens and keys removed, the place in our code where it happened, the request method and page address without anything after the “?”, the server and software versions and, for errors in your browser, your browser and operating system. It never contains your IP address, your account or user details, cookies, form contents or what you typed. Reports from your browser go through our own server, so Sentry does not receive your IP address. We do not record website performance or sessions.

Crashlytics keeps crash reports for 90 days. Sentry keeps app and website reports for up to 90 days.

You can ask us to stop by emailing [email protected].

We do not use advertising tools in the apps, and the only analytics are the anonymous counts described below.

App usage statistics: our apps send anonymous counts. Each count carries only the type of system (such as iOS or Fire TV), the app's version (such as 1.7.19; the first-time counts carry only the major version, such as 1.7), roughly how long ago the app was installed (such as 2 to 7 days), what is being counted and one small detail of it:

  • one count per day that the app is used, with your device's region (country only);
  • from app version 1.7.19, one count the first time each of these happens on an install: the first VPN connection (whether it worked or, if not, the type of error); your answer when your device asks to allow the VPN; the plans shown for the first time (and on which screen); the first free trial started (and through which store).

The counts have no account, device or advertising identifier, and we do not store your IP address with them. For the daily count our server replaces it with a fixed one; for the first-time counts it keeps a scrambled form for about a minute to limit abuse. For the first-time counts we keep only a total for each day. You can turn all of these off on first launch or at any time in Settings > Privacy.

If you turn off renewal or cancel in the app, it may ask you why. Your answer, and any note you type, is saved without your account, device or IP address, and we use it only to improve SpiderVPN.

Protection counts on the dashboard are worked out and kept on your device only and are never sent to us.

6. Our website

  • Server logs: our web servers record requests (the page address, the response code and size, and how long it took, but not your IP address) to protect the website from attacks and fix faults. We keep them for 7 days. When a request fails, the error log records the IP address it came from, also for 7 days.
  • “What is my IP” tool: if you use it, we send your IP address to ipinfo.io to look up its approximate location, and keep the result in a short-term cache for up to 24 hours.
  • Security checks: before a website chat starts, and before checkout creates a new account, Cloudflare Turnstile checks that a person, not an automated program, is using it. To stop password guessing, we keep one-way codes made from your email and IP address for a short time, and we limit how many requests one IP address can make. Our servers' security logs, which record the IP addresses of attempts to log in to the servers themselves, are kept for 7 days.
  • Website chat: if you open the chat, we store a chat identifier in your browser so the conversation continues across pages (see section 7.2).
  • Website statistics: we count how the website is used, anonymously and without cookies (see “Website statistics” below).

Website statistics

We count how our website is used so that we can improve it and plan our marketing: which pages are visited and which of our links are clicked, how long pages are viewed, the country a visit comes from, the site or campaign that linked to us, and the type of device and browser (including screen size and language). We do not use these statistics for advertising, and we do not sell or share them.

How it works: our statistics run on our own servers and use no cookies. We do not store your IP address, and we keep only the country a visit comes from, not your region or town. Before anything is sent, personal details are removed from the page address, such as order or invoice numbers.

If you arrive from one of our campaign links, the link's campaign tags (such as the site, the campaign and the post it came from) go with your order, so we can count which campaigns lead to trials and sign-ups. They are short labels, never your name, email or IP address, and we delete them 13 months after the order. If your browser sends Do Not Track or Global Privacy Control, or you turned statistics off below, your order carries none. Clicks on our short links (spidervpn.org/go/…) are counted on our own server in the same way, without your IP address.

If you arrive through a friend's referral link or an affiliate link, we record that code with your order so we can add the free month or pay the commission; this is not used for statistics, and Do Not Track or the statistics setting doesn't change it.

We keep the statistics for 25 months and then delete them. Backup copies of the statistics are kept for up to 6 months.

You do not have to accept anything. If your browser sends Do Not Track or Global Privacy Control, it sends us no statistics. You can also turn statistics off for this browser here; your choice is kept in this browser's storage:

Checking your choice for this browser…

Cookies and similar storage

Our website uses only the cookies and browser storage it needs to work. We do not use advertising or analytics cookies (our website statistics use none), so we do not ask you to accept cookies.

  • Your language choice: a cookie, so pages open in the language you picked.
  • Checkout: cookies that keep your order and your sign-in together while you buy. They expire after a short time.
  • Checkout payments: Stripe sets fraud-prevention cookies (__stripe_mid, up to a year; __stripe_sid, 30 minutes) when you open the checkout.
  • Account area: a sign-in session cookie and a security cookie that protects forms.
  • Light or dark theme: kept in your browser's storage until you change it.
  • Website statistics: if you turn them off, your browser keeps a note of that in its storage.
  • Website chat: the chat identifier described above.
  • Cloudflare, which delivers and protects our website, may set a cookie to tell people from automated programs, and Turnstile does a similar check before a chat starts or checkout creates a new account.

You can delete cookies and browser storage in your browser settings at any time. The website will then forget your choices, and you may need to sign in again.

7. Support

7.1 Support tickets

If you contact us, we keep your messages, our replies, your email address and anything you choose to send us (such as screenshots or logs). We use the support ticket system in our account area, which runs on our own servers, for this. Tickets from our old billing system were moved into it. We have deleted the old billing system's support tickets, emails and activity logs; the copies of the tickets you raised are kept in our current support system.

7.2 AI support assistant

Our website chat, and some replies to support tickets, are written by an AI assistant. The chat tells you at the start that you are talking to AI, and you can ask for a person at any time. The assistant uses Claude AI models from Anthropic, PBC (United States), which processes your messages for us as our service provider. If you are signed in, the assistant can see your account, subscriptions, invoices and devices, and the status of our VPN locations, so that it can answer you. It can check a payment with Stripe or PayPal, resend emails, and extend your service by up to 3 days at a time after an outage or a payment delay. It cannot change your email, password or two-step sign-in, or delete your account. A person checks any refund, plan change or cancellation it suggests before it happens. We keep chat transcripts for 30 days. Anthropic deletes chat content it receives within 30 days. If its automated safety systems flag a conversation as breaking its usage policy, it may keep that content for up to 2 years. Anthropic does not use these conversations to train its models. Please do not put passwords, full card numbers or health information in the chat.

Some ticket replies are drafted on our own office computer using an AI service. It receives the ticket's messages and basic plan details. That provider handles this data under its own terms, not as our service provider. A person checks each of these drafts before it is sent. We have turned off the setting that lets the provider train its models on this data, though it may still use content its safety systems flag.

8. Why we use your data and our lawful basis

Purpose
Create and run your account; provide the VPN; manage devices
Data
3.1, 3.4, section 4
Lawful basis (UK GDPR Art. 6)
Contract
Purpose
Take payment, renew, refund
Data
3.2
Lawful basis (UK GDPR Art. 6)
Contract
Purpose
Send trial start and trial-ending reminder emails, and renewal reminders
Data
3.1, 3.3
Lawful basis (UK GDPR Art. 6)
Contract
Purpose
Keep invoices and accounting records
Data
3.2
Lawful basis (UK GDPR Art. 6)
Legal obligation
Purpose
Stop trial abuse and payment fraud (one trial per person, including card fingerprint and PayPal account ID codes)
Data
3.3, 3.2
Lawful basis (UK GDPR Art. 6)
Legitimate interests: keeping free trials fair and protecting our business from abuse
Purpose
Keep the service and the website secure; stop attacks and password guessing
Data
Sections 4, 6
Lawful basis (UK GDPR Art. 6)
Legitimate interests: security of our network and information systems and of your account
Purpose
Recognise types of traffic on our VPN servers, block BitTorrent where it is not allowed, and teach our software to recognise new applications
Data
Section 4 (How our servers recognise traffic; Learning to recognise new applications)
Lawful basis (UK GDPR Art. 6)
Legitimate interests: protecting our service and network from abuse and legal risk, and keeping the service working well. You can object (section 12)
Purpose
Fix crashes and errors and keep the service reliable
Data
Section 5
Lawful basis (UK GDPR Art. 6)
Legitimate interests: a working, reliable app, website and service
Purpose
Count how the website is used, to improve it and plan our marketing
Data
Section 6 (website statistics)
Lawful basis (UK GDPR Art. 6)
Legitimate interests: improving our website and service. You can object at any time (section 6)
Purpose
Count how the apps are used, to improve them and plan our marketing
Data
Section 5 (app usage statistics)
Lawful basis (UK GDPR Art. 6)
Legitimate interests: improving our apps and service. You can turn it off at any time in the app (section 5)
Purpose
Ask you once, about 30 days after your first payment on our website, to review us on Trustpilot
Data
Sections 3 and 9 (your name and email address, with a one-off reference number)
Lawful basis (UK GDPR Art. 6)
Legitimate interests: learning how customers find our service and showing honest reviews. You can turn review invitations off in your email preferences, or object (section 12)
Purpose
Answer your messages, including through our AI assistant
Data
Section 7
Lawful basis (UK GDPR Art. 6)
Contract for customers; legitimate interests (answering questions about our service) when you are not a customer
Purpose
Draft some ticket replies on our office computer using an AI service
Data
Section 7.2 (the ticket's messages and basic plan details)
Lawful basis (UK GDPR Art. 6)
Legitimate interests: answering support tickets quickly and well. A person checks each of these drafts before it is sent. You can object (section 12)
Purpose
Bring over logins from our old billing system and find abusive sign-ups
Data
Section 3.5
Lawful basis (UK GDPR Art. 6)
Legitimate interests: letting former users keep access, and protecting the service from spam and abuse
Purpose
Ship routers
Data
3.2
Lawful basis (UK GDPR Art. 6)
Contract
Purpose
Send service emails (receipts, security, changes to terms)
Data
3.1
Lawful basis (UK GDPR Art. 6)
Contract and legal obligation
Purpose
Comply with the law, court orders and lawful requests
Data
Any data we hold
Lawful basis (UK GDPR Art. 6)
Legal obligation

You must give us your email and a password (or sign in with Google or Apple) to have an account, and payment details to buy. Without them we cannot provide the service.

Marketing: we do not send marketing emails today. If we start, we will send them only to people who opt in, and every message will have a one-click way to stop. We never send marketing to accounts brought over from our old billing system unless their owners opt in.

9. Who we share data with

We do not sell your personal data. We share it only with:

Who
Stripe
What for
Card payments
Where
United States (UK–US data bridge). Our contract is with Stripe Payments Europe Ltd (Ireland) and Stripe Payments UK Ltd (United Kingdom)
Who
PayPal
What for
PayPal payments
Where
United Kingdom (PayPal UK Ltd), with other PayPal group companies
Who
CoinGate
What for
Cryptocurrency payments
Where
Lithuania
Who
Apple, Google, Amazon
What for
App store purchases
Where
Each store's own locations, including the United States, under its own transfer arrangements (see section 10)
Who
Google and Apple
What for
Sign-in with Google or Apple, if you choose it
Where
Google: United States (UK–US data bridge). Apple: its own locations, including the United States, under its own transfer arrangements
Who
Hetzner
What for
Hosting of our main servers
Where
Germany
Who
VPN server hosting providers: Clouvider, LiteServer, EDIS, 1984 Hosting (until 20 November 2026), Alwyzon, Webdock, netcup, Ikoula
What for
Hosting of VPN servers
Where
The country of each VPN location: United Kingdom, United States, Netherlands, Iceland, Austria, Denmark, Germany, France. For the United States location, our contract is with Clouvider Limited, a UK company (number 08750969), which runs the server in Ashburn, Virginia, so UK data protection law continues to apply to it
Who
Cloudflare
What for
Website delivery and protection
Where
United States and Cloudflare's worldwide network (UK–US data bridge)
Who
Cloudflare (Turnstile)
What for
Website chat and account sign-up protection
Where
United States (UK–US data bridge)
Who
DNS infrastructure provider (runs SpiderVPN DNS)
What for
DNS for VPN connections when SpiderVPN DNS is on
Where
DNS servers worldwide
Who
Quad9
What for
DNS for VPN connections when SpiderVPN DNS is off
Where
Switzerland; DNS servers worldwide
Who
Cloudflare DNS
What for
DNS for VPN connections when SpiderVPN DNS is off and Quad9 cannot be reached
Where
United States and Cloudflare's worldwide network (UK–US data bridge)
Who
Brevo
What for
Sending emails
Where
European Union (France, Germany and Belgium)
Who
Trustpilot A/S
What for
Sending you one invitation to review us, about 30 days after your first payment on our website (your name and email address, with a one-off reference number). If you write a review, Trustpilot's own privacy notice applies to it
Where
Denmark. Trustpilot's group companies and service providers may also handle this data in other countries, including the United Kingdom and the United States, under Trustpilot's data processing terms. Trustpilot publishes the list of them on its website
Who
Anthropic, PBC
What for
AI support assistant (website chat and ticket replies)
Where
The United States and other countries
Who
An AI provider
What for
Drafting some ticket replies on our office computer (the ticket's messages and basic plan details, section 7.2); classifying unrecognised traffic (section 4: lists of website names and connection fingerprints, combined across servers and hours, not linked to anyone). It handles this data under its own terms, not as our service provider
Where
The United States and other countries
Who
Sentry
What for
App crash and performance reports; website and server error reports
Where
EU data region (Germany); Sentry is a US company covered by the UK–US data bridge
Who
Google (Firebase Crashlytics)
What for
App crash reports
Where
United States (UK–US data bridge)
Who
ipinfo.io
What for
IP location for the “What is my IP” tool
Where
United States
Who
ShipEngine and our delivery carriers; Ideal Postcodes
What for
Router delivery and UK address lookup
Where
ShipEngine: United States. Ideal Postcodes: United Kingdom. Carriers: the countries the parcel passes through
Who
Professional advisers, and a buyer if we sell our business
What for
As needed
Where
UK
Who
Police, courts and authorities
What for
Only when the law requires it, and only data we actually hold
Where
UK or as required

PayPal, Apple, Google and Amazon are responsible for their own use of your data in their services; see their privacy notices.

10. Transfers outside the UK, and security

Some of our providers process data outside the UK. When they do, we use one of these safeguards:

  • the country is covered by UK adequacy regulations, for example all EU and EEA countries (our main servers are in Germany);
  • for the United States, the provider is certified under the UK Extension to the EU–US Data Privacy Framework (the “UK–US data bridge”): Stripe, Sentry, Google and Cloudflare;
  • otherwise, the UK International Data Transfer Agreement, or the UK Addendum to the EU standard contractual clauses (for example Anthropic).

PayPal, Apple, Google and Amazon also use your data for their own services as independent organisations, under their own privacy notices, and make their own transfer arrangements. You can ask us for a copy of our safeguards at [email protected].

The AI provider in section 9 handles data under its own terms and makes its own transfer arrangements.

Security. We protect your data with encryption in transit, access controls and limited staff access.

11. How long we keep your data

Data
Account details
How long
Until you ask us to delete your account. We do not delete accounts automatically, except an account made at checkout and never paid for, which we delete after about a day. When we delete an account, we keep the invoices we must keep (see the next row) and remove the rest of the account's personal details
Data
Invoices and payment records
How long
6 years from the end of the company financial year they relate to (our financial year ends on 27 February), as company and tax law requires
Data
Archive of payment records from our old billing system (taken in May 2026)
How long
6 years, as invoices and payment records above
Data
VPN device records and the last-used date
How long
Section 4 (deleted within about 37 days of the device's last use)
Data
API application logs
How long
7 days
Data
Web server access and error logs
How long
7 days
Data
Server security logs (login attempts to our servers)
How long
7 days
Data
Records for learning new applications (website names, connection fingerprints)
How long
Deleted once dealt with; at the latest 24 hours after the hour they describe.
Data
Traffic recognition totals on each VPN server
How long
15 days
Data
Lists sent to the AI provider for classifying traffic (section 4)
How long
The provider keeps them for 30 days, or longer if its safety systems flag them
Data
Record of your marketing consent (when and from which IP address you gave it)
How long
While you stay on our mailing list, and for 2 years after you unsubscribe, so we can show you agreed
Data
Payment provider records (messages from Stripe, PayPal, CoinGate, Apple, Google and Amazon about your payments) and the history of changes to your plan
How long
While you have an active subscription, to deal with disputes and chargebacks. Once you have no active subscription, or you have asked us to delete your account, we keep them for 6 years from the end of the company financial year (ending 27 February) of your last record, and then delete them. This includes the payment notifications our previous billing system received from Stripe, PayPal and CoinPayments, which we keep for 6 years from the end of the financial year (ending 27 February) in which we received them, and then delete, even while you have an active subscription
Data
Backups
How long
Up to 30 days. Copies of our databases made when we update our service are kept longer for now
Data
Free-trial codes and trial records
How long
2 years after the trial record last changed. Refused trial requests: 90 days. Codes for refunded cards and PayPal accounts: 2 years after the refund
Data
Trial and renewal reminder emails sent (record of sending)
How long
2 years. Copies of the emails we send: 90 days
Data
Record that we asked you for a Trustpilot review
How long
While your account exists, so we never ask you twice
Data
Expired or revoked sign-in tokens
How long
Deleted 7 days after they expire or are revoked
Data
Support messages
How long
2 years after the ticket is closed and last updated
Data
AI chat transcripts
How long
30 days (Anthropic deletes its copy within 30 days, or keeps it up to 2 years if its safety systems flag a breach of its usage policy)
Data
AI help with support tickets
How long
The AI's working copy (the ticket messages it read, its draft replies and the account details it looked up): 30 days. The ticket itself: as "Support messages" above. Anthropic deletes its copy within 30 days, or keeps it up to 2 years if its safety systems flag a breach of its usage policy. Our record of actions the AI took (no message text): 1 year
Data
AI drafting of ticket replies on our office computer
How long
Our copy of the ticket text on that computer: deleted after each run. The AI provider's copy: 30 days, or longer if its safety systems flag it. The draft stays on the ticket, as "Support messages" above
Data
Accounts brought over from our old billing system and not used
How long
As account details above: we do not delete them automatically, and we delete them when you ask us to
Data
Crash and error reports
How long
Crashlytics 90 days; Sentry up to 90 days
Data
Website statistics
How long
25 months; backup copies up to 6 months
Data
App usage statistics
How long
25 months; backup copies up to 6 months
Data
First-time app counts
How long
13 months; backup copies as "Backups" above
Data
Router delivery details
How long
2 years after the order was last updated
Data
Router management records (the router's management connection and when it last checked in)
How long
While the router is set up with your account. Only the latest check-in time is kept; each new one replaces the old one
Data
Log of support sessions on a router's management connection (who, which router, when)
How long
2 years

We delete data when its period above ends. We do not delete accounts automatically, except an account made at checkout and never paid for, which we delete after about a day; we delete other accounts when you ask us to (section 12).

12. Your rights

You have the right to:

  • get a copy of your personal data;
  • correct data that is wrong;
  • delete your data (we may need to keep some of it, for example invoices);
  • restrict how we use your data;
  • object to our use of your data where we rely on legitimate interests;
  • move data you gave us to another provider (data portability);
  • withdraw consent where we rely on it, at any time;
  • automated decisions: where we make a significant decision about you using only automated means, you can ask us about it, tell us your view, ask a person to review it, and challenge it.

Our free-trial eligibility checks are automated. If we refuse you a trial, we tell you, and you can reply to tell us why you think we are wrong; a person will review the decision.

To use any of your rights, email [email protected] or contact us through support. You don't need a special form, and it's free. We reply within one month; if your request is complex we may need up to two more months and will tell you why within the first month. We may ask you to confirm your identity first, usually from your account email address.

Complaints: if you are unhappy with how we handle your personal data, tell us at [email protected]. We will acknowledge your complaint within 30 days and tell you the outcome. You can also complain to the ICO (see section 13).

Deleting your account: go to spidervpn.org/delete-account, or sign in and open spidervpn.org/billing/account/delete, or email [email protected] from your account email. Cancel any app store subscription in the store first; deleting your account does not cancel it.

13. Complaints

If you are unhappy with how we use your personal data, you have the right to complain to us. Email [email protected] with “Data protection complaint” in the subject. We will confirm we have received your complaint within 30 days, look into it, keep you updated, and tell you the outcome without undue delay. Section 18 of our Terms of Service explains how we deal with other complaints.

You can also complain to the UK regulator, the Information Commission (still known as the ICO): ico.org.uk, telephone 0303 123 1113. If you live in the EU, you can also complain to the data protection authority in your country.

14. Children

SpiderVPN is for people aged 18 and over. We do not knowingly collect data from children. If you think a child has given us data, contact us and we will delete it.

15. Changes to this notice

When we change this notice, we update the version number and date at the top and post the change on this page and on your account page.

For account, billing, cancellation, or data requests, contact support through the SpiderVPN support desk.