About data provision

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

Data provided to Kaspersky by using Kaspersky Who Calls 1.32 and later

To provide the core functionality, while You are using the Software the Rightholder has to receive from Your device and process information about the installed Software, the acquired license, information about the Computer, the Computer’s activity on the internet, specifically:

• Product ID, product version, installation ID, session ID, user ID, service ID.
• Application ID, application version, application locale.
• License ID, license state, license version.
• Country code, receipt data, transaction ID, OS type code.
• MD5 hash of the unique device identifier, machine universal time, device platform.

In order to identify new and challenging data security threats and their sources, as well as threats of intrusion, and to take prompt measures to increase the protection of the data stored and processed by the user with a computer, you agree to automatically provide the following information to Kaspersky:

• Type and version of the Rightholder’s software installed.
• Unique installation identifier.
• Operating system version.
• MD5 hash of the unique device identifier.
• information about the language (locale) of the device.
• Application ID.

For the purpose of updating the global Kaspersky Who Calls phone number database, you agree to the transfer of the following information to the Kaspersky Security Network cloud service:

• Information about the phone numbers added to the global database, including categories and comments.
• The phone numbers checked.
• The “spam” or “not spam” tag for the number.

For the purpose of improving the quality of the app, you agree to automatically provide the following information:

Information about the quality of KSN services:

• KSN service identifier.
• Statistics for successful packets.
• Statistics for unsuccessful packets.
• Statistics for packet time.
• Statistics for packet number.
• Number of connections from cache.
• Number of successful connections.
• Number of unsuccessful connections.
• Number of successful transactions.
• Number of unsuccessful transactions.
• Time distribution of successful connections.
• Time distribution of unsuccessful connections.
• Time distribution of successful transactions.
• Time distribution of unsuccessful transactions.
• Service request identifier.
• Number of service requests.
• Number of service requests from cache.
• Number of requests canceled because of network problems.
• Number of requests canceled because of inactive service.
• Number of requests canceled because of an invalid path.
• Time distribution of successful requests.
• Time distribution of canceled requests.
• Time distribution of requests that timed out.
• Time histogram.

The Rightholder also processes data in a form that does not, on its own, permit direct association with any specific individual. You can find the list of such data and purposes of their processing for a given software by visiting https://help.kaspersky.com/, selecting the software, and viewing its respective “Data provision” section.

When You provide Your data through the Software to the Rightholder, the Rightholder handles it according to its Privacy Policy, which describes, in particular, the manner by which the Rightholder protects Your data, where the Rightholder processes Your data, and your rights as the data subject. You can find and read its complete content at https://www.kaspersky.com/products-and-services-privacy-policy.

For the purpose of improving the quality of the app and analyzing user satisfaction, you agree to automatically provide the following information:

• To Firebase:
  • Information about Software installed on the Computer: instance ID, version, name of the store where the application was obtained, timestamp of the first launch of the Software, app foreground or background state, app package name, a pseudonymous app-instance identifier, network, and the following corresponding information: response codes, payload size in bytes, response times, duration times for automated traces.
  • Information about the use of the Software: event type, functional mode (free/premium), license name and name of the Software window or dialog that is active when data is submitted.
  • Information about the Users’ Computer where the Software is installed: Computer brand, category, model and orientation, RAM and disk size, version and language (locale) of the operating system; information about whether the application was first opened in the last 7 days or more than 7 days ago.
  • Carrier, radio/network information, IP address, geography, locale/language, signal strength, jailbroken or rooted status of device, battery level and battery-charging state.
  • Advertising ID, IDFVs.
  • Information about the User: User’s age category and gender, country of residence, and list of interests.
