Build fingerprint and kernel version
Reads the full build ID string and kernel version.
In one line
Can see your exact phone software build, a long label often over 100 characters
Reads the full build ID string and kernel version.
Pins the exact firmware (model, build, patch) and so the OEM and carrier variant. Tight fingerprint; also tells where a phone was sold.
What it can and can't do
What the user does: Nothing. The app can look it up as soon as it opens
It can
- See the full Android build label, with tags and type
- See the kernel version on Android and iPhone
- Use the label as one clue to tell similar phones apart
It cannot
- Learn who you are from this label alone
- See a carrier version on iPhone; Apple gives a plain build and kernel version
- Change the build or install a different one
How it differs between platforms: Android shows a long detailed label. iPhone shows less and only a partial guess in some cases.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 1.0 (API 1) | iOS 2.0 |
| Permission or entitlement | Not listed | none |
| Protection level | none | none |
| How access is granted | none | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | None listed |
| API | Build.FINGERPRINT, ID, DISPLAY, TAGS, TYPE; System.getProperty(os.version) | Build and Darwin version; no carrier variant |
| Notes | Typically 100+ characters | None |
Data you get
What comes back: Build fingerprint
Shape: string
How often: Changes on update
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
fingerprint | string | None | about 100 chars | exact |
Technical limits
- Rooted or custom ROMs often show test-keys in TAGS
The story
What it is
An app can read the exact firmware and system build of your phone.
For you
You never see it. It is a long label with your phone's maker, build and patch. It tells an app what exact software you have and often where the phone was sold.
For makers
Makers use it for bug fixes on one firmware version and for fraud checks. Because the label is so exact, it is also a strong fingerprint detail for tracking.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game applies a graphics workaround for a bug on one phone maker's build. | None named |
| security | A bank notices a login from a build string that does not match a real phone. | None named |
| developer | A crash tool groups crashes by firmware so engineers find the bad update. | Firebase Crashlytics |
| ads | An ad firm adds the build label to a device fingerprint. | None named |
| media | A streaming app checks that a build supports a video codec before offering 4K. | None named |
| shopping | A fraud team spots a fake phone because its build label does not exist. | None named |
Risks
- Strong fingerprint detail
- Shows where phone was sold
Android and iPhone in short
- Android: Available as Build.FINGERPRINT with no prompt.
- iPhone: iOS shows a coarser build number and kernel version through system calls.
Good uses and abuse
Legitimate uses
- Crash reports
Known abuse
- Fingerprint
- Rooted-device detection
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 5 | Rough identifying entropy, when known |
History
- 2008-09, Android 1.0 (API 1): Build.FINGERPRINT available
Related capabilities
Related
- Device model and manufacturer. Can see your exact phone model and maker on Android, and a model code on iPhone
Sources
How well checked: Based on official documentation.