Our website 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.

• 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.

We use the following cookies:

• If you ask to remember your color preference, we use a long-lived cookie to make your browser remember the preference. (The color preference is not stored on our website.)
• If you ask to remember your font preference, we use a long-lived cookie to make your browser remember the preference. (The font preference is not stored on our website.)
• If you use a thumbs up or thumbs down button to indicate your opinion of a review, helpful hint, or other community posting, we use a short-lived cookie to discourage voting multiple times.
(The color preference is not stored on our website.)

There is no opt-out or opt-in for the data collection behavior of the website.

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.