Analyst Crash Report Privacy Policy

Your Consent
By sending the error report, you consent to the AWR Privacy Policy.

How is the information organized?

The Error Report Details crash report dialog labels files as PROPRIETARY AND NON-PROPRIETARY.

To delete a file from the crash report:

1. Click What does this report contain on the Error Report dialog.
2. In the ensuing dialog, right click the file you want to delete and select Delete Selected File(s).
Multiple files can be selected at once by holding shift or control.

What information do we collect?

We collect information from you when you send us an error report from Analyst, hereinafter referred to as
the "Software". The information can be divided into the following two categories.

Contains no proprietary information:

Crash description XML file (crashrpt.xml) containing the basic information about the crash
(Software name and version, resource usage parameters, your Windows version, your country
and language). You may be asked to enter your e-mail address and short problem description.
This information is also included into the crash description XML file.
Crash minidump file (crashdump.dmp) which contains technical information about exception in
the Software (processor information, operating system version, process and thread information,
stack traces for each thread, the list of loaded modules).
Registry key dump file that may contain the persistent settings of the Software.

Log file that contains status information of the program as it runs. This is used to determine the
last action of the program before a crash.
Exceptions text file contains information about the exception which caused the crash report. It
contains a stack trace, message, targetsite and type.
Hotkey files contain mappings of keyboard keys to program commands. It may help in
reproducing an unusual crash.
Awr_regkey is a snapshot of the registry which the Software uses. It can help in diagnosing a
problem with having multiple versions of the Software installed at once.
Awrd.lic is the license file the Software is currently using. This has valuable information about
who is using the Software.
DockPanelLayout and ToolBarLayout contain information about the layout of the windows in
the Software. Sometimes these files can be written with problematic data.
MemoryReport has data about the random access memory being used by the Software.

ParameterDescriptions contains description information about each parameter which gets

shown in the property grids. We would like to know if this file has been corrupted.
 RecentFiles is a history of the project files which have been saved and opened. There is a
possibility that this file becomes corrupt and causes a crash.
Windows XML file is a collection of the most recent sizes and positions of various pop-up dialogs
in the Software. It is used to restore windows to their previous positions instead of the default
position.
Potentially contains proprietary information:
RecordingOutput: Recording output files keep track of what the user has done in the current
model. The contents of the recording output contain detailed information about the constructs of
the model for example the dimensions of the geometry. The recording output can be played back
in a new session to recreate what was manually created originally. Having these files in the crash
report is helpful to our developers when diagnosing crash reports.
Scripting input snapshot contains anything that was in the Scripting Input View at the time of the
crash. This could be played back scripts and manually entered python code.
Preferences files contain parameter values which are loaded by default for a particular type of
parameter. For example you could set a preference for the distance unit to be mm. Then every
time a new model is created it has its distance unit set to mm. Having this file when diagnosing a
crash report can help reproduce the conditions more exactly. There could potentially be
proprietary information in here because you can set a preference for parameters from all
constructs of the model.
Redo and Undo Dump files contain textual snapshots of the redo and undo stacks at the time of
the crash. There could potentially be proprietary information in these files because they contain
detailed information about the constructs of the model.
Last saved or opened project (.apz file).