Privacy policy
Shopfloor collects no accounts and runs no advertising. It uses Google Analytics 4 for aggregate traffic. Details of what the server necessarily sees.
Short version: Shopfloor has no user accounts, no comments, no newsletters and no advertising. It uses Google Analytics 4 to count visits in aggregate, which sets two optional cookies you can block (see the cookie policy). Reading the site requires no personal data and we build no profile.
What the server necessarily processes
Like every web server, the hosting server processes standard connection data to deliver pages: the requested URL, date and time, a truncated network identifier, and the browser-supplied user agent. This lives in routine server logs used for operations and security, and is not sold, shared, or used for profiling.
Analytics
Google Analytics 4 (Google LLC) receives the pages you view, your approximate location from the IP address, device and browser type, the referrer, and a random identifier kept in its cookies. We use it only for aggregate traffic reports. You can block it in your browser or with Google's opt-out add-on.
What the site itself stores
Nothing else about visitors. The site's server-side components keep only operational state: feed caches (copies of public headlines from automation publications) and a log of indexer-notification timestamps used to avoid duplicate submissions. Neither contains visitor data.
Calculator and search inputs
Server calculators and site search use GET forms. Inputs appear in the requested URL, browser history and bookmarks, and may appear in ordinary hosting logs. Use non-sensitive values. The Modbus register decoder computes locally in the browser; its register inputs are not submitted to the server. CSV worksheets download without an account or email address.
External links
Articles and index entries link to external sites. Following those links subjects you to their policies, not this one.
Contact
Questions about this policy: Yunus Emre Vurgun, the site's maintainer.
Changes
If this policy ever needs to change — for example, if the site adds a feature that processes data — the change will be published here with a new date.