Before BrightHire runs Deepfake Detection on a live interview, the candidate must explicitly opt in. You collect this consent through your Ashby Application Form, and BrightHire syncs it automatically.
Before you start
Deepfake Detection only runs on live interviews when the candidate has explicitly opted in. Before you add the consent field, make sure that:
Your BrightHire team has enabled consent collection for your organization. Your Customer Success Manager (CSM) turns this on once any required agreement updates are complete. If you're not sure where this stands, reach out to your CSM.
Deepfake Detection is turned on (or will be) for your meeting platforms. Your CSM enables this too.
You have admin access in Ashby to edit the Application Form used by participating jobs and add custom fields to it.
Note: Deepfake Detection consent is separate from interview recording consent. If you already collect recording consent in Ashby, you'll still need to add a new, separate consent field.
Ashby setup
1. Add the consent field
Add a required custom field to the Application Form used by participating jobs. It can be either:
A checkbox: Checked means the candidate consents. Unchecked means they decline.
A single-select field: Give it clear options for consenting and declining.
Link the Application Form across all participating jobs so the field title stays identical everywhere. One BrightHire configuration then covers all of them.
2. Capture the exact values
Record exactly:
The custom field title
If you're using a single-select field: the option representing consent and the option representing decline
For a checkbox, you only need the field title.
3. Share your consent field details with BrightHire
BrightHire needs your exact field title (and options, for single-select) to read each candidate's response from Ashby. Send the captured values to your Customer Success Manager (CSM).
Example consent question:
Placeholder — Not Legal Advice: This language is for illustrative purposes only and is not legal advice or a final legal provision. Please have qualified legal counsel review before use.
"By selecting "Proceed," you consent to [Customer], BrightHire and its vendors collecting, analyzing, and disclosing your facial geometry and voiceprint data for fraud detection purposes. Your biometric information will be deleted immediately after completing the analysis.”
Tips for getting this right:
Copy and paste instead of retyping. The field title and option labels must match Ashby exactly.
For single-select fields, use different labels for consent and decline (e.g. "Yes, I consent" and "No, I do not consent"). If both are the same, BrightHire can't tell them apart and won't collect consent.
Keep the field identical across jobs. Linking the Application Form keeps the same field title on every participating job, so one configuration covers all of them.
Your CSM will set up BrightHire and confirm with you when it's ready.
4. Allow Ashby to sync
You don't need to do anything else. BrightHire picks up candidates' consent answers during its regular Ashby sync. If a candidate answers or changes their response after applying, BrightHire picks that up on the next sync too.
Good to know: If a candidate hasn't answered the field, or declines, BrightHire won't run Deepfake Detection on their interviews. The interview is still recorded and processed as usual, based on your recording consent settings.
If you have any questions about the process, feel free to reach out to your CSM or to [email protected] and we'll be happy to help!