• To Crashlytics:
  • Device language code.
  • Information on how to load rules into a software extension: duration for uploading the rules into the software extension, number of rules deleted and added to the software extension; number of times that the software extension has been turned off; current status of the software extension.
  • Result of the session reset.
  • Result of request for permission to display notifications.
  • Information about the results of database updates: update duration, number of updated records and categories, total number of records and categories in the database, expected number of records, number and names of the update database files downloaded.
  • Link string when opening a URL.
  • Release date and time of the software's databases.
  • License information.
  • Information about the phone number: categories; phone number checked; phone number type (spam or not spam, organization).
  • Product operating mode (free or paid).
  • ID of the Software retail item (SKU).
  • Purchase status.
  • Type of legal agreement accepted by the user while using the Software.
  • Product/hardware manufacturer.
  • Version of the installed software.
  • Flag indicating whether the software was running in the background.
  • Flag indicating whether the frame was the cause of the software error.
  • Information about events that happened before the software terminated unexpectedly: event identifier, event date and time, event type and value; CPU architecture; unique event ID; event date and time.
  • Total disk space and amount currently used.
  • Text of the error message.
  • A flag indicating that the software exception was caused by a nested exception; the Software exception type.
  • For each frame associated with a thread, exception, or error: the name of the frame file, line number of the frame file, debug symbols, address and offset in the binary image, display name of the library that includes the frame, type of the frame, flag indicating whether the frame was the cause of the error.
  • ID of the issue associated with the event.
  • Name and version of the OS.
  • The queue the thread was running on.
  • Total RAM and amount currently used.
  • CPU register values.
  • Flag indicating whether the device is rooted.
  • Screen orientation at the time of the event.
  • Information about the signal that caused the Software to terminate unexpectedly: signal name, signal code, signal address.
  • A flag indicating that the thread caused the Software to terminate unexpectedly; thread ID.
  • Device model.
  • OS ID.
  • Unique installation ID.
  • Software ID.
  • Error code.
  • Version of the statistics being sent.

Data is forwarded to Firebase and Crashlytics over a secure channel.

Access to and protection of the information are governed by the corresponding terms of use of the Firebase and Crashlytics services.

For the purposes of allowing the Rightholder to create effective marketing and informational materials, you agree to automatically provide the following information:

• To AppsFlyer:
  • Information about the installed Software: name and version, Software ID, installation date on the User's Computer, first launch flag, date of the first launch, and preinstalled Software flag.
  • Information about the User's Computer: type, brand, model name, unique identifier, information about the type of network connection, language (locale) of the Computer, IP address, operating system version, User’s computer name, IDFA, User Agent.
  • Name of the mobile operator, carrier.
  • Information about the AppsFlyer SDK used in the Software: SDK version and build number, AppsFlyer transaction identifier, Advertiser ID, flag indicating use of the Advertiser ID, Rightholder’s unique identifier in the AppsFlyer service, AppsFlyer license key.
  • User’s unique identifier in Google services.
  • Timestamp and name of the event about which data is submitted, value of the event counter.

Data is forwarded to AppsFlyer over a secure channel. Information about how data is processed in AppsFlyer is published at: https://www.appsflyer.com/privacy-policy/.

• To BigQuery:
  • Information about Software installed on the Computer: Software version, name of the store where the application was obtained, timestamp of the first launch of the software, package name and version, pseudonymous app-instance identifier, application ID in Firebase services, application platform and ID.
  • Information about the use of the Software: event type and value.
  • Information about the User’s computer where the Software is installed: Computer brand, category, model, information about the language (locale) of the operating system.
  • Information about the User: country of residence, campaign and name of channel that attracted the User.
  • Advertising ID.

Data is forwarded to BigQuery over a secure channel. Information about how data is processed in BigQuery is published at: https://cloud.google.com/terms/data-processing-terms.

• To Firebase Cloud Messaging:
  • Unique installation ID (Instance ID).
  • Sender identifier (for sending messages).
  • Application version (version code).
  • Application build number.
  • Application version code.
  • Application package name.
  • OS version.
  • Version Google Play Services.
  • Version code Google Play Services.
  • Application ID.
  • Application ID in Firebase services.
  • Protocol version.

Data is forwarded to Firebase Cloud Messaging over a secure channel. Information about how data is processed in Firebase is published at: https://www.firebase.com/terms/privacy-policy.html.

For the purpose of activation of the extended version of the Software, you agree to automatically provide the following information to Firebase Dynamic Link:

• Program identifier in Firebase.
• Device specifications for iOS: device language code setting, device language code obtained by executing JavaScript code in WebView, device model, device display resolution height, device display resolution width, device time zone setting.
• App bundle ID.
• iOS version.
• Firebase SDK version.
• App installation epoch time.
• Possible unique matched link the server needs to check before performing fingerprint match.

Data is forwarded to Firebase over a secure channel. Information about how data is processed in Firebase is published at: https://www.firebase.com/terms/privacy-policy.html.

Page top