SlickEdit strives to meet the demands of its customers. Without knowing what features or languages our customers are using, it is a challenge to determine which areas of the product need our attention most. To close this information gap, we developed the Product Improvement Program. The program runs in the background, logging events as they happen in your daily usage.

We gather a variety of data, including information about command invocation, toolbars and tool windows, settings, project and workspace usage, error messages, and file types. We do not make any record of file, project, or workspace names, directory structures, or source code.

Periodically, the compiled data is sent to SlickEdit. The first time the program tries to send data, you are prompted.

The dialog contains a link to preview the data that was compiled before deciding to send it to SlickEdit. You can also get more information by clicking the Product Improvement Program Info link, which takes you to an informational page on SlickEdit's website.

Select the Yes radio button to send the data and continue your participation. If you do not wish to have any data logged or sent to SlickEdit, select the No option. After making your selection, click OK. You can also click the Ask me later button to postpone the data transmission. No data will be sent at that time, and you will be prompted again later. You can also change your participation status at any time by going to Window → SlickEdit Preferences → Application Options → Product Improvement Program. For more information about these preferences, see Product Improvement Program Options.

After this first prompt, if you agree to participate in the program, all data transmissions are completely silent. Transmission only occurs at start-up of the application or when the editor has been idle for a period of time, thus causing the least possible disruption to your work.

All data is completely anonymous. We do construct a source ID to enable us to determine how many data sources we have. This ID is a concatenation of machine name, user name, and serial number that is then hashed. The hash result is used as the ID. Therefore, even with a unique ID for each user, we are unable to associate an ID with any particular person or source.