Local-first records
Saved jobs, candidates, and notes are designed around an app-managed local database for the desktop MVP.
Candidate data is not casual data.
CmdHire is being built for recruiting teams that handle sensitive career information every day. The MVP keeps the data path narrow, visible, and practical.
No screenshot-first capture
The preferred context path is browser page context, not image capture of a recruiter’s screen.
Model choice
Teams can use local Ollama-style models where appropriate, remote APIs where approved, or basic offline workflows.
ATS integration path
Greenhouse and Lever workflows are planned around deliberate account authorization rather than asking every recruiter to manage API keys.
Policies will tighten as the product moves from pilot to production.
Before public rollout, CmdHire should complete formal legal review, subprocessor disclosures, data retention controls, and an enterprise security packet.