Privacy
This describes what Sorcrates actually stores and sends, in plain terms. Two different people's data is involved: yours, as the recruiter using it, and the candidates the product finds. They are treated differently and both are covered below.
What we hold about you
| Data | Why | Kept |
|---|---|---|
| An account identifier and access token | To know which data is yours | Until you delete the account |
| Job descriptions you paste | To produce searches and a scorecard | Stored as part of a tracked requisition; deleted with it |
| Your applicant tracking system API key | To search your own candidate records | Until you disconnect it |
| Usage counts | Fair-use limits and billing | Rolling, per calendar month |
Your ATS key is encrypted at rest with a key held separately from the database, and there is no feature anywhere in the product that reads it back to you or to us. The settings page shows only the last four characters. If you lose it, generate a new one in your ATS rather than asking us to recover it, because we cannot.
What we hold about candidates
When you track a requisition, the overnight run collects candidate records from two places: your own applicant tracking system, using the key you provided, and public search engine results. For each person we store what a search result contains: a name, a job title, an employer, a location, a public profile link, and our own score and assessment.
Retention: 90 days
Candidate records are deleted 90 days after they were first found. This is enforced every time a folder is written, not by a background job that might not run. Deleting a requisition deletes its candidate folder immediately.
What we do not do
We do not sign in to LinkedIn or any other network as you, we do not automate your browser session, and we do not harvest profiles in the background. Searching happens on our servers against a search engine's public results page. We do not sell candidate data, share it between accounts, or use it to build a database that outlives your requisition.
Where data is sent
| Processor | What it receives |
|---|---|
| Anthropic | Job descriptions you paste. For ranking, a shortlist of job titles and employers — never candidate names, emails or profile links. |
| Serper | The search strings a requisition runs. No personal data of yours. |
| Cloudflare | Hosting and storage for everything above. |
| Your ATS provider | Requests we make with the key you supplied, to read your own records. |
The ranking step is worth being precise about, because it is the one place candidate information reaches a third party. It is sent job titles and employers so it can judge relevance. It is not sent names, email addresses, profile URLs or source identifiers, and candidates are referred to by list position. This is enforced in code and covered by tests rather than being a policy we intend to follow.
Generation history
Your recent generations are stored in your browser and are never uploaded. Clearing them from the settings page removes them from the device.
Your rights, and candidates' rights
You can export or delete your data at any time by deleting your requisitions and account, which removes the associated candidate folders with them. If a candidate contacts us asking what we hold about them or asking for removal, we will act on it: write to the address below. Because candidate records expire after 90 days, in most cases the data will already have gone.
Security
Access to your data requires a bearer token that is stored only as a hash on our side and cannot be recovered or printed back. Integration credentials are encrypted with authenticated encryption. We do not currently offer single sign-on, and we will say so plainly rather than implying enterprise controls we have not built.
Contact
Questions, deletion requests, or anything you think this page gets wrong: privacy@example.com.