MultiTunnel Contact us

Privacy

Privacy notice

What MultiTunnel sends us, what it never sends, and what stays with your network, where we can't see it.

Version 1.0 (draft of 17 November 2026) · Not yet in force

1. Who we are

MultiTunnel connects a computer or phone to several private networks at once, each kept apart from the others, with post-quantum encryption. It runs on Windows, Linux and Android.

MultiTunnel is made by Prosperly Limited (“Prosperly”, “we”, “us”), a company registered in England and Wales under company number 15988727. Our registered office is 34 Water Lane, Southport, PR9 8JJ. We are registered with the Information Commissioner’s Office under number ZB949427.

2. Who answers for which data

MultiTunnel is built so that we hold as little as possible. There’s no central server that runs your network. Each network’s members, keys, rules and traffic stay on that network’s own devices. So most of the personal data involved in using MultiTunnel isn’t ours to answer for.

  • We are the controller for this website; emails and enquiries to us; security reports; the licensing check-ins devices send us (section 5.1); update checks and downloads from our site; diagnostics, if they’re ever switched on and shared; and billing records for paid plans. Contact us (section 3).
  • We don’t hold what’s inside a network, apart from what check-ins carry (section 5.1): its members’ email addresses, device names, access rules, the network’s signed log, and all the traffic its devices carry. The business or person that runs the network decides about that. Contact the network’s admins (section 6).

If you use MultiTunnel because your employer or another business added you to its network, the network’s admins answer for most of your data. They decide who joins, what each device may reach, and what the network records. They keep those records on their own devices. We can’t see or change them.

If you’re a patient or customer of a business that uses MultiTunnel, your records are held in that business’s own systems. MultiTunnel only carries them, encrypted, between that business’s devices. We never receive them. Ask the business that holds your records.

3. Contact us

We haven’t appointed a data protection officer. Our data protection lead deals with everything in this notice. You can complain to the Information Commissioner’s Office at any time (section 13). We’d appreciate the chance to put things right first.

4. What MultiTunnel sends us, and what it never does

Never sent to us: your traffic or anything about it (what you visit, your DNS lookups, who you talk to), where you are, your network’s access rules, or its members’ email addresses. Check-ins never say which other networks your device belongs to: each network on a device checks in separately.

We hold no keys for any network, so we couldn’t read a network’s traffic even if it passed through us. It doesn’t: devices connect to each other directly, or through a relay that the network itself runs.

What a device does send us is a daily licensing check-in (section 5.1), which includes some names, and, in some cases, update checks and downloads (section 5.2). Every connection to our services shows us the device’s IP address. Section 5.2 says when our web server records it.

5. Data we process as controller

5.1 Licensing check-ins

Every device checks in with our licensing service about once a day, for each network it belongs to, whether or not that network has a paid plan. Check-ins are automatic. They tell us whether the network’s licence is current, so that its devices can use paid features, and let us count active users for billing.

A check-in carries:

  • the network’s ID and the device’s ID (random-looking identifiers, not names), the device’s public keys, and the time it was sent;
  • a reference to the device’s user: a one-way hash of the user’s ID, salted with the network’s ID;
  • whether the device belongs to a person or to the network itself;
  • the MultiTunnel version, how far the device’s copy of the network’s log has got, and random numbers that stop a check-in being replayed or a device being copied;
  • the signed statement that an admin approved the device, which names that admin, or the delegate who added it;
  • if a delegate added the device, the entry that made them a delegate: the delegate’s name and the names of the users they may add devices for;
  • if the device’s own user added it, the entry that added the device they used to do so: that device’s name, its user’s name, its address inside the network, its tags and its keys;
  • the days (dates only) the device had a live connection in that network, for up to the last 35 days;
  • the IDs of the network’s devices it connected to on each of those days, with their signed approval statements the first time (which carry the same kinds of names as above), and the devices its network has removed or revoked;
  • the record of the network’s admin changes that we don’t already hold: the admins’ names and public keys, the network’s recovery public key, how many admins must sign a change, and the network’s address range;
  • the paid licence the network holds, if any.

