Privacy

You do not need an account to use BuildBatch. Without one, BuildBatch sends none of your measurements, names or prices anywhere: BuildBatch sets no cookie, and a project you save is kept in this browser and nowhere else. A list you send as a link carries its figures with it, as sending a list explains. Visits to the pages are counted, without a cookie, as counting visits explains. BuildBatch also counts which of its tools and steps are used, without a cookie or any identifier and never what you type, as counting what is used explains. If you choose to create an account, the projects you save are also kept in it, so that they appear on your other devices. This page says exactly what that sends, where it is kept and how to delete it.

It has two parts: without an account, which is the default, and if you create an account. The sections after them apply to both.

Without an account (the default)

This is how BuildBatch works unless you create an account, and it is how it worked before accounts existed. None of it changes if you never create one.

Using a calculator sends none of your figures

A calculator, the room planner and the job planner are programs that run inside your browser. When you enter a room size, the arithmetic happens on your own device and the answer is drawn on the page. None of your figures is sent to us or to anyone else: no request carries a measurement, a name or a price you entered. A list you send as a link yourself carries its figures to whoever you send it to, as sending a list explains. The usage summary described under counting what is used does say which job was chosen, which steps were reached, which buttons were pressed and which kinds of problem the form pointed out, from fixed lists and by code, never what you typed. A shop's link, if you tap one, sends that shop a few generic words for the item and nothing else, as finding an item in a shop explains.

Some pages do ask this site one question of their own. The earlier flooring calculator asks whether a published product fits an estimate. The job planner, wherever it appears (it is also on the paint, wallpaper, tile, floor tile, flooring, skirting board, plasterboard, carpet, sheet vinyl, loft insulation, concrete, patio, MOT Type 1 and gravel calculator pages), asks which products the catalogue has published for a material, when it shows the step for choosing paint or flooring products, so that the choice of a catalogue product can say at once when there are none to pick. That request names the calculator or the material, nothing else, and the answer is public information. If it fails, the planner and the calculators carry on without it.

Some links carry a room from one tool to another so that you do not type it again: from the room planner or a calculator into the job planner. They put the measurements after a “#” in the page address. Browsers do not send that part of an address to the server, so the measurements stay on your device. On a guide, the box “Your room, in your own words” (on some guides your wall, patio, slab, loft or area) reads what you type on your own device, as the planner's own box does: this site sends the words nowhere, keeps them nowhere and does not count them. Once it has read something, the guide's button carries the figures and fixed words it read after the “#”, and nothing else you typed. The visit counter leaves that part out too: see counting visits.

  • Nothing is kept by BuildBatch. Close the tab or reload the page and what you typed into a form is gone, unless you deliberately saved it to a project. A room drawn in the room planner is the exception: the page keeps it, with its ceiling height, in its own address after “#”, so a reload or a bookmark brings it back, and your browser's history holds it until you clear it. A page you opened from a link that carries a room or a list (from the room planner, a calculator, or a list or start link) keeps those figures in its address in the same way. So does a list a planner has worked out, while it is on the screen: the room's figures, its name if you gave it one, and your choices are in the page's address after “#”, so that a reload or the Back button brings the list back. The ticks you make on its shopping checklist are kept the same way, in that tab's history, not in the address. Your browser's history holds that address until you clear it, and the list comes out of the address when you go back to change the room. A list you save to a project keeps, beside it in this browser's storage and nowhere else, the day you saved it, whose prices it was worked out with, their day and what they came to for its materials (with a short code for which lines and products they were for, so that only the same lines are set side by side), and, if you say how its count came out, that word and its day: so that, opened again, it can say what has moved.
  • Visits are counted. The pages load a visit counter run by Cloudflare, described under counting visits. There are no tracking pixels and no A/B testing. BuildBatch also counts which tools and steps are used, as counting what is used explains. Cloudflare, which hosts the site, shows BuildBatch totals of the requests it serves, and a sample of single requests for its security, as what the web host can see explains. We cannot see the figures you entered. What we count has no identifier in it, so it cannot follow you from page to page or from one visit to the next; but on a very quiet day a day's totals can describe a single visit, as counting what is used explains.
  • One thing is loaded from somewhere else without asking: the visit counter's script, from Cloudflare. A second, Google Analytics, is loaded only if you accept its cookies. The typefaces are served from this site, not from a font service. There are no embedded videos, maps, social buttons or adverts.
  • No account needed, for a calculator, the room planner or the job planner. Nothing you use without an account asks for a name, an email address or a phone number.
  • No cookies unless you accept them. The calculators, the planners, the guides and these information pages set none of their own. One line, after the planner's answer or after a page's own answer (on some pages well down the page), asks once whether Google Analytics may set two; until you say yes it sets none and is not loaded. See Google Analytics. Cloudflare says its visit counter stores nothing in your browser. To stop the counter, see counting visits. (Signing in to an account sets one cookie, which your browser sends only to the account's own addresses; it is described below. The private admin, used only by staff who sign in, sets a sign-in cookie for them. The host, Cloudflare, can set cookies in one case, when it stops a browser to check it: see the host.)

Copy and print. “Copy list”, “Copy buying list” and “Copy a price request” put text on your device's clipboard, and “Print” hands the page to your own browser and printer. All of them stay on your device; the price request is text for you to paste wherever you choose, and BuildBatch does not send it. The usage summary counts that a list was copied or a page printed, never the text. Your browser and operating system have their own rules about the clipboard and about printing; those are theirs, not ours.

Sending a list as a link

“Send this list” makes a link to this site's /list/ page. The part of the link after “#” holds the room's measurements and name, any chimney breast, bay or alcove you added, every product figure in the list (tin and pack sizes, coverage and prices, a catalogue product's included, and the wall paint's colour, finish and the name you typed for it), your Need / Check first / Have / Not needed marks, and the version of the sums and the day of the shop prices your list was worked out with, so that the page can say when either has changed since. BuildBatch does not send the link: you copy it, hand it to your phone's share sheet, or press “Send on WhatsApp”, which opens WhatsApp with the link in a message for you to send (nothing goes through BuildBatch, and WhatsApp's own privacy policy applies from there), and it goes wherever you send it, where anyone who can see it can read those figures. Whoever opens it gets the list worked out again on their own device. Browsers do not send the part of an address after “#” when they ask for a page. The usage summary never reads it: it counts only that a link was copied or shared, and that a list was opened from one.

