Calculator inputs
Calculator measurements and results are processed in your browser. They are not sent to BuildMeasure's first-party analytics log. They are sent to the feedback database only if you choose to copy them into and submit the feedback form.
Saved estimates and projects on this device
The Save action stores an estimate in your browser's local storage so it remains available on that device. Project Mode can copy selected saved estimates into a named project, which is also stored only in local browser storage. Newly saved estimates may also keep the calculated purchase quantity, purchase-unit label, and any optional local price and currency snapshot you entered. Project Mode uses those structured local fields for shopping lists instead of reading numbers back from display text. Estimates and projects are not synchronized to an account or sent to BuildMeasure.
Use Clear all in a calculator to remove that calculator's saved-history list. A project is a separate local snapshot, so clearing calculator history does not delete an existing project. Use Delete in Project Mode to remove a project. Clearing browser site data can remove both saved estimates and projects.
Calculator feedback
When you submit a report, BuildMeasure stores the selected calculator, feedback type, text you enter, submission time, and a random anonymous browser token used to limit repeated submissions. The form does not ask for your name or email. Do not include personal, payment, account, or other sensitive information in free-text fields.
Feedback reports are retained for up to 24 months so calculation issues and regression evidence can be investigated. Include the report reference if you later ask for a specific report to be removed.
Anonymous product analytics
BuildMeasure records limited first-party events such as opening or using a calculator, clicking into a calculator from the homepage or a guide, completing or failing an estimate, using the optional cost feature or a result action, submitting feedback, and browser errors. The event may include the page, calculator, coarse browser and device classes, language, external referring host, and campaign tags in the link. Browser error details are shortened before storage.
Calculator-entry events use only a fixed source label (homepage or guide), and cost-feature events record only that the feature was used. Measurements, quantities, entered unit prices, currency labels, and calculated costs are not copied into the first-party analytics event.
BuildMeasure's first-party analytics log does not store IP addresses, names, email addresses, raw user-agent strings, or persistent analytics cookies. A random identifier is created for the current page load only and is not saved in the browser. Analytics events are retained for up to 90 days.
Microsoft Clarity
If you choose Allow analytics, BuildMeasure loads Microsoft Clarity to understand navigation, clicks, scrolling, session flow, and technical friction. Clarity is not loaded before that choice. BuildMeasure keeps Clarity advertising storage disabled and does not send custom user identifiers through the Clarity Identify API.
Microsoft Clarity masks input-box and dropdown content in its recordings by default. BuildMeasure also explicitly masks the Project Mode workspace so project names and saved-estimate text are not uploaded in Clarity recordings. Clarity may otherwise process device, browser, approximate location, interaction, and session data under Microsoft's privacy terms. You can change or withdraw your analytics choice at any time using Analytics choices in the site footer. Withdrawing consent clears Clarity cookie consent and reloads the page without loading Clarity again.
Advertising and Google AdSense
BuildMeasure may use Google AdSense. During AdSense site review, the site may expose account verification metadata and an ads.txt declaration before advertising code or ad units are enabled. If Google ads are enabled, third-party vendors, including Google, may use cookies, web beacons, IP addresses, or similar identifiers to serve and measure ads.
Google's use of advertising cookies enables Google and its partners to serve ads based on a visitor's prior visits to BuildMeasure or other sites on the Internet. Visitors can manage or opt out of personalized advertising through Google Ads Settings. Other third-party vendors or ad networks participating through AdSense may also use cookies or similar technologies; where applicable, the consent flow will identify participating vendors and provide available choices.
For more information, see how Google uses data when you use sites or apps of its partners. Where consent is required, BuildMeasure will use a Google-certified consent management platform before personalized ads are served. Calculator measurements, saved project names, entered unit prices, calculated costs, and feedback text are not intentionally supplied to AdSense as custom advertising-targeting data.
Hosting and security data
The managed hosting service may process request metadata and technical logs needed to deliver, secure, and diagnose the site. The AdSense site verification metadata and ads.txt declaration do not themselves create an advertising profile. Advertising code will be enabled only as part of the approved AdSense setup and with required consent controls.
Questions or deletion requests
Use the contact page or the feedback form. For a stored feedback report, include the relevant report reference and do not place sensitive information in the request.