Legal Center

Google Play’s Data safety

Google Play’s Data safety section is a way to support transparency towards users about the collection, use and protection of their data when using an app. By completing a form in the Play console, developers are required to inform their users about their privacy and security practices to make informed choices when using use of the app.

If you use Microblink’s SDK as a component of your app, this page will help you disclose privacy and security information to your users.

For more guidance on how to navigate Google Play’s Data safety section, visit Play Console Help.

BlinkID SDK, BlinkCard SDK and Capture SDK

Data type SDK accesses and collects

NOTE: No data from the images is being directly or indirectly transmitted anywhere from the device by this SDK. All the information is handled locally through the SDK.

(OPTIONAL) PING

PING is a mechanism used to track the number of scans and gather data:

• Licensee/package name
• Platform
• OS Version
• Device
• GUID
• User ID
• Details about the scan type and settings used
• Classification of the scanned document (Country/year/type)
• Scan session flow information (length, state change, timings)
• Location of the specific fields on the document

Most of the data sent through PING is used to gather analytics about the users’ scanning experience and to gather additional data on the scanning flow. The data regarding the individual user is in no way being used nor is it connected to the individual user.

Microblink uses PING to track license usage, and prevent the use of the solution in a way that is not permitted by the agreement between Microblink and the customer and for this reason, users have no control over whether the data will be processed using this mechanism.

Data is being sent to Microblink’s server where it is used for counting the number of scans via the client’s application and for analytic purposes. Most of the data collected is used to understand and improve the scanning flow.

All of the aforementioned data types are bundled together and therefore the same statements apply to all of them.

All requests are sent through the HTTPS protocol directly to Microblink’s server and are therefore encrypted. No additional encryption is provided for this data.

Before being sent, the JSON file is encoded via Base64 and decoded once it reaches the server.

Users cannot request the deletion of this data. However, this data does not contain any information about the user (other than the User ID) and cannot be connected with any other set of data to extract more information about the user.

Apple’s app privacy details

Data safety file is included in Microblink’s SDK where you can find information on the use of data.