Kaspersky Password Manager Help
[Topic 166860]

About data provided

View information about the data provided to Kaspersky while using previous versions of the application

Data provided to Kaspersky using Kaspersky Password Manager 10.1

Kaspersky protects any information received in accordance with law and applicable Kaspersky rules. Data is transmitted over a secure channel.

You can view the list of data provided under the terms of End User License Agreement (License Agreement) in the corresponding legal document. You can view the License Agreement in the App Store.

Additionally, you agree to provide Kaspersky with non-personal data by accepting the End User License Agreement.

Non-personal data is provided to Kaspersky for the following purposes:

To provide You with the core functionality of the acquired Rightholder's Software.

  • Information about the Software: full version of the Software; Software ID; Software localization; Software group; the result of the Software action; error code.
  • Information about the use of Kaspersky Security Network (KSN): the configuration identifier.
  • ID of the topic in the Software help; link name.

In addition to the information mentioned above, in case of signing in to the Web-Portal using Your Facebook or Google account, the Rightholder needs to receive from Your device and process the following non-personal data:

  • Information about the authentication: authorization code received from the identity provider; access token received from the identity provider; type of data sent to the identity provider; Rightholder ID in the identity provider's system; name of the identity provider; URI to which the identity provider's response is sent; parameters requested from the identity provider; ID of the Rightholder's resource; token type; value generated for request verification.

    Note: The availability of the option to sign in with Facebook depends on your region.

To improve the quality of the application.

  • Information about the use of Kaspersky Security Network (KSN): protocol used to exchange data with KSN; ID of the KSN service accessed by the Software; date and time when statistics stopped being received; number of KSN connections taken from the cache; number of requests for which a response was found in the local request database; number of unsuccessful KSN connections; number of unsuccessful KSN transactions; temporal distribution of cancelled requests to KSN; temporal distribution of unsuccessful KSN connections; temporal distribution of unsuccessful KSN transactions; temporal distribution of successful KSN connections; temporal distribution of successful KSN transactions; temporal distribution of successful requests to KSN; temporal distribution of requests to KSN that timed out; number of new KSN connections; number of unsuccessful requests to KSN caused by routing errors; number of unsuccessful requests caused by KSN being disabled in the Software settings; number of unsuccessful requests to KSN caused by network problems; number of successful KSN connections; number of successful KSN transactions; total number of requests to KSN; date and time when statistics started being received.
  • Version of the installed software; text of the error message; OS error code; http request method; token type; authentication token in the Rightholder's services; token TTL; path to the object being processed; method used for authentication in the Software; full version of the Software; Software update ID; information about implementation of the web service access handler; type of the installed Software; unique request ID to the Rightholder services; response status of the Rightholder's service; error code; line number of the source file in the exception handler; protocol ID; total duration of request processing; protocol processing error type; code of the error category; DNS address of the web service being accessed; server access duration; remote port and IP address of the web service being accessed; web address being processed.
Page top
[Topic 111964]

Compliance with European Union law

When distributed in the European Union, Kaspersky Password Manager complies with the terms of the General Data Protection Regulation (GDPR).

When you accept the End User License Agreement, you confirm that you are of the required age to install Kaspersky Password Manager within the European Union territory. After Kaspersky Password Manager is installed, you will be offered to read and accept the terms and conditions required for initial setup and use of Kaspersky Password Manager: the Conditions Regarding Data Processing and the Privacy Policy.

Important: To comply with the General Data Protection Regulation (GDPR), when updating Kaspersky Password Manager to version 9.1 or later, you will be asked to again accept the End User License Agreement, and the Conditions Regarding Data Processing and the Privacy Policy.

Page top
[Topic 166861]

Contents of trace files, dump files, and settings files

Note: All files described in this section can be accessed only by the system administrator of the computer and the owner of the computer account with Kaspersky Password Manager installed.

1. Trace files

Trace files contain the following information about events that occur during the operation of Kaspersky Password Manager:

  • Event time
  • Thread ID
  • Application component that generated the event
  • Description of the command's execution by the application and the result of the command execution

Trace files contain only the information necessary to fix defects in the application. Kaspersky uses trace files to investigate incidents associated with errors in the operation of Kaspersky Password Manager.

By default, the creation of trace files is disabled. You can contact Customer Service for information about how to enable creation of trace files.

Trace files can only be sent to Kaspersky manually. Kaspersky Password Manager does not send trace files to Kaspersky automatically.

You can choose how trace files are sent to Kaspersky.

