Last updated: 13 November 2026
BrowserPod runs in the web browser. Code, files and data in a Pod stay on the device. This policy explains the one thing that does reach us: the requests a web browser makes to our servers to download the BrowserPod runtime and its disk images, and what we keep from them.
1. Who We Are and What This Policy Covers
Leaning Technologies Limited ("Leaning Technologies", "we", "us", "our") is a company registered in England and Wales at Nexus, Discovery Way, Leeds, LS2 3AA, United Kingdom. We make BrowserPod and serve its runtime and disk images from our servers. We are the controller of the information described in this policy.
This policy applies whenever a web browser loads the BrowserPod runtime or
its disk images from our servers, at rt.browserpod.io and disks.browserpod.io, whether or not the website or application that uses BrowserPod also uses
BrowserPod Edge. It concerns two groups of people:
- End-Users: anyone whose web browser runs BrowserPod, because they use a website or application that includes it (an "Integrator's Site"); and
- Integrators: the developers and organisations that include BrowserPod in their websites, applications and tools.
It does not cover BrowserPod Edge or the BrowserPod console, which are described in the BrowserPod Edge and Console Privacy Policy, or the BrowserPod website, which is described in our website Privacy Policy. The Integrator's Site is the Integrator's responsibility, under its own privacy policy.
2. What Stays on the Device
The BrowserPod runtime runs entirely inside the End-User's web browser. The code it runs, the files in a Pod and anything typed into it stay on the device. The runtime may keep a Pod's files in the browser's own storage for the Integrator's Site, so that they are available next time; that data is not sent to us.
The runtime contacts us only to download its own files and disk images. It sends us no telemetry, no licence checks and no information about what happens inside a Pod, and we set no cookies through it.
Without BrowserPod Edge, a Pod's network requests are sent by the End-User's browser, or by a service the Integrator chooses, directly to their destinations; they do not pass through our servers. When the Integrator's Site uses BrowserPod Edge, the Pod's network traffic does pass through our servers, as described in the BrowserPod Edge and Console Privacy Policy.
3. What Our Servers Receive
Because the runtime and its disk images are downloaded from our servers, the End-User's web browser connects to them each time a page that uses BrowserPod loads the runtime and each time a Pod starts. As with any website, each request carries information that the browser sends automatically, which may include:
- the End-User's IP address;
-
the origin of the Integrator's Site (for example
https://app.example.com), in theOriginandRefererheaders; - the browser's user agent and language;
- the file or disk image requested, including the runtime version; and
- the date and time of the request.
Our servers run on Cloudflare's network. Cloudflare processes this information to deliver the files and to protect the service from attacks, and may derive an approximate location, such as the country, from the IP address.
4. What We Keep: Usage Records
From these requests we keep usage records, which include:
- the origin of the Integrator's Site;
- the disk image requested;
- the name of our server that received the request; and
- the date and time of the request.
Usage records do not include the End-User's IP address or user agent, or anything from inside a Pod. They tell us which websites and applications use BrowserPod and how often, not who their users are.
We may combine usage records into a summary for each origin, such as the first and last time we saw it and the number of Pod connections over a period.
5. Why We Use It
We use this information, on the basis of our legitimate interests, to:
- deliver the runtime and disk images;
- keep the service secure and available, and investigate misuse of it;
- measure how BrowserPod is used: how many websites and applications use it, how many Pods they start and which disk images they use; and
- identify the organisations whose websites and applications use BrowserPod, through internal analysis by Leaning Technologies, so that we can offer them support, security advisories and commercial licences.
An origin usually names an organisation's website rather than a person. Where an origin identifies an individual, for example a personal website, we use it only for the purposes above and contact the person, if at all, through the contact details they publish for their site. You can object at any time (section 9).
7. How Long We Keep It
- Individual usage records are kept for up to three (3) months.
- Summaries for each origin are kept for as long as they serve the purposes in section 5, and reviewed at least once a year.
- Information Cloudflare processes to deliver the service is kept under Cloudflare's own retention periods.
8. Where It Is Processed
Requests are handled at the Cloudflare data centre closest to the End-User, which may be outside the United Kingdom and the European Economic Area. Usage records may also be stored and processed outside those areas. Where they are, we rely on appropriate safeguards, such as the standard contractual clauses in our agreement with Cloudflare.
9. Your Rights
Depending on where you live, you may have the right to access, correct or delete personal information we hold about you, to restrict or object to our use of it, and to complain to a data protection authority; in the United Kingdom, that is the Information Commissioner's Office. To exercise these rights, contact privacy@browserpod.io.
Because usage records contain no IP addresses or other details about End-Users, we usually cannot link them to an individual End-User. If you run a website or application and want us to stop using its origin for the purposes in section 5, other than delivery and security, tell us and we will.
10. Information for Integrators
When you include BrowserPod in your website or application, your users' browsers connect to our servers as described in section 3. We suggest you mention this in your own privacy policy; our documentation has guidance and suggested wording. If your users must not connect to a third party, BrowserPod can be self-hosted under an Enterprise licence.
11. Changes to This Policy
We may update this policy from time to time and will change the "Last updated" date when we do. Previous versions are kept at browserpod.io/legal.
12. Contact Us
For anything about this policy or your personal data, contact privacy@browserpod.io. For other enquiries, contact info@browserpod.io.