Devices added before a network moves to the current log format send, instead of the approval statement, the entry that added the device: the device’s name, its user’s name, its address and mapped range inside the network, its tags, when its membership ends, and its keys. This stops once a network admin re-issues the network’s approval statements.

Connection days tell us something about people. Because each device reports which of its network’s devices it connected to on each day, we can see, for one network, which devices had connections with which on a given day. We use this only to count active devices accurately and to spot devices that never check in. We keep it for 40 days and then keep only the daily counts. We don’t combine it across networks. We do check whether one device ID checks in for two networks, which is a sign of a copied device.

Who sees the results. A network’s counts and billing standing go only to that network’s admins, on a request signed with an admin’s key. They include, for each user at or above their plan’s share of devices, how many devices that user had active.

Checks and flags. Most unusual patterns, such as a copied device, are flagged for a person at Prosperly to look at, and change nothing by themselves. Three checks also refuse a device automatically, so its paid features lapse once its grace ends: a device its own network has revoked, an approval signed after the signer stopped being an admin, and more self-added devices than the network allows. The network’s admins can put each of these right.

IP addresses. The licensing service doesn’t record a device’s IP address. To limit how many new networks can be registered from one place, it holds a count per address in memory, which is cleared at least daily.

If a check-in fails, MultiTunnel keeps working. A network’s tunnels never stop because of licensing. Paid features carry on for 30 days while our service can’t be reached.

5.2 Update checks, downloads and the transparency log

Update checks. When a device follows our stable releases, or one of its networks has it follow them, MultiTunnel looks up a public DNS record about every 10 minutes through the device’s usual DNS resolver, and fetches a small signed file from our site about once a day (devices in a network share what they fetch, so often only one asks). These requests carry nothing about the device except, unavoidably, its IP address. Once automatic security installs are switched on (see our terms of use), every device will make these checks.

Downloads. When a device downloads a release from our site, it may present a download token. The token names the network and the device, so we can check the network’s licence. If our site refuses one network’s token, the device tries the next network’s, so our site can then see that those networks share a device. We don’t keep a record of downloads.

Revoked licences are public. So that devices stop using a revoked licence, we publish a signed list of revoked licences in the same file. Each entry names the licence by its ID, the reason (such as non-payment) and the date. For revocations for fraud, cracking or a chargeback, it also names the network’s ID.

The transparency log. Releases are published with a transparency log at log.multitunnel.co.uk, and we publish a signing log for each of our release keys. These are public. They record what our release keys signed, as cryptographic fingerprints, and when. They contain nothing about customers or devices. A separate monitor, run at a different hosting provider, checks them every 10 minutes and alerts us by email if anything looks wrong. Those alerts are about our releases and keys, not about any network or person.

Our servers’ logs. Our web server keeps no log of ordinary requests. When a request fails with a server error, its error log records the request, including the device’s IP address. We keep that log, and our services’ own logs, for 30 days, to find and fix faults. Our services’ logs name a network’s ID when something about it needs a person’s attention, and never record addresses.

5.3 Diagnostics

MultiTunnel keeps a small record of how its connections are working (connection times, the kind of path in use, failed key exchanges, reconnects, memory use and version) on your device. It never holds names, addresses, keys or traffic. You can see it with multitunnel diag, and you can choose to send it to us yourself when you ask for help.

The app has a switch, off until you turn it on, to share anonymous diagnostics once a day: counts and timings in rough ranges, how many networks the device belongs to (never which), whether automatic security installs are turned off on it, the platform, the version and a random ID that changes every 30 days. Any network you belong to can forbid sharing on every member’s device. At present the app sends no diagnostics to us, even with the switch on: the collection service isn’t running. If we start it, sharing will still need your consent, and we’ll update this notice first to say how long we keep the reports.

5.4 This website

This website sets no cookies and stores nothing on your device. It uses no analytics, advertising or tracking tools, and its fonts, images and code all come from our own hosting.

Like every website, it’s delivered by a hosting provider. www.multitunnel.co.uk is served by Microsoft Azure Static Web Apps, and multitunnel.co.uk, for now, by our own server in Microsoft Azure’s UK South region, which passes visitors on to www. Each processes the technical details of a request, such as your IP address, your browser and the page you asked for, to deliver the site and protect it from abuse.