Before sending trace files to Kaspersky, please review the data they contain. Subsections 1.1–1.3 indicate the naming scheme for trace files and where they are stored on your computer.

Important: Trace files may contain personal or sensitive information. By sending trace files to Kaspersky, you agree to provide to Kaspersky all data contained in the trace files you send, and you consent to the method used to send them.

  1. kpm_app_<timestamp>.log trace files may contain information about events that occur in the graphical user interface of Kaspersky Password Manager.

    kpm_app_<timestamp>.log trace files may contain the following data:

    • Names and identifiers of operating system users on macOS
    • URLs of Kaspersky websites
    • Full names of the Kaspersky Password Manager files
    • User names and passwords for connecting to the proxy server
    • User names and passwords for accessing websites if the user signs in to websites while trace files are being created
    • User settings

    kpm_app_<timestamp>.log trace files are stored in the ~/Library/Group Containers/2Y8XE5CQ94.com.kaspersky.kpm/Library/Application Support/KPM/Logs folder.

    kpm_app_<timestamp>.log trace files are stored on your computer from the time tracing is enabled.

  2. kpm_agent_<timestamp>.log trace files may contain information about events that occur in the graphical user interface of Kaspersky Password Manager.

    kpm_agent_<timestamp>.log trace files may contain the following data:

    • Full names of the Kaspersky Password Manager files
    • Name and IP address of the proxy server
    • User settings
    • Information about visited URLs
    • URLs of Kaspersky websites
    • Names and identifiers of operating system users on macOS
    • User names and passwords for connecting to the proxy server
    • User names and passwords for accessing websites if the user signs in to websites while trace files are being created

    kpm_agent_<timestamp>.log trace files are stored in the ~/Library/Group Containers/2Y8XE5CQ94.com.kaspersky.kpm/Library/Application Support/KPM/Logs folder.

    kpm_agent_<timestamp>.log trace files are stored on your computer from the time tracing is enabled.

  3. kpm_daemon_<timestamp>_pid_<PID>.log trace files may contain information about events that occur during the following processes:
    • Configuring the application
    • Opening of websites by the user
    • Updating application databases or automatically updating the application
    • Connecting to My Kaspersky
    • Receiving settings from My Kaspersky
    • Changing or synchronizing password databases

    kpm_daemon_<timestamp>_pid_<PID>.log trace files may contain the following data:

    • Full names of the Kaspersky Password Manager files
    • Name and IP address of the proxy server
    • Information about visited URLs
    • URLs of Kaspersky websites
    • Names and identifiers of operating system users on macOS
    • User names and passwords for connecting to the proxy server
    • User names and passwords for accessing websites if the user signs in to websites while trace files are being created
    • User settings

    kpm_daemon_<timestamp>_pid_<PID>.log trace files are stored in the ~/Library/Group Containers/2Y8XE5CQ94.com.kaspersky.kpm/Library/Application Support/KPM/Logs folder.

    kpm_daemon_<timestamp>_pid_<PID>.log trace files are stored on your computer from the time tracing is enabled.

Important: To prevent website user names and passwords from getting into trace files, we recommend that you not sign in to websites when tracing is enabled.

Kaspersky protects any information thus received in accordance with the law and applicable Kaspersky rules.

Trace files contain only the data necessary to fix defects in the application. Kaspersky uses trace files to investigate incidents associated with the operation of Kaspersky Password Manager.

By default, the creation of trace files is disabled.

Trace files can only be sent to Kaspersky manually. Kaspersky Password Manager does not send them automatically.

You can choose how trace files are sent to Kaspersky.

Before sending trace files to Kaspersky, please review the data they contain.

By sending trace files to Kaspersky, you agree to transfer all data they contain and you consent to the method used to send them.

2. Dump files

Dump files include all information about the working memory of the application's processes at the time the dump is created. Memory dumps may contain confidential information.

Dump files are generated by the operating system and are sent only with your consent. Before sending a dump file, please review its contents.

3. Additional files

In addition, Kaspersky Password Manager generates additional settings files that are stored on the user computer. These files may contain information necessary for operation of the Software: settings, internal databases, configuration files.

Customer Service specialists might ask you to provide the additional files in order to shorten the time required to process requests associated with errors in the Software. The user sends this data manually at the request of a Customer Service specialist.

By sending the additional settings files to Customer Service, you agree to provide all data they contain and you consent to the method used to send them. Before sending these files, please review their contents.

These additional files may contain the following information:

  • Proxy server settings – the user name and password hash
  • Credentials for connecting to My Kaspersky
Page top
[Topic 171492]