How Oortcloud Job Hunter handles data
This page summarises the data model behind Job Hunter. It describes what the platform stores, how it is isolated between organisations, and how the AI features are billed and authenticated. For the full contractual policy covering your organisation, contact us.
What the platform collects
Job Hunter reads publicly available content from the career pages and job boards you point it at, together with the organisation details, tracked companies, saved searches, recipient lists and documents your team creates inside the platform.
Organisation isolation
Tracked companies, snapshots, saved searches, notifications, documents and analytics are scoped to your organisation. Another organisation using the platform never sees your universes or your findings.
Your own AI and search keys
OpenAI and Exa keys are stored per organisation and used only to run the AI features you trigger — intelligence reports, executive search, AI search and semantic matching. There is no shared deployment-wide key and no pooling of usage across customers.
Stored results and retention
Search results are stored with their timestamps, which is what makes it possible to see what has changed between searches and to keep an audit trail. Stored results remain available to your organisation to revisit, share and download.
Accountability
System events such as scrapes, notifications, report generation and user logins are logged with timestamps. Role-based access determines who can see and change what.
Questions about data handling? Email support@oortcloud.ai.