Fingerprint's device intelligence platform for Android devices.

Fingerprint's device intelligence platform is also available for Android devices. Our device intelligence platform for Android helps you to accurately identify the devices that interact with your mobile app and provides high-quality smart signals that will help you identify risky transactions before they happen.

To make integrations with mobile apps easier, we offer SDKs for apps built natively using Android as well as for apps built using multi-platform frameworks (e.g. React Native).

A Fingerprint account is required to be able to use the Fingerprint Identification SDK in your mobile apps. If you do not have an account yet, please sign up for one.


Download our demo app from Google Play to see Fingerprint in action!

Device Identifier

When the Fingerprint Identification SDK is integrated into your mobile app, it will collect several attributes from the device. With the help of these attributes and additional algorithms, Fingerprint is able to provide a unique device identifier (i.e. visitorId) for every device on which your app is installed.

When compared with browsers, the identification accuracy is better for mobile devices because we identify mobile devices using signals that have higher longevity than those used for identifying browsers. But there are scenarios where a visitorId does not persist.

For your reference, we have listed various scenarios where a visitorId will remain the same before and after and where a new visitorId will be created.

ScenarioWill I receive the same visitorId before and after?
The app or device is restartedYes. You will receive the same visitorId even after the app or device is restarted.
The app data/cache is clearedYes. You will receive the same visitorId even after the app's data/cache is cleared.
The app is uninstalled and re-installed againYes. You will receive the same visitorId even after the app is removed and installed again.
The device is factory resetYes, in most of the devices. After a factory reset, except for a few Android models, the visitorId remains the same.
The app is installed on one or more profiles, that belong to a single user on the same deviceYes. You will receive the same visitorId even when the app is installed on multiple user profiles that belong to a single user on the same device.
The app is installed for one or more user accounts, all belonging to the same deviceYes. You will receive the same visitorId even when the app is installed on multiple user accounts that belong to the same device.
The app is cloned to a different appYes. The visitorId does not change even when the app is cloned numerous times or when the cloned app is installed on a different profile.

Android Smart Signals

Smart Signals are actionable device intelligence signals that help you to make informed decisions about the device and thus prevent fraud. These signals could be used as input to your machine learning models behind your fraud detection or risk mitigation engines. For example, when you know that a request is originating from a rooted device or from a recently factory reset device, you will be able to take additional precautionary security steps (e.g. multi-factor authentication).

For Android, the following smart signals are available:

These smart signals are available as part of our Pro Plus and Enterprise plans. If you are interested in one or more of these signals, then please contact our support team to enable them for you. Signing up for an Enterprise plan does not automatically enable these signals.

Fingerprint Identification SDK for Android


Current Version: 2.4.0

For release notes and older versions, visit our Releases page.

Supported Versions

The minimum version that the Android SDK for Fingerprint Identification supports is Lollipop, API Level 21. Per Google, this will allow your app to be compatible with a wide variety of active Android devices.

Getting Started Guides

Our Getting Started guides are aimed at helping you to easily integrate our SDK with your apps.

Data Safety Requirements for Google Play

For every app that is uploaded to the Google Play Store, Google requires that the app's privacy and security practices are made available to all its users. For this reason, when an app (or a new version) is uploaded to the Play Store, Google requires app developers to fill out a data safety form. See Provide information for Google Play's Data safety section for more information.

If your app includes our Android SDK, then you can use the table below as a reference to fill out the data safety form:

Question in Google Play Console's data safety formResponse
Does your app collect or share any of the required user data types?Yes.
What type of data is collected?Device or other identifiers.
Is this data collected, shared, or both?Collected.
Is this data processed ephemerally?Yes.
Why is this user data collected?Fraud Prevention, Security, and Compliance.

FingerprintJS-Android: Open-source identification for Android

We also provide a lightweight, open-source library called fingerprintjs-android which is available to use for free by everyone. Our commercial SDK, Fingerprint Identification for Android, is based on our well-maintained, free, open-source library.

Compared to the open-source library, our commercial SDK collects many more attributes from the device. It also uses advanced fingerprinting and matching algorithms to create a unique device identifier.

For your better understanding, here is a complete set of differences between our open-source library (fingerprintjs-android) and our commercial SDK (fingerprint-android-pro).


Fingerprint Identification for Android

Core Features

Attributes collected from the device Basic
(e.g. Android ID, GSF ID, model)
Advanced. Lot more attributes, in addition to those collected by the open-source library.
ID Type Device ID or a fingerprint that is a hash of the collected attributes A single visitorId that is computed using advanced fingerprinting and matching algorithms
ID Origin Attributes are processed only within the library. External servers are not involved. Attributes are processed on external servers
ID Lifetime Only up to a few weeks Lasts several months and sometimes even years
ID Collisions Common Very rare

Support for multi-platform frameworks

Flutter -
React Native -

Advanced Features

Server API and Webhooks
(Build flexible workflows)
Mobile Smart Signals
(VPN Detection, Factory Reset, App Cloners, etc)
(Based on IP address)


Data security Depends on your infrastructure Encrypted at rest
Storage Depends on your infrastructure Unlimited up to 1 year
Regions Depends on your infrastructure Global, EU and Asia data centers
Compliance Depends on your infrastructure Compliant*** with GDPR, CCPA, SOC 2 Type II, and ISO 27001
SLA SLA is not provided 99.8% Uptime
Support GitHub Issues/Questions. Response times varies. Dedicated support team that responds to chat, email, and calls within 1 business day

How to get started?

Get it on GitHub Sign up for a free 14-day trial
**In comparison to fingerprints, VisitorIDs are more accurate and stable identifiers because they are deduplicated, are processed further on the server, and utilize fuzzy matching. On the other hand, fingerprint hashes become unstable across time intervals greater than 2 weeks because they rely on an exact match of all browser attributes.
***The company, Fingerprint, in its role as data processor is compliant with GDPR, CCPA and SOC 2 Type II. It is also ISO 27001 certified. As a data controller, it is still your responsibility to be compliant with GDPR and CCPA and use the identification result for legitimate purposes.