Finding an item in a shop

Each line of a list has a “Find it at” button. It opens a short list of shops (Amazon UK, B&Q, Homebase, Screwfix, Toolstation and Wickes; for tiles and the adhesive, grout, spacers, trim, tanking and sealant that go with them, Tile Mountain, Topps Tiles and Walls and Floors in place of Amazon UK and Toolstation), and each one is a link that opens that shop's own search for the item, in a new tab. The link is an ordinary web address: the shop's search page and a few generic words for the item, such as “masking tape” or “matt emulsion 5 litre”. A line that names several things, such as gloves and a dust mask, first opens a short list of them, and each one opens its own search at the shops. A shop is left out of an item where its own search showed nothing of that kind on the day BuildBatch tried it; the list names the shop and the day. Some lines offer one more shop, and that link is an advert, marked “Ad”: Decorating Centre Online on some primer, mould treatment and wallpapering-tool lines, Insulation4less on the eaves ventilation, downlight cover, loft boarding, and pipe and tank insulation lines of a loft list, Materials Market on building-material lines, Wallpaperdirect on the wallpaper, lining paper and wallpaper paste lines, and Travis Perkins on the lines where it shows its own price for a named product. The links that are paid for, below, says what is different about them.

  • What the shop is sent. Only the search words in the address. They are generic words for the kind of item on the line, and never include your room's measurements or name, or a price. For paint they also carry the largest of the standard tin sizes (1, 2.5, 5 or 10 litres) that the list buys, and the wall paint's colour and finish where you chose them (such as “magnolia silk emulsion”). If you typed the name of your wall paint, such as “Farrow & Ball Estate”, that name is searched for instead, in letters and spaces only. If you chose a product from the reviewed catalogue, its catalogue name is searched for instead, and if you picked a partner shop's product for the line, its brand, range and size. The link also asks your browser not to tell the shop which page you came from.
  • When. Only when you tap a shop's link. BuildBatch loads nothing from any shop, so nothing goes to a shop while you use the list, and the list does not check whether a shop has the item.
  • What the shop sees. Once you have tapped, the shop sees your visit as any website does: your device's internet address, your browser and the search words. The shop's own privacy policy and cookies apply from then on, not this page.
  • No money. BuildBatch earns nothing from the links to those six shops. They are not adverts, and they carry no tracking code or affiliate identifier. BuildBatch does not know whether a shop has the item or what it costs.