5.5 Emailing us and reporting security problems

If you email us, we use your message and contact details to reply, to follow up on what you asked, and to keep a record of the conversation. Our email is provided by Microsoft 365. Please don’t send us patient information, or anything else confidential about people, in an email.

If you report a security problem, we use your report and contact details to investigate it, to keep you informed and, if you want, to credit you.

5.6 Billing

Paid plans will be billed to the business or person that holds them. We’ll hold the billing account’s name, billing contact, billing address and VAT number, invoices and payment records, linked to the network IDs the plan covers. Card details will be held by our payment provider, never by us. Online billing isn’t running yet. We’ll update this notice, naming the payment provider, before it starts.

5.7 Purposes and lawful bases

  • Licensing check-ins: keeping a network’s licence and paid features current, and counting active users to bill a paid plan: Legitimate interests in providing the licence the network’s holder has with us, billing it accurately and protecting the licensing service; where you hold the network’s plan yourself, performance of our contract with you.
  • Using connection days between a network’s devices to count accurately, and checking for copied or cracked devices: Legitimate interests in accurate billing and in preventing fraud.
  • Update checks, downloads, the list of revoked licences, release signing and the transparency log: Legitimate interests in keeping devices secure, our releases trustworthy and our licences honoured.
  • Delivering and protecting this website, and keeping our servers’ error logs: Legitimate interests.
  • Replying to enquiries: Legitimate interests; steps at your request before entering a contract.
  • Handling security reports: Legitimate interests in keeping MultiTunnel secure.
  • Billing, invoicing and collecting payment: Performance of contract; legal obligation (accounting and tax).
  • Messages to a network’s admins about its licence, payments and security releases: Performance of contract; legitimate interests.
  • Shared diagnostics, if switched on in future: Consent.
  • Establishing, exercising or defending legal claims: Legitimate interests; legal obligation.

Where we rely on legitimate interests, we’ve weighed them against your interests. Ask us for the details (section 3).

6. Data that stays with your network

A network’s admins (the people holding its admin keys) decide what goes into their network: members’ names and email addresses, device names and addresses, groups, tags, access rules and the network’s contact details. All of it is held in the network’s signed log, which is kept on the network’s own devices and passed directly between them. Traffic goes directly between the network’s devices, or through a relay the network runs.

The business or person running a network is the controller of that data. We are not its processor either, because we don’t hold or handle it. The exception is what check-ins carry (section 5.1), which we hold as controller.

So if you want a copy of what a network holds about you, or want it corrected or deleted, ask that network’s admins. MultiTunnel shows each network’s contact details where the network has set them. If you contact us instead, we’ll tell you so and, where we can tell from what you send us which network it is, pass your request to that network’s admins with your agreement.

7. Who we share data with

These providers help us run MultiTunnel’s services and act only on our instructions:

  • Microsoft Azure: Hosting the licensing service, the release site, the transparency log, multitunnel.co.uk for now, and their backups. United Kingdom (UK South).
  • Microsoft Azure Static Web Apps: Hosting www.multitunnel.co.uk. Served from Microsoft’s worldwide network.
  • Microsoft 365: Our email. See section 8.
  • Cloudflare: Our domain’s DNS, which answers the update lookups in section 5.2. Worldwide network.

Others who see data:

  • A network’s admins see that network’s counts and billing standing, including how many devices each user at or above their share had active (section 5.1).
  • Anyone can read the list of revoked licences (section 5.2), and the public transparency and signing logs.
  • Our payment provider, once billing starts (section 5.6).

We may also share data with professional advisers under duties of confidentiality, with regulators or law enforcement where the law requires it, and with a buyer if we sell or merge part of our business. We don’t sell personal data to anyone.

8. International transfers

The licensing service, the release site and the transparency log run in Microsoft’s UK South region, and their backups are kept there too. www.multitunnel.co.uk is served from Microsoft’s worldwide network, and Cloudflare answers DNS lookups from its worldwide network, so the technical details of those requests may be processed outside the UK. Microsoft 365 holds our email. Where a provider processes personal data outside the UK, the transfer is covered by UK adequacy regulations, the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.

9. Security

