Before a deal or a hire, teams usually check documents, registries and references. Many questions remain: did the person really work where they say, how long has their professional history existed, are they posing as someone else. The answers often sit in the open: profiles on professional sites, public repositories, publications. Oracul collects them into one profile with sources.
What gets checked
- Name and role against public profiles: do the name, employer and occupation match.
- Footprint age: how long the person's history online goes back. A professional with years of experience and a trail a couple of months old is a reason to ask questions.
- Publications: repositories and activity on GitHub and GitLab, posts on Habr, dev.to and Medium, public Telegram channels.
- Linked identities: which other usernames and emails lead to this person, and where each link came from.
- Breaches by email, on paid plans.
The namesake is the main risk
In a counterparty check a mistake costs more than in a search: you can walk away from a deal over someone else's past. So Oracul shows a confidence level and a reason for every account, and moves namesakes, other people's names and different faces on avatars into a separate list. If the analyst spots an error, they mark the account "not them", and the whole branch found through it leaves the profile.
Candidate checks: only what relates to the job
Hiring is a sensitive case. A digital footprint helps verify what was stated: experience, public work, professional history. It must not become a reason to reject someone over their views, private life or group membership. Discrimination in hiring is explicitly prohibited by Oracul's rules.
- State the purpose before the scan: "confirm the experience and public work of a candidate for a lead engineer role".
- Look at facts relevant to the role and keep everything else out of the decision.
- Consent and notice requirements for candidates depend on the country and your role, so check them with counsel.
- Delete the scan after the decision: DELETE /v1/scans/{id}.
What a digital footprint cannot replace
Oracul works with people's public profiles. It does not check companies against registries, court records, sanctions lists or PEP lists. For AML and EDD it adds context to those checks (who the person is online, who they are linked to) but does not replace them.
How to run it
In the console, enter everything you know: username, email, phone, full name, known location. The scan shows links being found and builds a profile you can export to HTML or JSON. For a stream of checks, run the same scan through POST /v1/scans, get a webhook when it is done, and keep an audit log with the purpose of every check.