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.
- The links that are paid for. Five shops have accepted BuildBatch into their affiliate programmes, which the network Awin runs, and each of their links has the label “Ad” in front of the shop's name, where you see it before you tap. Since release 0.66.0 the wallpaper, lining paper and wallpaper paste lines also offer Wallpaperdirect: if you buy from Wallpaperdirect after following that link, BuildBatch is paid a commission, 3% of the basket before VAT and postage by the programme's terms as read on 6 October 2026. Since release 0.67.0 about forty ordinary lines (fillers, tapes, dust sheets, roller kit, safety gear, primers, and tiling and plasterboard sundries) also offer Travis Perkins: its commission is up to 3% of what you spend, less VAT and delivery, by its terms as read the same day. Since release 0.83.0 the building-material lines that no other paid link is offered for (plasterboard, plaster beads, loft insulation rolls, skirting, architrave, formwork timber, hardcore and levelling compound) also offer Materials Market: its commission is 3% of what you spend, excluding VAT, by its terms as read on 6 October 2026. Since release 0.162.0 the stain-blocking primer, primer or sealer, adhesion primer and mould treatment lines, and the paste brush, smoothing brush and seam roller among the wallpapering tools, also offer Decorating Centre Online: its commission is 3% of what you spend, 4% on an order from a new customer, or 1% where a voucher code is used, worked out without VAT and delivery, by its terms as read on 4 and 5 November 2026. The eaves ventilation, downlight cover, loft boarding, and pipe and tank insulation lines of a loft list also offer Insulation4less: its commission is 2% of what you spend, worked out without VAT and delivery, by its terms as read on 14 November 2026. No line offers more than one paid link. A paid link sits in its alphabetical place among the shops, and the list is the same whether you follow it or not.
- A shop's price. Under Travis Perkins' link, and since release 0.93.0 under Materials Market's link on the cement line of a mix on site, the list shows that shop's own price for one named product: the price its feed gave on the day shown, including VAT, with its delivery charge (Materials Market's feed gives none, and the list says so). BuildBatch reads it from a file the shop publishes for the sites it has accepted; it does not read the shop's website, and reading the file tells the shop nothing about you. A price is shown for 14 days after its day and then not at all; the shop's link to that product stays after those 14 days, without the price, and says that the shop's page has today's. It is one shop's price for one product on one day: BuildBatch does not rank shops, does not say a price is the lowest, and does not know what the shop charges today. Which product stands for a line was chosen with AI tools, for being the shop's plain, ordinary one and never for its price; no person has checked the choices yet. You buy from the shop, on its terms. Since release 0.71.0 a list also adds these prices up, line by line, as what the list costs at that shop, with the wall and ceiling paint in three kinds the makers name: vinyl matt, durable matt and diamond matt (until 17 October 2026, grades of one range each chosen by hand), each from the paint the shop sells, a step in the kind of paint and not a judgement of quality. Each total is one shop's own, before delivery. Where more than one partner shop prices a list, their totals are shown side by side, each with its day, in alphabetical order: they are never ranked, and nothing is called the cheapest.
- A product you pick in the planner. The products the planner offers to pick are a partner shop's own, from the same file of prices: each with that shop's price, the day it was read and its link marked “Ad”. Picking one sets the pack the list counts in. Since 14 November 2026 a product is shown with the shop's own picture of it where the shop's file gives one: your browser fetches it from this site, and the first time a picture is asked for, this site's server fetches it from Awin's image service and keeps a copy for up to a week. That request comes from this site's server and carries nothing about you: not your IP address, your browser's name, a cookie or the page you are on. Your browser asks nothing of the shop or of Awin until you tap the link, and the link is Awin's, as below.
- On a product's own page. A page under Products has “Where to buy it”: the same six shops' plain searches, for the product by its catalogue name, which earn BuildBatch nothing; and, where Travis Perkins' file of prices has that exact product in that tin size, its link marked “Ad” beside its price for it, with the day, the VAT and its delivery charge, shown for the same 14 days and then not at all. Which of the shop's products is that tin was matched with AI tools, from the product's whole name and its size; no person has checked the matches yet. Where no partner shop's file has that exact product, the page may offer a partner's link to a different product of the same kind, named as a different product and marked “Ad”. The page loads nothing from a shop or from Awin before you tap: the shop's picture of the product, where one is shown, is a copy kept on this site. A tap on a link marked “Ad” here is counted as one in the planner is, as below; a tap on a plain search is not counted. What is said here about where a paid link goes and what Awin records holds for these too.
- On a room-size table. A table under Examples of what a room needs by its size, where a partner shop prices the job's own material, has “What it costs today” under its table: what the table's example room costs at that shop, from the same file of prices, with the day, the VAT and its delivery charge, shown for the same 14 days and then not at all, and each product's link marked “Ad”. The page loads nothing from a shop or from Awin before you tap: the shop's picture of a product, where one is shown, is a copy kept on this site. A tap on one of these links is counted as one in the planner is, as below. The page's Markdown copy carries none of this. What is said here about where a paid link goes and what Awin records holds for these too.
- Where the link goes. Since 14 November 2026, first to this site's own address
/go/, which sends your browser straight on to Awin and keeps nothing about the request; then to Awin's click address (awin1.com), which passes you straight on to the shop: to Decorating Centre Online's, Insulation4less's, Wallpaperdirect's or Materials Market's own search for the same generic words, or to the named product's page at Travis Perkins or Materials Market. The address carries those words or the product's number, the programme's number and BuildBatch's publisher number, and nothing about you, your room or your list. It asks your browser not to say which page you came from. - What Awin records. Awin says it stores, for a click, a sequence of figures that does not reveal your name, with the advertiser, the publisher, that it was a click and in which country, and the device used; that it sets a cookie on its own tracking address when an advert is clicked; and that it keeps this tracking data for up to three years. If you buy, the shop tells Awin the value of the order, so that the commission can be worked out. Awin is Awin AG, in Berlin, Germany, and acts under its own privacy policy, on awin.com, which says how to object or to have a record deleted. From your tap on, Awin's and the shop's privacy policies and cookies apply, not this page.
- What BuildBatch does and learns. BuildBatch sets no cookie for these links, and your browser loads nothing from Awin or a shop before you tap. Awin tells BuildBatch how many clicks and sales there were and what commission is due; it does not tell BuildBatch who you are, and BuildBatch does not ask. In the planner, and since release 0.152.0 on a product's page and on a room-size table, BuildBatch counts a tap on a paid link in its own usage counts as it counts a plain search in the planner: which of the five partner shops, and which kind of item, added to separate daily totals, as counting what is used explains; never the product, its price, the line or the link's address. Since 14 November 2026 the tap is also counted when it passes through
/go/, by this site's server: one daily total made of the partner shop, the kind of item and the kind of page the link was on (a product's page, a room-size table, the planner, a list or the quote check), each from a fixed list, and nothing else. It is not counted when your browser sends Global Privacy Control or Do Not Track, or when the request names itself as a robot or a script; the address, the time and anything about you are not kept.
- Your usual shop. The list asks once which of those shops you usually use, with “No usual shop” as a choice. Your answer only changes the order: the shop you chose is first and the others stay alphabetical. It is not a recommendation. The answer is kept in this browser's local storage under
buildbatch.preferred-shop.v1, as the shop's fixed id or the wordnone. It is not sent to BuildBatch, a shop or anyone else, and it is not counted. Choosing again from the same list replaces it. - The kind of paint. Under a list, what it costs at a shop is shown for three kinds of white wall and ceiling paint from that shop's own products, named as their makers name them: vinyl matt, durable matt and diamond matt. The kind you choose lasts while the page is open and is kept nowhere: not in this browser and not by BuildBatch. Until 17 October 2026 it was kept in this browser's local storage under
buildbatch.paint-grade.v1; a value left there is no longer read. It is not sent to BuildBatch, a shop or anyone else, and it is not counted. - What BuildBatch counts. Not what you searched for, and not which line. When you open a shop's link in the planner, the usage summary says that a shop's link was opened, which of the six shops it was, or for a link marked “Ad” which of the five partner shops, and which kind of item it was for, chosen from a fixed list of 25 kinds such as paint, insulation, tools or safety gear. It adds one to a daily total for that shop and one to a daily total for that kind of item, as counting what is used explains. It never says which item, the search words, a colour, a measurement, a product or a price.
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 account's cookie, and what it keeps in this browser
- 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, namedbb-account.0,bb-account.1and 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.
- What it processes. When you use a website that runs on its services, Cloudflare processes your interactions with that site. That may include your IP address, how your traffic was routed, and other information about the traffic to and from the site.
- On whose behalf. Cloudflare handles the logs it makes available to BuildBatch, and what passes through its network, for BuildBatch and on its instructions (as a processor). For the rest of what it collects, Cloudflare decides the use itself (as a controller), under its own privacy policy. Cloudflare also keeps information it works out from traffic to run and protect its network, such as request volumes, error rates and threat scores for IP addresses.
- Where. Cloudflare says it mainly stores information in the United States and the European Economic Area, and that it may transfer and access it from other countries. What Cloudflare handles for BuildBatch in the United States goes there under the UK's adequacy regulations for the United States, through the UK Extension to the EU-US Data Privacy Framework, in which Cloudflare takes part; otherwise under the UK's International Data Transfer Addendum in Cloudflare's data processing terms.
- For how long. Cloudflare's privacy policy gives no fixed period. It keeps personal information for as long as its business purposes or the law need, then deletes it. Its data processing terms keep the personal data it handles for BuildBatch, which includes those logs, until BuildBatch's agreement with Cloudflare ends, or sooner once it is no longer needed.
- The site's own request log. Cloudflare can keep a log of each request that the site's own program on Cloudflare (its Worker) handles: the request and the response, with details Cloudflare adds, such as the country the request came from. If that log is switched on, Cloudflare keeps it for 3 days on its free plan and for 7 days on its paid plan. For BuildBatch it is switched off, and BuildBatch is on Cloudflare's free Workers plan: both were checked in Cloudflare's dashboard on 29 September 2026. The setting is written into the site's own configuration, so a new release cannot switch the log on unnoticed.
- The totals BuildBatch sees. Cloudflare measures every request it receives, with no script on the pages, and shows BuildBatch the totals. For the site's Worker, that is how many requests there were and how many failed, for up to three months back. Because the site is on its own domain, Cloudflare also shows the number of requests, the amount of data sent, the number of unique visitors and the requests from each country. It counts visitors by their IP addresses, and the totals include bots and crawlers, not just people. Cloudflare's security dashboard also shows BuildBatch a sample of single requests from the last 7 days (the time, the IP address, the page, the country and the browser), and a sample of the requests its protections acted on from the last 24 hours. BuildBatch looks at them only to keep the site working and safe.
- Reports of failed requests. Every page tells your browser that, if a request to this site fails because of a network problem, it may report the failure to Cloudflare (Network Error Logging). The report goes to Cloudflare, not to BuildBatch. Cloudflare says it works out the network, the country and the area the report came from, keeps your IP address only in memory while it receives the report, and does not log it.
- Why, and on what basis. To serve the pages and to keep the site working and safe. Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)): a page cannot be served without the request for it, and a site has to be protected from attacks.
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.
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.
- What it sends. Timings from your browser: how long the page took to load and to appear, and how quickly it responded when you used it, with how much memory it used. With them go the page's address, the address of the page that linked to it, a random code made in your browser for that one page view, and the names and versions of your browser and operating system. For the slowest moments, it names the part of the page involved, such as a button, by its name in the page's code.
- Not what you type. It measures how the page behaves, not what is in it or what you enter. Cloudflare says Web Analytics does not log the part of an address after “?”. We also read the counter's script as Cloudflare published it on 2 September 2026: it removes the part after “?” and the part after “#” from both addresses before sending them, so the measurements that links carry between the tools are not sent. Cloudflare can change the script at any time, so this is checked again whenever this page is reviewed.
- No cookie, and nothing kept in your browser. Cloudflare says the script stores nothing in your browser and reads no cookie or other stored data. So the counter adds no cookie. BuildBatch's own script, which loads it, looks for one thing in this browser's storage: whether you have asked for your visits not to be counted, described next.
- Your IP address. As with any request, each report reaches Cloudflare from your IP address. Cloudflare says the counter drops the address at the nearest Cloudflare data centre and does not keep it in its main databases or logs. Cloudflare also says the reports may be handled in a different country from the one they came from.
- What BuildBatch sees. Totals, not people: page views and visits for each page, the websites that sent people here, and totals by country, browser, operating system and kind of device, with how quickly the pages loaded. Cloudflare says it does not track individual people across the websites that use it. BuildBatch also sees the totals Cloudflare shows it as the host, described under what the web host can see.
- Why, and on what basis. To learn which pages are useful, so that the site can be made better. Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)). You can object at any time, as the next items say.
- For how long. Cloudflare keeps every report in full for 7 days, then keeps about a tenth of them. BuildBatch can look back six months. Cloudflare's documentation does not say when that tenth is deleted.
- To stop it. Use the button under this list, “Stop counting my visits and my use of the tools on this browser”, which also stops the usage counts described next. It is free and it works on this site itself: from the next page you open, BuildBatch's own script no longer loads the counter in this browser, so the counter sends nothing from it. “Count my visits and my use of the tools again” undoes it. The choice is kept in this browser's local storage under the name
buildbatch.visit-counter.v1, not in a cookie, and it applies to this browser only: on another browser or device, use the button there too. To know your choice, BuildBatch's script looks for that one name each time a page loads, and reads nothing else there. If your browser sends the Global Privacy Control signal, BuildBatch takes it as the same choice and does not load the counter while the signal is on. A browser that will not let this site look in its storage is not counted either, and nor is one with JavaScript switched off. Cloudflare says ad blockers block the counter's script, including Adblock Plus, Brave and the DuckDuckGo extension. However the counter is stopped, every page and tool works as before.
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.
- What a summary can say. Only choices from fixed lists. The kind of page: the home page, the job planner, the room planner, the paint, wallpaper, tile, floor tile, flooring, skirting board, plasterboard, carpet, sheet vinyl, loft insulation, concrete, patio, MOT Type 1 or gravel calculator page (each of them the job planner on that job), the earlier flooring calculator, the list of calculators or of guides, which guide, the projects page, a products page, a room-size table (never which), an information page such as this one, a list opened from a link, the planner filled in from a link or, on the home page, once a list is worked out for your own sizes, once a size is typed, once the box for describing the job is used, once a saved list's question on how its count came out is answered, or once the example room's list, a shop's link, the product pick or the sheet for a tradesperson is used, the page on how list links work, or another page. Where the visit came from, worked out from the address of the website that linked here, or from a utm_source tag in this page's own address (never on a list or start link), and reduced to one of a fixed list: an AI assistant (ChatGPT, Perplexity, Claude, Gemini or Copilot, each named), a search engine, a social site, another website, another page of this site, or none. Whether the window is phone-sized, tablet-sized or larger. Roughly how long the page was open: under 10 seconds, under 30 seconds, under 2 minutes, under 10 minutes, or longer. And, in the planners and on the projects page: which job was chosen (paint, flooring, carpet, loft insulation, both, paint and carpet, skirting and architrave, plasterboard, a concrete slab, a patio, or sub-base and gravel, and whether the walls are painted, papered or tiled), how the planner was opened (at the start, with a job already chosen, carrying a room from another tool, reopening a saved list, from a list link, or from a guide's box for your room in your own words: that it was, never the words or the sizes), which steps were reached, whether a size was typed in the planner (once a visit, whether or not a list could be worked out from it yet: never the size, and never which box), whether a list was worked out, which buttons were used (copying the buying list or the price request, printing the list, saving to a project, opening a reviewed offer, marking a line Need, Check first, Have or Not needed, and changing the units; on the room planner, printing or downloading a drawing, copying its measurements and carrying it into the job planner; on the projects page, exporting or importing projects), whether a room was drawn, whether a room was traced over a drawing, whether a list was sent as a link (copied or shared), whether the shopping checklist was opened, whether “Pick the actual product” was opened and whether a search in it found nothing (that it happened, never the words typed), whether typical door and window sizes were chosen and roughly how many times (once, 2 or 3 times, or 4 or more, as it stood the first time the page was summarised after one was chosen), whether a room was started from a typical room (a yes or no: never which room, and never its size), whether the sheet for a tradesperson was opened from the planner (a yes or no: never the list it carries), whether “I would buy one” was tapped under a decorating list's tools, to the question whether you would buy a kit of them from BuildBatch (a yes or no, by job: nothing is on sale, and nothing else is asked or kept), whether the box for describing the job was used, whether anything was read from it or a question asked back and which kind, never the words (the kinds are which job, which unit, walls or floor for tiles, which vinyl and which gravel; what is typed in the box is read on your own device, and this site sends it nowhere and keeps it nowhere), on a saved list, if you answer it, whether a saved list's count came out too much, about right or short, as one of three words by job, never a figure, which unit of measurement was in use, whether products came from the catalogue, were typed in or were a quick estimate, and which kinds of problem the form pointed out, such as “the room length is missing”, by a code. On a list opened from a link, only whether it was sent on and whether its shopping checklist was opened. On a product's page and on a room-size table, only the partner shop and the kind of item of a link marked “Ad” that was opened, as described under shop links, below.
- Shop links. In the planners, two more facts when a “Find it at” link is opened: which of the six shops it was for, and which kind of item it was for, as finding an item in a shop explains. The kind is one of a fixed list of 25: Wall and woodwork paint; Ceiling paint; Primer, sealer and treatments; Filler; Caulk and sealant; Sanding and abrasives; Sugar soap and cleaner; Masking tape; Dust sheets; Brushes, rollers and trays; Other tools; Safety gear; Wallpaper and lining paper; Wallpaper paste and size; Tiles; Tile adhesive and grout; Tile spacers, trim and waterproofing; Flooring; Underlay, membrane and tape; Flooring fixings, spacers, beading and door bars; Skirting, architrave and fixings; Plasterboard and finishing materials; Loft insulation and accessories; Concrete, aggregates and formwork; Paving slabs, bedding and jointing. It is never the item itself, the search words, the line, the list, a colour, a measurement, a product, a price or the shop's address. The shop and the kind are added to separate daily totals, so the totals cannot say which kind of item was looked for at which shop. The same two facts, kept apart from these, when a link marked “Ad” is opened in the planner (since release 0.115.0), on a product's page or on a room-size table: which of the five partner shops it was for (Decorating Centre Online, Insulation4less, Materials Market, Travis Perkins or Wallpaperdirect), and which kind of item, from the same list; never the product, its price, the line or the link's address. It is not counted at all on a list opened from a link.
- What it never says. No measurement, name, price, note or anything else you type; no web address and no search words; nothing about a project; nothing about a drawing you trace over, not its file, its name, its size, its scale or the corners you mark; no list link and nothing in one; no door or window size; nothing about your device beyond phone, tablet or larger; no time of day. The request that carries it sends no cookie and does not carry the page's address: the kind of page, from the list above, is in the summary itself. There is no identifier, and nothing is kept in your browser: nothing links one page to the next or one visit to another, so BuildBatch cannot tell whether two summaries came from the same person.
- What is kept. Totals for each day, and nothing else. When a summary arrives, the site adds one to a few daily totals, such as “job planner pages opened from Google on a phone” or “planner pages where the buying list was copied”, and keeps nothing of the summary itself: not your IP address and not your browser's name; the day is the only time kept. Calls to the assistant interface are added to the same kind of daily total, as when an assistant asks BuildBatch explains. A day holds at most 1,500 different totals, so made-up summaries cannot fill the database. The totals are kept in BuildBatch's database, described under the database, for 26 months. Older days are deleted automatically on the first day something is counted after they turn 26 months old; if counting is ever switched off, the person who runs BuildBatch deletes them by hand when they reach that age.
- Your IP address. As with any request, the summary reaches Cloudflare's network and this site's server from your IP address, as what the web host can see explains. BuildBatch does not store it or log it.
- Who sees it. The totals are for BuildBatch alone. There is no identifier in them, but on a very quiet day a day's totals can describe a single visit. So they are shown only in BuildBatch's private staff admin, and are never made public, shared with or sold to anyone. The admin shows each total added up over 7 to 90 days, today included, and one number for each day: how many pages were counted that day. Staff who sign in to the admin with a second step (MFA) can also read each day's totals on their own. Supabase keeps them for BuildBatch, on its instructions, with the rest of the database.
- Why, and on what basis. To learn how the site is used, so that it can be made better, and for nothing else. The law on storing and reading information on your device (the Privacy and Electronic Communications Regulations, Schedule A1, paragraph 5, in force since 5 February 2026) lets a site do this for that purpose without asking first, as long as it says so clearly, shares the information only to help improve the site, and gives you a simple, free way to object. For the request itself, the lawful basis is legitimate interests (UK GDPR Article 6(1)(f)).
- To stop it. The same button stops both: “Stop counting my visits and my use of the tools on this browser”, under counting visits. It is free, and it works on this site itself. From then on no summary is collected or sent from this browser, not even from a page that is already open. “Count my visits and my use of the tools again” undoes it. Global Privacy Control and Do Not Track, if your browser sends either, stop it too, and so does a browser that will not let this site look in its storage, or one with JavaScript switched off. However it is stopped, every page and tool works as before.
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.
- It is off until you accept. One line, after the planner's answer or after a page's own answer (on some pages well down the page), asks once: “Yes” or “No thanks”. Until you press “Yes”, nothing of Google's is loaded, no cookie is set and Google is told nothing. “No thanks” is remembered, and you are not asked again in this browser.
- You are not asked at all, and it stays off, if your browser sends Global Privacy Control or Do Not Track, or does not let this site keep your answer.
- The cookies. If you accept, Google's script sets two cookies on this site's address:
_ga, which Google says is “used to distinguish users”, and one whose name starts with_ga_, “used to persist session state”. Each holds a random number, not your name or anything you typed. Google's default is to keep them for two years; this site sets them to last 395 days from your last visit. - What Google is sent. For each page you open: the page's address and title, which site you came from (its name, not the page; for a page of this site, its address), the time, your browser, device type, screen size and language, and the number in the cookie. Your device's internet address reaches Google as it reaches any website; Google says that for visitors in the UK it uses it only to work out an approximate location (such as the town) and then discards it without storing it.
- What Google is never sent. The words and figures you type into a planner or a calculator: no measurement, name, price or note is passed on, and no drawing. The page's address is cut before it is sent: everything after “?” is removed except the labels that say which campaign or site a link came from, and nothing after “#” is sent, so a list sent as a link is never passed on. On the page that opens a list and the page that starts one from a link, only the page's own path is sent.
- No advertising. The advertising features of Google Analytics (“Google signals” and ad personalisation) are switched off in the script this site runs, and the browser is told not to let the page contact Google's advertising addresses at all. BuildBatch shows no adverts other than the shop links marked “Ad”, and builds no profile of you.
- Who holds it. The figures are kept by Google, which acts on BuildBatch's instructions as its processor under Google's data processing terms, and may process them on servers outside the UK. Google's own description of what it does is at How Google uses information from sites that use its services.
- How long. Google keeps the detailed records for the shortest period it offers, two months, and totals after that. Your answer to the question is kept in this browser's local storage under
buildbatch.analytics-consent.v1, as the wordgrantedorrefused, until you change it or clear the browser's data. - To change your mind. Use the button under this list. Turning it off deletes the two cookies from this browser and stops the script on this page; later pages do not load it.
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.
- What the assistant sends. For
/plan.json, whatever it puts in the address, such asjob=paint&length=4.2. An address includes everything after a question mark, so Cloudflare's own records of the request, and the sample of single requests that it shows BuildBatch for 7 days, may include those measurements. For/mcp, the same kind of figures are in the request's JSON body instead of its address; to find a guide, the body holds the words of a question instead, as the assistant wrote them, which BuildBatch matches against its guides' titles and answers and then drops. In both cases the request reaches Cloudflare's network and this site's server like any other, as what the web host can see explains. BuildBatch looks at Cloudflare's sample only to keep the site working and safe, and does not search it for measurements. - What BuildBatch does with it. It works the list out on this site's server from the address or JSON body, with the same code that the planner runs in your browser, and sends the list back. It does not store the address or request body, the measurements, the answer, the caller's internet address or the name the caller gives itself (its User-Agent header), and it keeps no log of the request: the site's own request log is switched off, as the host explains. It sets no cookie and reads none. The answer can only be as good as what the assistant sent: BuildBatch cannot tell whether the assistant got your measurements right.
- What BuildBatch counts. One daily total for each request for questions or a list, made of three words from fixed lists: what was asked (the questions, a list, or a list that was refused because a figure was missing or could not be used), which job (paint, flooring, carpet, loft insulation, paint and flooring, paint and carpet, skirting and architrave, plasterboard, a concrete slab, a patio, sub-base and gravel, or none), and which kind of caller it was (ChatGPT, Claude, Perplexity, Gemini, Copilot, another AI assistant, a web browser, an MCP tool call, or something else). A request that was refused carries a fourth word from a fixed list of eight, saying why: nothing was sent, no job was given, a job BuildBatch does not plan, an argument it does not take, a value it could not read, a measurement missing, a measurement out of range, or a product's own figures missing. It is the kind of reason only, worked out from the refusal: never an identifier, and never the words or figures that were sent. An MCP tool call is known from the address it used. For the other addresses, the kind is worked out from the name the caller gives itself, which anyone can set to anything, so it is a guess; the name is read and dropped, never kept. Opening the MCP connection, asking which tools it has and searching for a guide are not counted. Nothing else is counted: no measurement, no part of the answer and no time of day. The totals are kept as counting what is used explains: for each day, at most 1,500 different totals, for 26 months, and read only in BuildBatch's private staff admin. A caller that sends Global Privacy Control or Do Not Track is not counted. The button under counting visits is for a browser, and an assistant is not one: to object to these counts, email contact@buildbatch.co.uk.
- The link in the answer. The answer includes a link to this site's list page, with the same figures after “#”. It works like any list link, as sending a list as a link explains: the figures are in it, so it is as private as wherever it is pasted.
- Who else sees it. The assistant's company sees your conversation and the answer it fetched. BuildBatch has no arrangement with any assistant or the company behind it, and earns nothing from these calls. It shows no price and no advertisement in an answer.
- Why, and on what basis. To answer the request, and, when counted, to learn whether assistants use the interface and which jobs they ask about, so that it can be made better. Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)). To object, email contact@buildbatch.co.uk.
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.
- What BuildBatch keeps. Your email address, your name if your email carries it, and what you wrote. They are used only to deal with what you wrote about and to answer you: you are not added to any list, and your message is not passed to anyone else.
- For how long. Until what you wrote about is dealt with. Then your message and BuildBatch's reply are deleted from the mailbox, its Trash included; Zoho keeps a deleted message for a further 30 days, when it can still be recovered, and then removes it for good.
- Where. Zoho keeps the mailbox in its European data centres, in the Netherlands and Ireland, two countries that UK law treats as protecting personal data adequately. Zoho's own companies in the United States and the other countries where it operates can be given access to run the service, under an agreement between them based on standard contractual clauses. Cloudflare no longer handles BuildBatch's email.
- Why, and on what basis. To deal with what you wrote about and to answer you. Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)): you asked for an answer, and nothing else is done with your message.
If that ever changes
One change is possible later, and it has not happened:
- Links that earn money. Five shops' links do, each marked “Ad” where you can see it before you tap it: Decorating Centre Online's, on the primer, sealer and mould treatment lines of a list and on three of its wallpapering tools, Insulation4less's, on the eaves ventilation, downlight cover, loft boarding, and pipe and tank insulation lines of a loft list, Wallpaperdirect's, on the wallpaper, lining paper and wallpaper paste lines of a list, Travis Perkins', on the lines where it shows its own price, and Materials Market's, on building-material lines such as plasterboard and loft insulation rolls, and with its own price on the cement line; a partner shop's, beside its own product that you can pick in the planner; and a partner's again under “Where to buy it” on a product's page, for that exact tin where its file of prices has it, or for a different product of the same kind, named as a different product; and under “What it costs today” on a room-size table whose example room a partner shop prices. The links that are paid for says where they go and what is recorded. The “Find it at” links to the six other shops earn BuildBatch nothing, as finding an item in a shop says. No other link on this site is paid for; if one is ever added it will be marked “Ad” in the same way, and this page will name it first.
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.