How HireSight handles data

It supports a decision, it never makes one

HireSight surfaces evidence and questions to ask. It does not score people as hireable, does not rank candidates against each other, and never rejects anyone. Every finding shows both original values so you can judge it yourself. Findings come from public sources and can be incomplete or out of date — verify anything you act on.

Where the data comes from

• The resume file the customer uploads.
• Public LinkedIn profile pages, collected logged-out through BrightData. No logging in, no connection requests, no private or connections-only data.
• The public GitHub API.
• Public web and news search results for the candidate's name.

HireSight does not buy data brokers' files, does not look at credit, criminal, or medical records, and does not attempt to identify anyone from a photograph.

How long things are kept

Anonymized statistics are counts and categories only — how often a kind of discrepancy appears, how accurate the tool is. They carry no names, links, filenames, or quoted text, so they cannot be traced back to a person.

If you are the candidate

Write to mikkicon.jobs@gmail.com and you can ask for a copy of anything HireSight holds about you, ask for it to be corrected, or ask for it to be deleted. Deletion removes the resume file, the analysis, and the cached profile data. Requests are answered within 30 days and you never have to explain why.

Who else processes the data

OpenAI (analysis), BrightData (public profile collection), MongoDB Atlas (storage), AWS S3 (file storage), Vercel (hosting). Resume content is not used to train anyone's models.

Sharing a report

Reports are private by default. A report becomes viewable by link only when its owner explicitly turns sharing on, and can be switched back off at any time. Shared reports never include the resume file itself.