Privacy

What Botlero collects, in full

Almost nothing. There are no cookies, no analytics, no trackers and no third-party scripts on this site, and there is no account to create. Two optional forms — suggesting a robot and joining a notify-me list — do store what you type into them, and that is disclosed plainly below rather than folded into the rest. Everything else on this page is about what happens when you simply read a page, which is what almost every visit here is.

Cookies

Botlero sets no cookies at all — not for analytics, not for preferences, not for “essential” purposes. That is why this site has no cookie banner: there is nothing to consent to. You can confirm it in your browser's developer tools, on any page, under Application → Cookies.

What your browser stores, and it never leaves your browser

Four preferences are kept in your browser's own localStorage. They are written and read only by the page you are looking at, are never transmitted to Botlero or to anyone else, and are not visible to the server — which is precisely why they are stored this way rather than in a cookie, since a cookie would be sent with every single request. Clearing site data in your browser removes all four.

• botlero:theme Whether you chose the light or the dark theme.
• botlero:units Whether you chose metric or imperial. Both systems are already in the page; this only decides which one is shown.
• botlero:compare The robots you ticked for comparison, as a list of page names.
• botlero:saved The robots you bookmarked, as a list of page names.

Every one of those reads and writes is wrapped so that a browser which refuses storage — private browsing, or storage disabled — simply loses the preference rather than breaking the page.

Analytics, tracking and advertising

There are none. No Google Analytics, no Tag Manager, no Vercel Analytics, no Plausible, no PostHog, no Sentry, no advertising or remarketing pixel, no session recording, no heatmap, no A/B testing tool and no fingerprinting. The project has no analytics dependency installed at all, so there is nothing to switch on by accident. Botlero therefore does not know how many people visit it, which is a cost the site accepts rather than a claim it makes.

Requests to other websites

Most of a page on Botlero sends no request to any third party: there are no external scripts, stylesheets, fonts, iframes, embedded videos or map tiles, and the typefaces are served from this domain.

One exception, added 2026-10-04: a robot page or listing card may show a real photograph of that robot. Where one is shown, your browser loads it directly from the manufacturer's own server the moment the page renders — the same request a click on a link would make, except automatic rather than on click. Nothing is copied onto Botlero's own servers; see About & method for why that is not the same thing as re-hosting it. That request carries this site's referrer policy (strict-origin-when-cross-origin), so the manufacturer learns only that the request came from botlero.com, not which robot's page you were on — plus whatever your browser always discloses on any request, its IP address and user agent. Where a photo cannot be shown this way (a manufacturer that blocks direct loading, or none exists), the page links to it instead, as every robot page always has.

A second exception, added 2026-10-08, is a different shape: your browser never contacts it at all. If you submit the newsletter form (footer or /newsletter), your browser sends the address to Botlero's own server, same-origin, exactly like any other form on this page. Botlero's server then passes that address to Resend, which is who actually sends the confirmation email and, once you confirm, any later newsletter mail — Resend is the one place this project's own infrastructure hands a visitor's data to a third party rather than your browser doing so directly. See how this actually works for the confirmation step, and Resend's own privacy policy for what it does with an address beyond delivering that mail.

A robot page also contains many plain links to other websites — that is the point of the site, since every value cites the page it came from. A link fetches nothing until you click it. When you do click one, your browser tells that site only that you came from botlero.com and not which page you were on, for the same referrer-policy reason. After that you are on someone else's site, under their privacy policy, and Botlero has no visibility into it.

What the host necessarily sees

Botlero is served by Vercel. Like any web host, Vercel receives the technical details a request cannot be answered without — your IP address, the page requested, your browser's user-agent string and the time — and processes them to deliver the page and to keep the service up. That is the whole of the data handling involved in serving this site, and Botlero adds nothing to it: no logging of its own, no user profiles, no enrichment, no sale or sharing of anything. What Vercel itself retains, and for how long, is governed by Vercel's own privacy documentation rather than by this page, and this page does not guess at it.

What Botlero's database actually holds

Mostly, specifications of humanoid robots and facts about the companies that make them, each stored with the URL it was read from, the verbatim sentence that states it, and the date that sentence was last seen on that page. Everything in it is already published on a public page elsewhere, which is exactly why every value can show you where to check it. The one exception — what you type into the two forms described next — is the only visitor data anywhere in this database, and it exists only because you chose to submit it.

If you submit a robot or join the notify-me list

These are the only two places on the site where typing something in causes it to be stored. Both write to a collection that is separate from the robot data above — neither ever becomes a published value on a robot page by itself, for the same reason described on Submit a robot: nothing here has passed the evidence checks every published number has to.

• Submit a robot. The robot's name, and whatever else you choose to fill in — a manufacturer name, a link, a note, and an email address if you want to hear back. All four besides the name are optional. It is read by the site's maintainer as a lead, the same way a candidate name is picked for review before the data pipeline ever touches it — see Submit a robot for what actually happens to it.
• Newsletter. An email address, which form you used (the footer or the newsletter page itself), and three dates — when it was entered, when it was confirmed (if it ever was), and when it unsubscribed (if it ever did). Nothing is sent until a confirmation link is clicked; see how this actually works for the double opt-in flow and the one-click unsubscribe link every later email carries.
• How abuse is stopped without tracking you. Both forms use an invisible field a real visitor never sees or fills in, and reject a submission that arrives implausibly fast after the page loads. On top of that there is a coarse, site-wide cap on how many submissions either form accepts per hour, and the newsletter form specifically will not re-mail the SAME address more than once an hour, which stops it being used to mail-bomb someone else's inbox. None of that needs your IP address or any other identifier, so none is stored — the same position as everywhere else on this page.
• How long it is kept. A suggestion until the maintainer has reviewed it; a newsletter address until you ask to be removed or until the unsubscribe link in an email is used, which only marks the address unsubscribed rather than deleting it — see the correction route below to have it deleted outright.

Search, filters and comparison

The filter panel on the robot list and the comparison picker both submit with GET, which means your choices end up visible in the address bar and nowhere else. Nothing is stored about what you searched for, filtered by, or compared. The share button on a robot page hands the page's URL to your operating system's own share sheet, or to your clipboard, without Botlero seeing it. The two forms described above — submitting a robot and the newsletter — are the only forms on the site that submit any other way, and the only ones that store anything.

Children

This is a reference site about industrial and consumer robots. It is not directed at children, and it collects nothing from anyone regardless of age beyond what is described above — which requires typing into one of two optional forms, not simply visiting.

Your rights, and why there is little to exercise them against

Rights of access, correction, erasure, portability and objection apply to personal data that a site holds about you. Botlero holds almost none: no account, no cookie, no analytics record, and the four preferences above live in your browser rather than on the server, where you can delete them yourself at any moment without asking anyone. The one exception is whatever you typed into the robot-suggestion or newsletter form, if you used either — ask below and it is removed. If you believe something here nevertheless identifies you, or a quotation from a public page mentions you and should not, say so too and it will be looked at.

Questions, and a correction route

Corrections to a robot's data and questions about this page use the same route. Report it. The About page explains who is responsible for the site, and the terms cover what you may do with what you read here.

Changes to this page

This page describes the code that is currently deployed, and it is part of that code: if the behaviour changes, the page changes in the same release. Last reviewed 8 October 2026. There is no mailing list to notify, because there is no mailing list.