Our services use TLS and offer a hybrid post-quantum key exchange, which MultiTunnel’s apps use. Everything our licensing service issues, and every release, is signed with hybrid classical and post-quantum signatures. Releases need two separate keys, and every release signature is published in the transparency log. Each service runs under its own account, sandboxed, and doesn’t record client addresses.

No system is perfectly secure. If we suffer a personal data breach, we’ll tell the networks’ admins affected without undue delay, and the Information Commissioner’s Office and the people affected where the law requires it. To report a security problem, email security@multitunnel.co.uk. More detail is on our Security page.

10. How long we keep data

  • Each network’s licence, billing reference and record of admin changes: While the network is registered with us.
  • Each device’s licensing record (ID, user reference, whose it is, how it was added, install ID, version, and when it was first known, enrolled, last checked in, last seen by other devices and removed): 400 days after the device was last seen.
  • Which devices were active, and which connected to which, each day: 40 days.
  • Daily counts of a network’s active users and devices: 400 days.
  • Flags for a person to review: With the network’s records.
  • The record of check-ins already seen (to stop replays): 10 minutes.
  • New-network counts per IP address: Until the next day, in memory only.
  • The check-ins themselves: Not kept.
  • Our web server’s error log and our services’ logs: 30 days.
  • Enquiries and the people who send them: 12 months from your last contact with us, unless you become a customer.
  • Customer contracts, billing, support and correspondence: 8 years from the last activity.
  • Security reports: As long as we need to fix the problem, then as correspondence.
  • Server backups: 30 days, so deleted records can last that much longer in a backup.

We apply the periods for a network’s records each time one of its devices checks in. If every device in a network stops checking in, we keep its records until its admins ask us to delete them. When a network’s admins ask, we’ll delete that network’s licensing records, except what we must keep for billing, accounting or legal claims.

11. Cookies

Our website sets no cookies, so it doesn’t ask for consent to them. The MultiTunnel app uses no cookies or advertising identifiers.

12. Your rights

You can ask us for a copy of the personal data we hold about you, and ask us to correct it, delete it, restrict how we use it or let you take it elsewhere. Where we rely on consent, you can withdraw it at any time. Email privacy@surgerly.co.uk and we’ll reply within one month.

Your right to object. You can object at any time to anything we do on the basis of legitimate interests, including licensing check-ins. Tell us, and we’ll stop unless we have compelling reasons that override yours. Check-ins can’t be switched off on a single device, so we’ll work with you and your network’s admins on how to act on it.

Most of what we hold is keyed to network and device IDs, not names. To find your records, we may ask for the network or device ID, which MultiTunnel shows.

Where data comes from. Most of it comes from your own device. Some comes from other people and devices: other devices in your network report the days they connected to your device and pass on your device’s approval statement; your network’s admins’ signed entries name you as an admin, a delegate or a device’s user; your network’s devices pass on its record of admin changes; and billing details come from the billing contact and, once billing starts, our payment provider.

Do you have to provide it? Check-ins are automatic. Paid features and downloads from our site depend on them. Without them, MultiTunnel keeps working, and its tunnels never stop.

Automated decisions. Some licensing decisions are automatic: a licence is revoked for non-payment when an invoice is a month unpaid, and the three checks in section 5.1 refuse a device by themselves. They’re about a network’s plan and payment, and its admins can put them right. We make no decisions about you by automated means that have legal or similarly significant effects on you.

13. Complaints

Contact us first at privacy@surgerly.co.uk and we’ll try to put it right. You can also complain to the Information Commissioner’s Office: Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF; helpline 0303 123 1113; ico.org.uk.

If your complaint is about what a network holds about you, the ICO will normally expect you to raise it with that network’s admins first.

14. Other

Your device’s own software. MultiTunnel uses parts of your operating system, such as Microsoft Edge WebView2 for the app window on Windows. Those parts are governed by their makers’ own privacy terms.

Children. Our website and services aren’t directed at children.

Links. Our website links to other sites. We don’t control them and aren’t responsible for their privacy practices.

Changes. We may update this notice. When we make a material change we update the version number and date above, and tell networks’ admins where it affects them. Previous versions are available on request.

Our terms of use cover using MultiTunnel itself.