Tracing a room over a drawing

The room planner and the job planner can open a floor plan you choose, a PDF or a picture, so that you can trace a room over it. Your browser opens the file on your device. It is not uploaded to BuildBatch and it is not saved: the page holds it in memory while it is open, and when you close or reload the page it is gone. What is kept is the room you trace, as corners in metres, exactly like a room you draw by hand, and the sums for it run on your device.

To open a PDF, the page loads a PDF reader from this site, and only when you choose a PDF. PDF reading uses pdf.js from Mozilla (Apache-2.0). Its licence is published with it, at /vendor/pdfjs/6.3.289/LICENSE.txt on this site.

What having it done would cost

Under a shopping list, “Having it done for you?” shows what published labour rates come to for that list. When you open it, the page loads the directory of rates from this site's own address, /labour-rates.json: the same figures, sources and dates as the labour costs page shows. The request carries nothing of yours, and the sums are worked out in your browser.

Saving a project stores it in this browser

A project lets you keep several estimates together — the paint for two bedrooms and the flooring for a hall — and see one shopping list for all of them. To do that it has to remember them, so a project is saved on this device, using your browser's local storage. Without an account it is not sent anywhere and it is not synchronised to any other device. Open the site on your phone and your projects are not there, because they never left the computer you made them on.

What is saved: the name you gave the project, the name you gave each area or room, the measurements and product figures you typed, and, for a list from the job planner, which lines you marked as needed, already owned or not needed, and which lines of its shopping checklist you ticked; since release 0.166.0, for such a list, the day it was saved, the shop whose prices it was worked out with, their day, what they came to for its materials and a short code for which lines and products they were for, and, if you answer the list's question, whether its count came out too much, about right or short, with that day. That is all. The answers are not saved — they are worked out again from your measurements every time you open the project, so a project can never disagree with a corrected calculator. What a shop's prices came to on the day you saved a list is kept only as a record of that day, to set beside the same shop's prices of today; nothing is worked out from it.

It is stored under the name buildbatch.projects.v1. You can see it in your browser's developer tools, under local storage.

To remove it: the projects page has a “Delete everything saved on this device” button, which removes all of it at once. Deleting a single project removes that one. Clearing this site's data in your browser settings does the same thing. Nothing we do can stop you: it is on your machine, not ours.

To keep it, or move it: the projects page can export everything to a file, and read that file back. The file is plain readable JSON, and it is yours — put it in your own backups, send it to yourself, or move it to another computer. An account, described next, is the other way to have the same projects on two devices.

If your browser is set to block storage, or you are in a private window, the projects page still works for as long as the tab is open and tells you that nothing is being saved.

If you create an account

An account is optional, and it changes one thing: where your saved projects are kept. The calculators, the planners, copying and printing work exactly as above, signed in or not, and BuildBatch sends your measurements, names and prices nowhere until you save them to a project. An account asks for an email address and a password, and nothing else: no name, no phone number and no address.

What the account stores

  • Your email address, to sign you in and to send the emails an account needs: one to confirm the address when you create the account, one with a link to choose a new password when you ask for it, and, if your account ever had to be closed, one from BuildBatch's own address to tell you first, where that is possible, as the terms say. There is no newsletter and no marketing email.
  • Not your password. The password you type is passed to the sign-in service, which checks it; BuildBatch never stores it. The sign-in service keeps only a one-way scrambled form of it (a hash), which cannot be turned back into the password.
  • The projects you save while signed in, and any you choose to copy in: the same things as in this browser (the project's name, each area's name, the measurements and product figures you typed, and your decisions on a list), with when each was created and last saved, and a version number so that two devices can tell which copy is newer. As in this browser, the answers are not stored: they are worked out again every time.
  • A deletion marker when you delete a project or an estimate: which one it was, by its identifier (a short code made when it was created, from the time and a random part) and not its contents, and when, so that your other devices remove it too.
  • What the sign-in service records about signing in: when the account was created and confirmed, when you last signed in, and a security log of sign-ins and account changes, which names your email address. Every sign-in request is made by BuildBatch's own server, which does not pass on your IP address or your browser's name, so the network details the sign-in service records are the server's, not yours.

How projects move between this browser and your account

