---
Source: https://docs.microblink.com/platform/capabilities/personal-data-checks
Title: Personal data checks
Description: Verify personal data against authoritative government and commercial databases
---

# Personal data checks

:::tip[Availability]
Available in SDK v1.2+
:::

:::info
🇺🇸 US only.

These checks run against US-based identity databases.
If your workflow is used by non-US residents, they won't be found in these databases and the check will return a low or no-match score.
Don't configure automatic rejections based on this capability unless you are certain that all users in your workflow are US residents.
:::

The Personal data checks capability compares data the user has provided against authoritative identity databases to verify its accuracy.
It's primarily used as a fraud signal: a significant mismatch between what the user provided and what appears in the database may indicate identity fraud or misrepresentation.

This capability must come after a step that collected the relevant data: either a [User input](user-input.md) step or a [Scan ID](scan-id.md) step.

## Checked data points

The following data points can be verified, each independently:

- **Address**: verifies that the provided residential address is associated with the identity
- **Phone number**: verifies that the provided phone number is associated with the identity
- **Email address**: verifies that the provided email address is associated with the identity
- **Social Security Number (SSN)**: verifies that the provided SSN matches the identity
  :::note
  The option to check anonymized SSNs will be available in a future version of the platform.
  This checkbox is now available as a feature preview.

  The checkbox, when checked, will also allow matching (rejections) on anonymized SSNs.
  :::

Each data point that's present is checked independently.
You don't need to have all four present; the capability will check whichever are available.

## Score and rules

Each checked data point contributes to an overall match score.
You can configure thresholds for this score and define outcomes:

- If the score exceeds a threshold, the step passes
- If the score falls below a threshold, the step can result in **Rejected** or **Manual review**

The score can also feed into the [Trust score](trust-score.md) capability if it's present later in the workflow.


Last updated on Apr 20, 2026