# Run background checks

> Decide whether Checkr or you collect the candidate's personally identifiable information (PII), then pick your integration flow.


Every integration follows the same lifecycle — **candidate → check ordered → webhooks → report → adverse action** — and that part works the same either way. What actually differs comes down to **one decision: does Checkr collect the candidate's PII and own compliance, or do you?** That single choice determines how much you build *and* how much legal responsibility you carry.

## The core decision: Checkr-hosted vs self-hosted

Before you build, decide **who collects the candidate's PII and owns compliance**:

Checkr-hosted
Checkr collects PII and owns compliance.

* All screening types
* Compliance handled — nothing to maintain
* Fastest to launch


Self-hosted
You collect PII and permanently own compliance.

* US Criminal + MVR only
* You own FCRA disclosures, eSignature, 6+ yr retention, law-change monitoring — ongoing
* You control the candidate UI


Once you've decided, expand the matching option below to see how to build it.

## Checkr-hosted options

Apply Flow — Checkr emails the candidate
You send Checkr the candidate's name and email; Checkr emails them a secure link to enter their PII, consent, and disclosures.

[Start the Quick Start with APIs →](/get-started/quick-start)

Checkr Embeds — drop-in UI, no API code
Add Checkr's pre-built, themeable UI components to your app instead of calling the API directly. To start a check, you fill in the candidate's name and email in the NewInvitation embed, and Checkr emails the candidate the secure Apply Flow link — the same candidate experience as the Apply Flow, with no API code to write.

[Explore Checkr Embeds →](/embeds/overview)

## Self-hosted options

Disclosure & Consent Embed — Checkr handles disclosures
You build the candidate form and collect PII in your own UI, then call the Reports API. The Disclosure & Consent Embed handles FCRA disclosures and eSignature so you don't build that compliance logic — but you still collect and secure the candidate's PII.

**US screenings only — Criminal and MVR.** International, education, employment, drug/health, and credit screenings are **not** supported on self-hosted. Need any of those? Use a Checkr-hosted path.

[Read the Disclosure & Consent Embed docs →](#)

Fully custom — you own all compliance (requires SOW)
You build and host everything — candidate form, PII collection, disclosure forms, eSignature, and compliance storage. Maximum control, maximum responsibility.

This path requires a paid Statement of Work (SOW).
Implementing a fully custom self-hosted flow without the Disclosure & Consent Embed requires engaging Checkr Implementation Services to ensure the integration meets all compliance requirements. Contact your Account Manager or [api-onboarding@checkr.com](mailto:api-onboarding@checkr.com) before starting.

**What you own:**

* Federal, state, and municipal disclosure forms
* eSignature collection (E-Sign Act compliant)
* IP address and timestamp capture
* Storing signed PDFs for 6+ years
* Monitoring for law changes and updating forms
* Uploading the signed authorization PDF to Checkr per candidate


US screenings only — Criminal and MVR.
International, education, employment, drug/health, and credit screenings are **not** supported on self-hosted. Need any of those? Use a Checkr-hosted path.

This is **not a one-time build** — the responsibilities above are ongoing, and Checkr can't assume them for you while you self-host.

[Contact us →](https://checkr.com/contact)