While this browser is signed in, BuildBatch keeps the projects saved in it and the projects in your account the same. When you save, change or delete a project, the change is sent to your account, and projects saved on your other devices are fetched and added here. The requests go to this site's own addresses under /account/, which pass them to the database. They carry your projects' contents: that is what they are for.

  • Projects already on this browser are not uploaded when you sign in. They stay on this browser only, until you choose to copy them into your account from the projects page.
  • Nothing is thrown away without you seeing it. If the same project was changed on two devices before they caught up, both versions are kept: your account's version keeps the name, and this device's version is kept beside it, named “… (this device)”.
  • Deleting a project on one device deletes it on the others when they next catch up, unless another device has changed it in the meantime: then the newer work is kept.
  • Signing out. “Sign out” leaves this browser's copies of your projects where they are. The second sign-out button also removes your account's projects from this browser, which is the one to use on a shared or borrowed computer. Either way, your account keeps them: signing out also forgets what this browser had matched with your account, so a project you delete here after signing out is not deleted from the account.
  • The sign-in cookie, bb-account, set when you sign in. It keeps you signed in and is used for nothing else, so it is a strictly necessary cookie. When it is long, your browser may hold it in parts, named bb-account.0, bb-account.1 and so on. Its path is /account, so your browser sends it only with requests to the account's own addresses, never to the calculators, the planners or the other pages. It lasts 30 days, or until you sign out, and the page's scripts cannot read it.
  • Only while you choose a new password from an emailed link: bb_account_pw_grant, a one-use code that lets that page change the password without asking for the old one. It lasts 15 minutes, is sent only to the new-password page, and is also strictly necessary. The database keeps a matching record of it (whose it is, when it was issued and whether it was used), which holds no password and cannot be used again.
  • buildbatch.account.v1, in local storage: which account this browser is linked to (a random account number, not your email address), when it was linked, and which of the projects on this browser stay on this browser only. It is removed when you sign out, or when the site finds you are no longer signed in. A small script on each page reads it to show “Your account” instead of “Sign in”; it sends nothing.
  • buildbatch.sync.v1, in local storage: for each project and estimate shared with your account, a version number and a fingerprint of its contents, so that BuildBatch can tell what has changed since the two last matched. It never holds a project's contents, and this account's part of it is removed when you sign out.

Where it is kept, and who can see it

The account and its projects are kept in BuildBatch's database. The sign-in service and the database are run for BuildBatch by Supabase (Supabase Pte. Ltd., Singapore), which keeps it in its London region, on servers in the UK, under the data processing addendum that is part of its terms of service (published at supabase.com/legal/dpa). Where Supabase's own staff reach the data from outside the UK, that addendum's safeguard for such transfers applies: the UK Information Commissioner's addendum to the standard contractual clauses, acting as BuildBatch's processor: it holds the data on BuildBatch's behalf, to run the account, and not for its own purposes.

The two emails are sent by Brevo (Sendinblue SAS, France), from BuildBatch's own sending address at mail.buildbatch.co.uk, on servers in the European Union. For each email Brevo keeps a log (the address it went to, when, and whether it was delivered) for one month, and no copy of the email itself. Brevo also passes the email's link through an address of its own before it reaches BuildBatch's, and counts that the link was followed without tying the count to your address; on the plan BuildBatch uses, that cannot be switched off.

Only you, signed in, can read or change your projects: the database refuses anybody else's request for them. That includes BuildBatch's staff. A customer account is never a staff account, and the staff admin has no access to customers' projects. The one exception, as with any database, is whoever administers the database itself through the provider's own controls.

Why it is kept, and for how long

  • Lawful basis: contract. The account is a service you ask for, and your email address and your projects are what it takes to provide it (UK GDPR, Article 6(1)(b)). They are not used for anything else: no marketing, no profiling and no selling.
  • Kept until you delete the account. Deleting it deletes the account's sign-in record, with your email address, and your projects and their deletion markers, straight away. Two things can outlast it: the sign-in service's security log, which names your email address, and the provider's backups. On the plan BuildBatch uses, the sign-in service keeps its security log for an hour and its other logs for a day, BuildBatch's database does not copy them, and there are no backups, so nothing of a deleted account is left there after a day. Brevo's log of the emails it sent goes after a month.

Download it or delete it, yourself

