GDPR & data export
Bulk-export candidate profiles and assessment results, and find where privacy requests and retention rules live.
This page covers the organization-wide Data export. To handle a single candidate's privacy request (see, delete, restrict, or object), or to set how long data is kept, use Settings → Privacy requests instead. See Privacy requests and retention.
Exports can contain sensitive personal information. Downloading data doesn't by itself complete a GDPR or other privacy request, and InsightHire doesn't decide your legal obligations.
Where things live
| Task | Where |
|---|---|
| Bulk export of candidates or assessment results | Insights → Data export (/dashboard/data-export) |
| A candidate's request to see, delete, restrict, or object | Settings → Privacy requests |
| How long data is kept | Settings → Privacy requests → Data retention |
| Candidates managing their own data | /my-data (login-free, email link) |
| People who must not be contacted | Settings → CRM & sourcing → Suppression list |
Before you begin
- Confirm you're an org admin. Other users see "Organization admins only".
- Decide the purpose, scope, date range, and format you need.
- Pick an encrypted, access-controlled place to save the file.
- Decide when the working copy will be deleted.
Export organization data
- Go to Insights → Data export.
- Under Data Type, pick Candidate Profiles or Assessment Results.
- Under Format, pick CSV (for spreadsheets) or JSON (for technical teams).
- Under Date Range, pick All Time, Last 30 Days, Last 90 Days, or Last Year.
- Select Export Data.
- Open and check the file before sharing it.
For analytics exports, use Reports instead.
A request about one person
The export covers your whole organization. For one person, start from Settings → Privacy requests. If you need to send someone a copy of their data, filter an export down to that person in a spreadsheet, remove everyone else, and check every identifier before sending. Record what you sent and when.
Report API keys
The same page has Report API keys (BI feeds) for read-only reporting tools. Create one key per tool, give it only to its owner, store it in a secrets manager, and revoke it when the tool is retired. See BI data feeds.
Security checklist
- Keep exports to authorized org admins.
- Encrypt files at rest and in transit.
- Never put exports in public links, source control, or widely shared drives.
- Check recipients before sending.
- Delete temporary copies when the purpose is done. An export is an extra copy your retention policy must cover.
