Download our demo app from App Store to see Fingerprint in action!
Device Identifier
When Fingerprint Identification SDK is integrated into your mobile app, for every device that interacts with your app, you will be able to receive a unique device identifier (i.e.visitorId). The visitor ID is derived solely from Apple’s identifierForVendor (IDFV) property. The SDK does not use any fingerprinting techniques to identify a device.
However, despite the visitor ID being derived from IDFV, there are a few important differences between them:
- The visitor ID will remain the same even when the app is removed and re-installed whereas the IDFV will not.
- In addition to being scoped by the vendor, the visitor ID is also scoped by the Fingerprint Workspace. It means the only time the visitor ID remains the same between two apps is when the apps are from the same vendor and when they belong to the same Fingerprint workspace.
Did you know?The device identifier generated by the iOS SDK (embedded within your mobile app) will be different from the visitor ID generated by the Javascript agent (embedded within your website).
iOS 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 jailbroken device, you will be able to take additional precautionary security steps (e.g., multi-factor authentication). When your mobile app requests a visitor ID, the SDK, along with the IDFV, will collect several other attributes from the device. The Smart Signals are deduced by combining these attributes with additional algorithms. For iOS, the following Smart Signals are available:- Factory Reset Detection
- Frida Detection
- Geolocation Spoofing Detection
- IP Geolocation Detection
- IP Blocklist Detection
- Jailbroken Device Detection
- MitM Attack Detection
- Tampered Request Detection
- VPN Detection
- iOS Simulator Detection
- Developer Tools Detection
- Smart Signals common for browsers and mobile devices
Fingerprint Identification SDK for iOS
Current Version: 2.17.1
For release notes and older versions, please visit the Changelog for iOS SDK page.Supported Versions
The minimum version that the iOS SDK for Fingerprint Identification supports is iOS 13, tvOS 15. Per Apple and Statista, this will allow your app to be compatible with a wide variety of active iOS devices. As of May 2023, our SDK will allow your app to be compatible with more than 94% of the devices in the world.Getting Started Guides
Our Getting Started guides are aimed at helping you to integrate our SDK with your apps easily.- For native iOS apps, see Getting Started Guides > iOS and our iOS quickstart.
- For apps built using Flutter, see our Flutter SDK on GitHub and our Flutter quickstart.
- For apps built using React Native, see our React Native SDK on GitHub and our React Native quickstart.
Privacy Manifest File Requirements for App Store
During WWDC 2023, Apple introduced a new requirement where app and SDK developers must create privacy manifest files to declare the data that their app/SDK collects and the reasons for collecting this data. Accordingly, starting from v2.3.2, the Fingerprint Identification SDK for iOS will include a privacy manifest file. To learn more, please see Understanding privacy manifest files.FingerprintJS-iOS: Open-source identification library for iOS
We also provide a lightweight, open-source library called fingerprintjs-ios which is available to use for free by everyone. Our commercial SDK, Fingerprint Identification for iOS, is based on our well-maintained, free, open-source library. For your better understanding, here is a complete set of differences between our open-source library (fingerprintjs-ios) and our commercial SDK (fingerprint-ios-pro).
**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