The account page has both, and neither needs you to ask anyone.

  • “Download my data” gives you a file with your email address, when the account was created, every project in it and its deletion markers. It does not include the sign-in service's records; ask the contact below for those. It is plain readable JSON in the same form as the projects page's export, so any browser can read it back in.
  • “Delete my account” deletes the account and everything in it, as described above, once you have entered your password. It cannot be undone. Projects saved in your browsers are not deleted by it: each stays on its device as an ordinary saved project until you delete it there.

What the web host can see

This is the part that is easy to overstate, so to be exact: the calculator sends none of your figures, but asking for a web page is itself a request, and the computer serving it can see that request. That is true of every website.

The host can see things like the address of the page you asked for, the time, your IP address and which browser you used. Without an account, it cannot see the measurements you typed, because those never form part of a request: links that carry a room between tools keep the measurements after the “#”, which browsers do not send. Opening a saved project puts its identifier in the address: a short code made when the project was created, from the time and a random part, which does not include its name or contents. Without an account it means nothing outside your browser; with an account, the same code is stored with the project in your account, so the host's record of the page address could be matched to the account. With an account, the projects you save do form part of requests, to this site's own account addresses, and the host carries them on to the database.

The host: Cloudflare

BuildBatch runs on Cloudflare Workers, a service of Cloudflare, Inc., so every request to this site reaches Cloudflare's network. This is what Cloudflare's own privacy policy and documentation say about that.

The database: Supabase

The product catalogue, the usage totals described under counting what is used and the staff admin keep their records in a database run for BuildBatch by Supabase, in London (the region Supabase calls eu-west-2), chosen when the project was created on 28 September 2026 and fixed from then on. The site cannot be built without it. Your browser never talks to Supabase: when a page asks which products are published, this site's own server asks the database, and the question names only the calculator or the material. When a usage summary arrives, this site's server adds it to the totals in the same way. Supabase's own request log records that the server did so, and when, for as long as Supabase keeps such logs on BuildBatch's plan; the request comes from this site's server, so it carries neither your IP address nor your browser's name.

This section was written by AI tools on 28 September 2026 from Cloudflare's and Supabase's own pages, and completed on 29 September 2026 from what BuildBatch's Cloudflare and Supabase dashboards show. The person who runs BuildBatch published it on 30 September 2026 and is responsible for it.

Counting visits

To learn which pages are useful, BuildBatch counts visits with Cloudflare Web Analytics, a service run by Cloudflare, which also hosts the site. A small script of BuildBatch's own, served from this site, loads Cloudflare's counter script, from static.cloudflareinsights.com, unless you have asked it not to, as to stop it explains. Cloudflare's script sends its reports to cloudflareinsights.com. The private admin, the account pages and the page shown for an address that does not exist do not load it. This is what Cloudflare's own documentation says about it, and how to stop it.

The counter was switched on by a decision of the person who runs BuildBatch on 29 September 2026. It was written by AI tools on 28 September 2026 from Cloudflare's own pages, the counter's published script and the ICO's guidance, and the script was read again on 29 September 2026, unchanged. The person who runs BuildBatch published it on 30 September 2026 and is responsible for it.

Counting what is used

To learn which tools help and where people give up, BuildBatch counts how its pages are used. A small script of BuildBatch's own, served from this site, keeps a short summary of each page while it is open, in the page's memory only, and sends it when you leave the page or switch away from it, to this site's own address, /e. If you come back to the page, it later sends only what is new since then. It sends nothing anywhere else and loads nothing from anywhere else. The private admin, the account pages and the page shown for an address that does not exist do not load it.

Added in release 0.15.0, by a decision of the person who runs BuildBatch on 29 September 2026. They read its wording, and the wording of the sections on sending a list, tracing over a drawing and finding an item in a shop, on 30 September 2026.

Google Analytics, only if you say yes

BuildBatch uses Google Analytics to see which pages are visited, how people found them and what kind of device they used, in more detail than the two counts above give. It is the one thing on this site that sets cookies, so it asks first.

Why it is lawful. Analytics cookies are not needed to give you the pages, so the law asks for your consent before they are set, and for the personal data they produce the lawful basis is that consent. You can take it back at any time with the button above, as easily as you gave it.

When an assistant asks BuildBatch

