What we store, and what we do not.
Buildlas has no accounts, no advertising and nothing that follows you between visits. It puts two things on your device, both of which are the feature you came for. It counts how many people read each page, in a way that cannot tell one reader from another and that stores nothing on your device to do it. This page was last checked against the code on 2026-08-02.
On your device
| What | Why | How long |
|---|---|---|
Your countryA cookie named buildlas_region, holding a country code | So prices show in your currency and the safety and registration rules shown are the ones that apply to you. Written only when you choose a country from the selector in the header; nothing is guessed from your address or your connection. | One year, or until you clear it |
| Your buildA browser storage entry holding the parts you picked | So the build you assembled is still there when you come back. It is a list of product references and quantities. It never leaves your browser: we cannot see it, and it is not sent to us. | Until you clear the build, or clear your browser data |
Clearing the build in the planner deletes the second entry outright rather than emptying it. Nothing is written at all until you have put something in a build, so a visit where you only read costs you no storage.
We count pages, not people
We keep a running count of how many times each page was opened, so we can tell whether anyone is reading this and whether that number is going up. That is the whole purpose, and the way it is built is the reason it can be described in one table:
| What we record | Example |
|---|---|
| The day | 2 August 2026 |
| Which page | /learn/video-systems. The address only, never the part after a ?: a planner link carries your whole build, and it is removed before anything is counted. |
| Which site you came from | google.com. The site's name, not the page you were on and not what you searched for. |
| The country you chose | SE, if you picked one in the header. Your own choice, still never a guess from your address. Blank for everyone who never touched the selector. |
| A number | How many times that combination happened that day |
There is no entry for you in any of it. No identifier is created, no cookie is set, nothing is written to your browser, and no request leaves this site to make it happen: the count is added up on our own server as it answers a request it was already answering. The smallest thing a row can say is something like “this guide was opened 17 times on Tuesday by people arriving from Google”. It cannot say whether that was seventeen people or one person seventeen times, and there is nothing to join it to that would.
We also count clicks out to a shop, as a daily total, so we can tell whether the recommendations are of any use. That count records which shop, whether the link earns us a commission, whether it went to a product page or a search, the CATEGORY of part it concerned, and which part of this site you pressed it on.
It does not record which product, and that is a line rather than an oversight. Category is a group of twenty; a product is one thing you were looking at, and a click count beside a named product starts to describe an individual’s shopping on a day when the total is one. So the row says “someone bought a motor link today”, never “someone clicked this motor”. It records no identifier of any kind and there is nothing to join it to that would.
Search engines and other robots are counted separately. Most of what visits a small site is automated (search engine crawlers, link checkers, and our own deployment tests), and counting those as readers would make the numbers above meaningless. To tell a robot from a person we read the browser identification that every browser and every crawler sends with each request. We do not store it. What we keep is a daily total against the name the robot gives for itself, like googlebot, and those visits are left out of the page counts above.
These totals are kept indefinitely, because comparing this year with last year is the only reason to have them and because there is nothing personal in them to expire. The server logs described further down are a different thing, they do contain IP addresses, and they are still deleted after two weeks.
Product images load from Banggood
This is the one thing on the site that contacts somebody else. Product photographs are supplied by Banggood's affiliate programme and are served from their image servers rather than ours. When a page shows one, your browser fetches it from Banggood, and in doing so tells them your IP address, which browser you use, and which Buildlas page you were looking at.
That happens as the page loads, before you click anything. We do not send them your build, your country choice, or anything you have typed, and we get nothing back about you. But we cannot promise that Banggood does not record the request, and it is their servers, not ours.
We would rather serve these images ourselves, which would stop your browser contacting them at all. That needs the programme's permission to host their images rather than link to them, and until we have it in writing this page tells you what actually happens instead of claiming something tidier.
Why there is no cookie banner
European rules require consent for storing things on your device unless the storage is strictly necessary for something you asked for. A preference you set yourself and a basket you filled yourself are the two textbook examples of that exemption, and they are the only two things here. A banner offering you a choice between necessary and necessary would be theatre, and it would train you to dismiss the banners that do matter.
The exemption is about what is stored on your device, and the product images above store nothing here: they are pictures, not trackers, and we set nothing on Banggood's behalf. What they do is reveal your address to a company you did not choose to contact, which is why it has its own section rather than a footnote.
The counting does not change this answer, and it is worth being precise about why. The rule is about writing to your device, and none of the counting writes to it: no cookie, no storage entry, nothing that persists after you close the tab. Page views are counted entirely on the server, from a request that was already being served.
Clicks out to a shop do run a small script, and here is exactly what it does. When you press a link to a retailer,about ten lines of JavaScript send us five short facts: the shop, the kind of link, the category of part, whether the link earns us a commission, and which part of the site you pressed it on. It sends no identifier, reads nothing from your browser, and stores nothing: it is a message, not a mark. We count it because a link that nobody follows and a link that does not exist look identical from here, and without that number there is no way to tell whether any of this is useful to anyone.
If that ever changes, you will be asked first. The moment this site wants an advertising pixel, a hosted analytics script, a third-party script of any kind, or any counting that could pick you out of the total, consent comes before it happens, refusing is one click like accepting, and this page says so before it happens.
What we do not do
- No analytics product, no session recording, no heatmaps. The page counting described above is our own, runs on our server, and produces daily totals rather than a record of anyone's visit.
- No advertising networks, no tracking pixels, no fingerprinting.
- No visitor id, no session id, nothing that recognises you when you come back.
- No accounts, so nothing is tied to a person.
- No external fonts, no tag manager, no embedded widgets. With one exception, described below, loading a page here contacts this site and nothing else. You can confirm that in your browser's network tab.
- No guessing your location from your IP address. You tell us, or we do not show country rules at all.
Links to shops
Product links point at retailers and manufacturers, and some of them earn us a commission, which is marked on the link itself. Following one takes you to that company's site, where their own cookies and their own privacy policy apply. We are not told what you look at there or what you buy, and no tracking of ours runs on their pages.
The affiliate disclosure covers the money side in full: which links earn a commission, how many there currently are, and what a commission does not buy.
If you send feedback
The feedback form stores what you wrote, which product it was about, and a short technical note about the page you were on and the browser you used, so a report can be reproduced. Your IP address is held in memory for about twenty seconds to stop automated flooding and is not written down.
Please do not put personal details in the message box: there is no reason for us to have them. If you did, write to support@gustalabs.com and we will take the report out.
Sharing a build
The share button puts the parts list into the address bar rather than saving it on our servers. That means the link itself contains the build, and anyone you send it to can open it. It also means we hold no copy.
Server logs
The servers that run this site keep short-lived operational logs, as every web server does. Those can include your IP address, the page requested and the time. They exist to keep the service up and to investigate errors and abuse, they are kept for two weeks, and they are not used to build any picture of you.
Your rights, and how to use them
Under the GDPR you can ask what we hold about you, ask for it to be corrected or deleted, and complain to a supervisory authority. In practice almost everything here is already in your own hands: the two entries above are on your device and you can delete them without asking anyone.
For anything that is not, write to support@gustalabs.com. That is a real mailbox, read by the people who build this.
In Sweden the supervisory authority is Integritetsskyddsmyndigheten (IMY, imy.se); elsewhere in the EU it is your own national authority. You can complain to them without going through us first.
Who we are
Buildlas is built and run by Gustalabs, in Sweden. Questions about this page, about the site, or about anything else: support@gustalabs.com.