# Product Improvement Program: Data Transferred

The Product Improvement Program enables Thales to determine which functionality in Sentinel LDK Envelope is used the most by vendors and how it is used. This program benefits vendors because Thales is better able to determine what is most important to vendors and where to allocate their product improvement resources.

Your participation in this program is determined by the Envelope setting Participate in Product Improvement Program.

This topic describes the information that is collected by the Product Improvement Program.

Currently, data is sent from the Sentinel LDK Envelope GUI and Envelope command line tool as follows:

> Every time a project file is processed (command line or GUI "Protect All") or a file inside a project file is processed (GUI "Protect File"), a data set is sent to the Program server.

> If participation in the Product Improvement Program is disabled, no data is sent.

The contents of the submitted data are described below.

Information regarding Envelope, including:

>Whether the Envelope GUI or Command Line Tool was used

>Envelope version number

>Host architecture where Envelope was executed

Information regarding the Envelope project, including:

>File name of the project file (excluding path)

>Vendor ID used in the project

>Number of files in the project

>Information regarding files processed by Envelope:

•Name of the original file (excluding paths)

•Global Feature ID used during protection

•Whether data file protection was used. Version of data file protection used

•Which engine is used for protection (Mach-O). Engine build version

•Original file name of the target (excluding path)

•Target platform

•Architecture of the target

•File type (executable, dynamic library, or anything)

•Size of the file before and after protection

•Whether a custom login scope was used. The actual login scope is not transmitted.

•Posix timestamp (GMT) when protection was started

•Duration of protection process (how long did it take to process this file)

•Protection result (status code 0 on success, or the error code if protection fails)

•The selection for the various protection settings and advanced protection settings (check boxes, pull-down lists)

Information regarding the Mach-O Engine, including:

>Whether Signal Blocking is used (Off, Default Settings, Customized Settings - with no details)

>Whether Exceptions Handling is used (Off, Default Settings, Customized Settings - with no details)

>Whether Kernel Debugger Detection is used (Off, Default Settings, Customized Settings - with no details)

>Selected option for Gap Adjustment

>For protected Dylibs: Option to handle license failures on startup (Exit Process or Return Value of exported functions)

>Dump Protection value

>Option for suspending threads

>Whether Objective-C Obfuscation is enabled

>Number of unsupported architectures stripped form the binary

>Whether the signature of codesigned input file has been stripped

>Whether the binary contains a Loader Command unknown to the Engine