An AI assistant that is helping you can ask BuildBatch for a shopping list on your behalf. It can fetch web addresses of this site: /plan.json, with the job and the room's measurements and choices, as the assistant understood them from you, written in the address, and /ask.json, which returns the questions an assistant should put to you and carries nothing of yours. An assistant using the Model Context Protocol can instead call /mcp; its plan_room tool sends the same measurements and choices in a JSON request body. This section says what happens to those requests. It does not say what the assistant, or the company behind it, does with what you told it or with BuildBatch's answer: that is under their privacy policy, not this page.

Added in release 0.17.0, written by AI tools on 30 September 2026. The MCP wording was added locally on 1 October 2026, the sentences about finding a guide on 7 October 2026, and the reason a refused request is counted with on 14 November 2026. The person who runs BuildBatch is responsible for it.

If you email BuildBatch

The site's one address is contact@buildbatch.co.uk. A message sent to it goes to BuildBatch's own mailbox, which only the person who runs BuildBatch reads. That mailbox is on Zoho Mail, provided by Zoho under Zoho's privacy policy.

This section was written by AI tools on 29 September 2026, when the address was first published. The person who runs BuildBatch published it on 30 September 2026 and is responsible for it. The mailbox moved to Zoho Mail on 6 October 2026, and AI tools changed these words that day from Zoho's own pages. On 8 November 2026 AI tools removed the paragraph about a message sent before that day, once the person who runs BuildBatch had deleted those messages and Cloudflare's 31-day records of them had gone.

If that ever changes

One change is possible later, and it has not happened:

It will not be added quietly. The change would appear on this page first.

Your rights, and who is responsible

UK data protection law gives you rights over personal data held about you: to see it, correct it, have it deleted, limit how it is used, object to it being used, and to complain to the UK's data protection regulator: the Information Commissioner's Office until 29 September 2026, and the Information Commission from 30 September 2026. Those rights need somebody to address them to.

The person responsible for this site under UK data protection law (the data controller) is Angelos Hallaci, who runs BuildBatch. BuildBatch's business address is 15B Raven Road, London E18 1HB. They are registered with the UK's data protection regulator as a data controller; the registration reference is ZC265595, and the regulator's public register can be searched for it. To ask about your data, to use any of those rights, or to complain about how BuildBatch has handled your data, email contact@buildbatch.co.uk. A complaint is acknowledged within 30 days.

Your right to object. Everything described on this page apart from the account, which rests on contract, rests on legitimate interests, so you can object to any of it: email contact@buildbatch.co.uk. Google Analytics is the exception: it rests on your consent, which you can take back at any time with the button under Google Analytics. For the visit counter there is also the button under counting visits, which stops the usage counts too.

Without an account, the site itself holds nothing about you, and the only records of your visit are Cloudflare's, described under what the web host can see and counting visits. The usage counts are daily totals with no identifier and no IP address in them. On a very quiet day, a day's totals can describe a single visit, which is why only BuildBatch sees them, in its private admin.

With an account, the site holds what is listed above. You can download your email address and projects, and delete the account and everything in it, yourself, at any time, from the account page, and correct a project by editing it. For anything else, or if something is not right, use the contact above.

The regulator's guidance for the public is at ico.org.uk/for-the-public.

How to check any of this

You do not have to take our word for it. Open your browser's developer tools, go to the network tab and reload a calculator page: every request goes to this site, apart from the visit counter's, unless you have stopped it: its script, from static.cloudflareinsights.com, and its reports, to cloudflareinsights.com, and, only if you accepted analytics cookies, Google's: its script, from www.googletagmanager.com, and its reports, to google-analytics.com. When you leave the page or switch away from it, one more request goes to this site's own address /e, carrying the usage summary, or what is new in it, unless you have stopped it: you can read exactly what it says there. A shop's link opens the shop in a new tab only when you tap it, so no request to a shop appears here until you do. Without an account, the application tab shows no cookies (unless Cloudflare has stopped this browser to check it, as the host's cookies explains), and no stored data until you choose a usual shop, save a project or stop the visit counter. Signed in, it shows the bb-account cookie on the account pages and the two account keys in local storage, and the requests that carry your projects go to this site too. BuildBatch's own code is plain, readable JavaScript that you can read in the same tools. The PDF reader, loaded only when you open a PDF to trace a room, is Mozilla's pdf.js, included as published: it is compressed, and its source is published by Mozilla at github.com/mozilla/pdf.js.

This page describes release 0.171.0. If you think it is inaccurate, tell us.