The Gauge Calculator product family follows our general privacy philosophy.
No information that identifies a specific device, person, or network address is ever collected.
All information we collect automatically is used solely for the purpose of improving the product. It is not used
to send you ads or sales pitches.
By default, information about serious product errors are uploaded to our website.
By default, counts of how many users are making use of various features are uploaded to our website.
We are transparent about the data collection behavior when you are using the product.
We give you access to the privacy policy on our website before you use the product.
Online Edition
If you scroll down to the bottom of the webpage implementing Gauge Calculator, you can read
about what data is collected. We collect:
The count of visits to the page (lumping together all visitors).
If you have scripting turned off, each visit will add to our count of scripting-off-visits.
We keep one counter for the entire website.
The count of each type of web browser used to visit the page. We keep one counter
for each web browser type covering all the pages in the website.
If our server side code generating the look-and-feel of our website has a serious error,
we try to log an incident report with the time, page, and type of web browser.
If the scripting code in the page has a serious error, we try to log an incident report
with the time, page, and type of web browser.
There is no opt-out or opt-in for the data collection behavior of the Online Edition.
Windows Phone Edition
The Windows Phone Edition has a privacy policy reachable via the information (?) icon
in the application bar. Data collection is enabled by default but can disabled (or re-enabled)
at will. In other words, the policy is opt-out.
If you have not disabled data collection, the Windows Phone Edition application will report:
The count of visits to each page in the application. When we receive counts, we lump them
in with the counts of all users. We do not track counts on a user-by-user basis.
The count of times the application was started up in inches-mode or centimeters-mode plus
how often you switch between inches and centimeters.
The count of uses of the estimate-gauge, compute-gauge, compute-size, and compute-stitches
tools.
The highest disk and memory usages noted by the application during one of its periodic
internal checks. When we receive performance data, we lump it in with the data from all users.
We do not track performance data on a user-by-user basis.
The manufacturer, model, etc. of the phone used to run our application. We keep a count
of the number of types of devices using our application. We do not track which person has what
kind of phone.
If our phone application detects that it is crashing,
it tries to log an incident report with the time, crash location, and type of phone.
You can opt-out of the monitoring of normal usage and continue opting-in to crash reporting -- or
vice versa.
We use the incident reports to give us an automatic heads-up that our product is behaving badly
and to provide clues to the root cause of the bug.
We use the other information to guide our priorities. If we know certain features are being
used a lot, we'll put a lot more effort into making sure that they work well. We're also more likely
to put a larger fraction of our efforts into adding features and products that we think would
complement the kinds of things we observe you doing with our existing products.
