mirror of
https://github.com/fingerprintjs/fingerprintjs.git
synced 2026-05-06 22:08:25 +08:00
767b90fee4
* Move the licensing section to its own page in /docs. Many people see it right at the top of the README and believe this is our commercial product. * State at the top of the page that FingerprintJS != Fingerprint Identification. * Refresh some of the copy in the Fingerprint Identification section. * Bring the comparison table from our docs into a new page here in this repo in /docs * Mention Discord server
5.0 KiB
5.0 KiB
FingerprintJS vs. Fingerprint Identification
The main difference between FingerprintJS and Fingerprint Identification lies in the number of attributes collected from the browser, how they are processed, and the accuracy in identifying visitors.
Compared to FingerprintJS, Fingerprint Identification has numerous advantages. The table below compares and contrasts these two products:
FingerprintJS |
Fingerprint Identification |
|
|---|---|---|
Core Features |
||
|
Basic identification input signals
(screen, os, device name)
|
✓ | ✓ |
|
Advanced identification input signals
(canvas, audio, fonts)
|
✓ | ✓ |
|
Smart signals (output)
(Bot detection, device, network, and user behavior)
|
- | ✓ |
| ID Type | fingerprint | visitorID** |
| ID Lifetime | Only upto a few weeks | Will last several months and sometimes years |
| ID Origin | Client | Server |
| ID Collisions | Quite common | Very rare |
Support for native mobile platforms |
||
| Android SDK | ✓ | ✓ |
| iOS SDK | ✓ | ✓ |
Support for cross-platform frameworks |
||
| Flutter | - | ✓ |
| React Native | - | ✓ |
Advanced Features |
||
|
Incognito mode detection
(See our full
list of supported browsers)
|
- | ✓ |
|
Increased accuracy
(Gained from additional server-side signals (e.g.
TLS crypto support, ipv4/v6 data. etc)
|
- | ✓ |
|
Query API & realtime Webhooks
(Build flexible workflows)
|
- | ✓ |
|
Geolocation
(Based on IP address)
|
- | ✓ |
Operations |
||
| 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.