The M4 Back Office and M4 Creator applications send information about license and usage to m4backoffice.de.
This information does not contain any personal data.
Additionally the application allows to send exception messages to m4backoffice.de.
Exceptions messages are never send automatically but on user request only.
Depending on the kind of exception and user settings, these messages may contain personal information.
Find below lists with detailed description of the information sent.
No other information is sent.
In this document the term "personal data" includes all data that can be used to identify persons, organizations or technical equipment like computers or networks.
License Registration (M4 Creator Only)
Licenses are registered when you add a license in the dialog Edit Licenses to the license list or if you select Refresh Registration.
The registration key is stored.
License Registration does not contain any personal data.
NOTE: Licenses marked as MultiServer are valid without registration and no registration request is sent.
| Name | Description |
|---|---|
| License ID | The unique ID found in the license file. |
| Registration Key | An anonymous key generated on registration process. |
License Validation (M4 Back Office And M4 Creator)
Licenses are validated in M4 Creator after registration (if license requires registration) and in M4 Back Office on startup.
No information is stored.
License Registration does not contain any personal data.
| Name | Description |
|---|---|
| License ID | The unique ID found in the license file. |
| License Key | An anonymous key found in the license file. |
| Registration Key |
An anonymous key generated on registration process. Not transmitted for MultiServer licenses. |
Usage (M4 Back Office Only)
Information on M4 Back Office usage is sent on startup and application closing.
The information is stored with time stamps of start and end of usage.
Usage logging does not contain any personal data.
| Name | Description |
|---|---|
| Session ID (Startup And Closing) | A unique anonymous ID generated on startup. This ID is different every time you use M4 Back Office. |
| Address Key (Startup Only) |
Anonymized key (hash) of your physical network address. NOTE: The network address is anonymized using SHA256. It is not possible to reconstruct the network address from the hash code. A hash of the physical network address is also used for exception logging. For both loggings different hash codes are generated, making it impossible to match these loggings. |
| Version (Startup Only) | Application version used. |
Exceptions (M4 Back Office And M4 Creator)
Exceptions are never sent automatically.
For each exception to be sent, the link Send, found on most exception dialogs, has to be selected.
Exception logging may contain personal data. Please see details below.
NOTE: Exceptions are stored along with an anonymized key of your physical network address.
This key can also be found in the about dialog. If you send us this key, we can find your exceptions in the exception log, which can be useful for assistance.
Of course, doing this, the anonymized key is not anonymous anymore.
Sending exceptions can be disabled, setting the SendExceptions flag in
AppSettings.xml. Default setting is true.
| Name | Description |
|---|---|
| Create Date | Date when exception was created or sent. |
| Address Key |
Anonymized key (hash) of your physical network address. NOTE: The network address is anonymized using SHA256. It is not possible to reconstruct the network address from the hash code. A hash of the physical network address is also used for usage logging. For both loggings different hash codes are generated, making it impossible to match these loggings. |
| Message |
Short exception message. NOTE: Short exception messages, generated by standard components, do not contain any personal information. |
| Full Message |
Complete exception message including call stack. This message is send by default. Full exception messages, generated by standard components, do not contain personal information as long as the call stack does not include custom components with classes, methods or properties with personal data in their names (e.g. "MyCompanyFunction"). NOTE: Sending the full message can be disabled, setting the SendFullMessage flag in AppSettings.xml. |
| Technical Message |
Additional technical message. This message is not send by default. NOTE: Technical messages can contain personal data like database field names and also field values. For this reason these messages are not included by default. Sending the technical message can be enabled, setting the SendTechnicalMessage flag in AppSettings.xml. |