Nightjar Browser security
Short answer
On Windows, rendering comes from WebView2, so page-level security tracks Edge and patches arrive through Windows Update. The Windows installer is signed by Purple Comet LLC and the Mac build is notarized by Apple.
The rendering engine
Nightjar uses WebView2, Microsoft's embeddable Chromium runtime. Site isolation, sandboxing and the patch cadence are Chromium's, and updates arrive through Windows rather than through us — which is faster than a small team could manage.
Signing
The Windows installer is signed by Purple Comet LLC, and the Microsoft Store build is signed by Microsoft. A new release of the direct installer can still show a SmartScreen warning for its first few days while its reputation builds; check the publisher reads Purple Comet LLC before choosing Run anyway.
The Mac build is signed with an Apple Developer ID and notarized by Apple. Builds 0.3.7 and earlier were not signed, which is the only reason macOS would say it cannot verify the app.
What local AI does and does not protect against
It removes a whole class of exposure: there is no vendor holding your documents, no retention policy to change, and nothing for a third party to be compelled to hand over.
It does nothing about prompt injection. A page can contain text written to be read as an instruction, and a local model is as susceptible as a hosted one. What limits the damage is that the assistant has no account, no credentials and no ability to act on your behalf — there is nothing for an injected instruction to spend or send.
It also does nothing about a compromised machine. Local processing moves the entire trust boundary onto your device, which is better if your device is well looked after and worse if it is not.
Other ways people ask this
- is nightjar browser safe
- nightjar browser virus
- Is Nightjar Browser trustworthy? It's unsigned and my antivirus complained.