AI privacy & data — what gets sent
For recruiter teams that need to know exactly which candidate fields go to AI and which never leave our database.
Candidate PII is never sent
When you (or any AI feature) needs to consider a candidate's profile, GreenHired strips PII before composing the prompt:
- Candidate name — replaced with placeholder
- Candidate email and phone — stripped
- Candidate resume PDF — never sent (we only use the structured profile)
- Candidate account ID and IP — never sent
Salary advisor sends zero candidate data
The salary advisor uses only role/location/seniority signals from your job draft. No candidate-side data is involved. This is the most permissive feature — safe to use even when you have strict data policies.
JD writer / improver
These send the job posting content itself (which is meant to be public). No employer-side PII like team-member names or internal Slack channels is included.
Cache vs. log
AI output is cached in Cloudflare KV for speed (24h-7d depending on feature). The cache is keyed on the input — same input = same response, no re-call. The audit log keeps redacted metadata for 90 days, then purges.
Disabling for the whole company
If your company has a "no AI on candidate data" policy, the owner can flip the AI toggle off on /recruit/company. All AI endpoints return 403 immediately. The audit log still exists for past calls but no new ones can be made.
Need something else?
Did this article miss the mark, or do you have a question we have not covered yet? The GreenHired team is happy to help.