What we do not collect
- Your inputs. Dimensions, parts lists, densities, and results are computed in your browser and never uploaded. We do not store them on our servers. Ordinary form values are lost when you close or refresh the page. When Pipe Weight hands a profile to Material Planner, the profile is kept in this tab's session storage and removed when Material Planner reads it. Until then, it can survive a refresh in the same tab but is cleared when that tab closes. It never travels through the address bar, so it cannot appear in a shared link or a server log.
- Cookies, accounts, or identifiers. We set no cookies and keep no persistent identifier in your browser.
- Third-party scripts. No analytics, advertising, or social scripts load on these pages.
What we do collect: eight anonymous counts per utility
To understand how the utilities are used, the page sends one small message to our own server on eight occasions: when a utility page is opened, when a result is generated, when a result is copied, when a CSV is exported, when print is opened, when the inputs produce an error message, when a link to a related utility is followed, and when the feedback link is clicked. The message contains two things: the name of that event and which utility you were using (for example tap-drill) — none of your inputs, not the error itself, and nothing about which link you followed.
There were four of these until 23 September 2026. The four added tell us how many people who open a page go on to use the tool, which utilities reject the input people bring them, and whether the links between utilities are followed. What did not change, and will not: these are first-party only, they set no cookie, no third party ever receives them, and nothing links your visits on one day to your visits on another.
On the server, the request's network address and browser identification string are combined with the current date and a secret and reduced to a short one-way digest so that several events on the same day can be recognised as one visitor. The address and browser string themselves are not stored, the digest changes every day, and it cannot be reversed into who you are.
Two things are then written. One line in the server log — event name, utility, date, and that day's digest — which lives only as long as the host's runtime-log window (currently one hour on our Vercel plan). And running totals in a small database: how many events of each kind per day, per utility, and roughly how many distinct visitors, estimated from the digests without storing them. Nothing about you individually.
Where this runs
The site is served by Vercel and the totals are stored with Upstash, both in the United States. Like any web host, they process connection metadata to deliver the page and keep short-lived operational logs under their own policies.
If you email us
Feedback goes to feedback@arzentiq.com only if you choose to write. We keep your message to act on it and reply, we do not share it, and we ask you not to include customer data or drawings. Quotes used internally are anonymised.
Changes
If any of the above changes, this page and its effective date change with it. Questions are welcome by the same email. See also about ARZENTIQ.