Candidates must consent to being screened before a background check is requested. These consent forms will be handled differently depending on whether you use Checkr's Dashboard or API to request background reports.
Consent through the Checkr Dashboard
If you are using Checkr directly through the Dashboard and requesting reports via invitation links sent by Checkr, we will store completed consent forms on your behalf.
Once a candidate e-signs the “Acknowledgment and Authorization for Background Check” form, a PDF version of this document is generated and stored on Checkr’s servers.
Consent through the API
If you request consumer reports via API, you are required to store and maintain the candidate's consent form. Collecting proof of authorization is a requirement of the end-user of background reports -- that is to say, the company hiring or engaging candidates.
If you are audited, you must must be able to furnish copies of the authorization for background check.
Copies must be stored for at least five (5) years. This means that your custom API flow must include a mechanism for storing the candidate's consent. We recommend doing the following:
- Make sure the user is identified by username and password
- Have the candidate type their name in signature box
- Upon submission of authorization, generate a PDF of the authorization form and store this PDF on your internal system
- On the PDF, store date/timestamp and store candidate IP Address