This is the version that shipped with Nightjar Browser 0.3.13. The current one is at /privacy.html.
Privacy Policy — Nightjar Browser
Published by Purple Comet LLC. This describes what the software does, written directly from the code rather than from intent, and is accurate as of the date below.
Every factual claim here is checked against the code by an automated test, so a change that makes one of them untrue fails the test suite rather than sitting here unnoticed. The Terms of Use covers using the software and the Licence covers the software itself.
Last updated: 2026-10-28 · Applies to: Nightjar Browser 0.3.13
The current version is the one at nightjarbrowser.ai/privacy.html. It supersedes any other copy, including one that came with an earlier download. What changed, and when, is in §10, with each earlier version kept on the site.
The short version
Nightjar Browser has no servers. There is no account, no login, no telemetry, and no analytics. Nobody operating this software receives your browsing history, the pages you open, what you type, or what you ask the assistant — because there is nowhere for that to be sent.
Being a browser, it still contacts the websites you visit, exactly as any browser must. The rest of this document is about the handful of other things it contacts, and what it keeps on your own computer.
1. What we collect
Nothing. No usage data, no crash telemetry, no analytics, no unique identifier, no advertising ID.
This is a property of the code, not a promise about our conduct: the application contains no telemetry client and no endpoint to send one to.
2. The AI assistant
The assistant runs entirely on your machine. Model weights are executed by
llama-server, a child process on localhost. There is no API key and no
inference provider.
The page you are reading, your chat messages, files you attach, and text the assistant writes into form fields are processed locally and are never transmitted to us or to any third party.
Voice input stays on this computer. The microphone is used only while the 🎤 button shows it is recording, for ten minutes at most. The recording is held in memory, transcribed on this machine by the Whistle speech engine, and deleted as soon as it has been read; the transcript is put in the chat box or the field you are typing in. No audio, and no transcript, is sent anywhere or kept.
Better search in long pages stays on this computer. When it is on, the passages of a long page or file and your question are turned into numbers by the EmbeddingGemma 2 model running on this machine, to find the passages that match in meaning, and the bge-reranker-v2-m3 model, also on this machine, reads the question beside the best of them to pick which answer it. The numbers are held in memory and dropped when Nightjar closes; nothing is sent anywhere.
Password fields are never read. A password box, or a field that marks itself as holding a password, a one-time code or a payment card's number, security code or expiry, is left out of everything the assistant, the agent and the writing assistant see: its value is not read, not sent to the model and never filled by the assistant. Nightjar does not store passwords; use the password manager you already have.
One setting can change that, and only if you set it. Under AI settings you may point the browser at another OpenAI-compatible engine. Nightjar also offers engines it finds already running on this computer — Ollama, LM Studio, llama.cpp, vLLM — on their usual loopback ports; those are other programs on your own machine, and using one sends nothing over a network, though what that program does with what it receives is governed by that program and not by us.
An engine at an address that is not this computer is different in kind: everything the assistant reads is sent to it, which means the open page, your chat messages and any file you attached leave this machine and are handled by whoever runs that server. Nightjar warns before saving such an address, marks it as remote in the model picker, and never selects one on its own. Discovery of local engines can be turned off entirely in the same settings pane.
3. When Nightjar Browser contacts the network
Beyond the websites you choose to visit:
| What | Where | When |
|---|---|---|
| Searches | google.com, duckduckgo.com |
Only when you search, from the start page or the address bar (Google or DuckDuckGo in Settings) |
| Model downloads | huggingface.co |
Only when you choose to download a model |
| Search model for long pages | huggingface.co |
Once, when you agree to it or turn on "Better search in long pages": the EmbeddingGemma 2 and bge-reranker-v2-m3 models, about 946 MB, checked against fixed hashes. Nothing about you or your pages is sent |
| Voice input engine | huggingface.co |
Once, the first time you press the microphone button: the Whistle speech engine and model, about 18 MB, checked against fixed hashes. Nothing about you or your voice is sent |
| Inference runtime downloads | github.com |
Only when a runtime is installed or updated |
| Update check | api.github.com |
Once on launch, and when you press "Check for updates". Sends the version you have and nothing else. Switch it off in Privacy & blocking |
| Installing an update | github.com |
When the update check finds a newer version this copy can install: downloaded in the background and installed the next time you close or restart Nightjar. With "Download updates automatically" off, only when you press Update and restart. The file is checked against the checksum GitHub publishes (and on macOS, that Apple notarized it and our developer signed it). Nothing about you is sent. Only the program is replaced; everything in §4 is kept |
| Built-in app updates | github.com |
With the update check, on launch and when you press "Check for updates": the list of the newest versions of the apps built into Nightjar, such as Scribble, and any newer app it names. The list must carry our signature, checked against a key built into Nightjar, and each file the checksum the list gives; anything else is discarded. Sends the version you have and nothing else. Your notes are not touched. Switched off with the update check, or on its own with "Update apps only with new browser releases" |
| Ad/tracker filter lists | easylist.to |
The first time the browser starts, then every three days while "Update the blocklist automatically" is on (on by default). A plain download: nothing identifying is sent |
| The page engine's own connections (Windows) | Microsoft | Microsoft Edge WebView2, the page engine Windows provides, connects to Microsoft by itself — when Nightjar starts, and from time to time after — for its own services, such as Microsoft Defender SmartScreen's checks of sites and downloads. Nightjar does not make these connections, sends nothing through them and cannot see what they carry; Microsoft's privacy statement covers them |
| Model catalogue sync | remote registry | Only if "Registry sync" is on (off by default) |
| Address-bar suggestions | your search provider | Only if "Online suggestions" is on (off by default) |
Each of these sees your IP address, as any web request does. The update check
sends a User-Agent of NightjarBrowser/<version> and nothing identifying the
machine.
The new-tab page makes no request at all. Opening a tab loads a page that ships inside the application: a search box, no script, no fonts or images fetched from anywhere. Nothing is contacted until you search, and searching goes to your search engine exactly as typing the same words into the address bar does.
You can change this under Settings → Privacy & blocking → New tabs open on, which also offers Google's own page and a blank tab.
4. What is stored on your computer
In your application data folder
(%LOCALAPPDATA%\NightjarBrowser on Windows,
~/Library/Application Support/NightjarBrowser on macOS):
-
Settings — your preferences, in
settings.json. -
Usage counts — how many times each of a few features has been used (a message sent in the AI panel, a summary, a Fill, voice input, and so on) and on how many days, also in
settings.json. Counts only: never what was asked, on which page, or with which file. They leave this computer only in a feedback report you send yourself (§5a). -
Browsing history — off by default. Nothing is written down unless you turn on Remember the pages I visit under Privacy & blocking, and turning it back off deletes what was recorded. When on: recent addresses, kept locally and capped.
-
The tabs you had open — their addresses only, so a crash puts them back rather than losing them. Not scroll position, not what you typed into a page, not per-tab history. Removed by Clear browsing data along with everything else.
Closing the browser normally does not bring them back next launch: a new window starts on a new tab, as in every other browser, and the addresses are erased as it closes. They are kept past a normal close only if you turn on "Reopen my tabs when I start the browser" in Settings.
-
Sites you have made a choice about — where you allowed ads, allowed or blocked pop-ups, or turned on form autocomplete. Only the site names, only the ones you chose, shown one at a time in the shield panel while you are on that site. On Windows they are encrypted at rest with DPAPI, like your profile; on macOS they are stored in the same owner-only file as the other settings.
-
Bookmarks — locally. These are kept whatever the history setting says: a bookmark is something you asked to keep.
-
A list of what you downloaded — the address, filename and where it was saved. Follows the history setting: with history off it is emptied when you close the browser. The downloaded files are never touched — deleting your own file would be data loss rather than privacy.
-
Saved conversations — off by default. Chats stay in the window and are gone when you close it, unless you tick Save conversations on this computer above the Recent chats list. Turning it off deletes what was saved. When on, they are stored locally and never uploaded.
-
Downloaded models — often several gigabytes.
-
Filter lists — the compiled ad/tracker block list.
-
A key for the local AI engine — a random token in
engine-key.txt, rewritten each time the engine starts and deleted when it stops. It authenticates this browser to thellama-serverprocess on your own machine; it is not an account, and it is not sent anywhere. -
Profile and password data — encrypted at rest using Windows DPAPI or the macOS Keychain, so it is readable only by your operating system account.
None of this is synchronised, backed up, or transmitted. Deleting the folder deletes all of it.
Cookies. Private browsing is on by default: cookies are held in memory and discarded when the browser closes, so you sign in again each launch. The same goes for the page cache and the web engine's own record of pages visited — the browser runs its web engine in InPrivate mode, which keeps them in memory only. Turning it off in Settings keeps them on disk instead.
The one exception you can make is per site: turn on the Keep me signed in switch (🔑) beside the address. While any site is kept, the web engine uses its normal profile on disk instead of InPrivate — as Chrome and Firefox do for their "clear on close, except these sites" settings — so that site stays signed in. Every other site's cookies, and the browsing history, cache, download history, autofill and every site's stored data, are deleted when the browser closes, and at the next start if it did not close normally. Until then they are on disk, in the browser's profile folder, like any browser's.
A site first kept during a private session has its cookies saved — encrypted at rest with Windows DPAPI or the macOS Keychain — until the next start, which puts them into the profile and deletes the copy. Turning the switch off means that site is forgotten when the browser closes; Clear browsing data deletes everything at once.
5. Crash reports
If the application crashes it writes a report to your own machine and shows it to you. Nothing is uploaded. There is no crash-reporting endpoint. If you choose to send it, you do so yourself, by email, having read it.
A report contains the error, a hardware and OS description, which model was last loaded, and the app's own startup errors. On Windows it also lists what Windows Error Reporting recorded: the faulting module and exception code. It deliberately excludes browsing history, page URLs, page content, chat messages, attachments, cookies, and the inference server's log.
fatal.log. Some crashes kill the process outright, giving the application
no chance to write anything. For those, a Python stack trace is written to
fatal.log in the data folder as the process goes down. It holds file names,
line numbers and function names — not variables, not page text, not chat
messages. It does contain the full paths of the files involved, which on
Windows include your user name.
Freezes and hangs. Any time the window stops answering for a second or
more, one line goes into stalls.log in the data folder: when, for how long,
and which function it was in. If it stops answering for ten seconds, every
thread's stack is written to fatal.log while it is still happening, the same
kind of trace as above. Neither holds a page, an address or a chat.
After a crash or a hang, the next launch says so once and offers to send a report. That button only opens Send feedback (below); nothing is sent by it.
Crash dumps are a different thing, and are not ours. If you or your system
administrator have switched on Windows' LocalDumps for this application,
Windows writes a memory dump to %LOCALAPPDATA%\CrashDumps. A full dump is a
copy of everything the process had in memory, which can include the page you
were reading and what you asked about it. Nightjar does not create these, does
not read them, and never attaches one to a report — it only tells you
that one exists, so you can decide what to do with it. Deleting them is safe.
5a. Feedback
Send feedback in the ⋮ menu writes a report and shows you all of it before anything happens to it. Nothing is uploaded. The buttons copy it to your clipboard and open a feedback form in a tab, or save it to a file; the browser itself makes no request. You choose between a mail draft, which opens your own mail app with the report ready to send, and copying it to paste into a feedback form — and in both cases what leaves is a decision you take, after reading it.
The report carries the version, your hardware and OS, which model and runtime
are loaded, whether Smart App Control is on, and the recent lines from the
Activity tab. Unless you untick it, it also carries the last few days of crash
and freeze logs: the stacks in fatal.log, a summary of stalls.log, and your
system's crash reports for this app, with your user name removed from the
paths. It excludes browsing history, page content, chat messages,
attachments and the inference server's log — the same exclusions the
crash report makes, for the same reason.
The page you are on and your last question can be added by ticking a box. It is off by default, and the preview grows to show exactly what ticking it adds, so nothing travels that you have not read.
Unless you untick it, the report also carries your usage summary (§4): on how many days you have used the browser, since which month, and how many times each counted feature was used. After a week of use the browser asks once whether you will answer two questions about how you use it; answering opens this same report with the questions in it. "Not now" asks once more a month later; "Don't ask again" ends it.
6. What we send on your behalf
Nightjar Browser sends Global Privacy Control with your requests —
Sec-GPC: 1 and DNT: 1 headers, and the navigator.globalPrivacyControl
property. Under CCPA/CPRA and several other laws this is a binding instruction
to a site not to sell or share your personal information.
On Windows the headers accompany the page itself and the request types that carry tracking — scripts, XHR, fetch, websockets, beacons. They are not attached to images, media, fonts or stylesheets: a video fragment is not something a site makes a selling decision about, and stamping every one of them measurably destabilised the browser during playback.
On macOS they accompany top-level page loads only; WKWebView provides no way to attach headers to subresource requests. The JavaScript property is present everywhere on both platforms.
It also blocks requests to known advertising and tracking hosts, and suppresses cookie-consent banners, before those requests are made.
6a. The website, NightjarBrowser.ai
This policy covers the website as well as the software, because the two are published by the same company and the site is where you are most likely to be reading it.
The site sets no analytics. No Google Analytics, no Plausible, no telemetry, no advertising pixel, no tracking cookie. There is no account and no login, so there is nothing to log you into.
What it does contact. The download button asks api.github.com for the
latest release so the version and file size shown are current. GitHub receives
that request, including your IP address, as it would for any page that embeds
a resource. The site's pages also load a script from purplecomet.co, the
site of Purple Comet LLC, which publishes Nightjar: it draws the "A Purple
Comet Product" menu linking our other products. Loading it gives Purple Comet's
server your IP address and the page you are on, as any request does; the
script sets no cookie, stores nothing and sends nothing further. Those are the
only two places the site talks to.
Do Not Track. Several laws, California's among them, require a site to say how it responds to a browser's Do Not Track signal. The honest answer here is that it makes no difference: the site does not track visitors whether the signal is present or not, so there is no behaviour for it to change. Global Privacy Control is treated the same way, for the same reason.
Cookies. The site sets no cookie for its own purposes. A component library used in the layout can set one to remember whether a panel is open; it is functional, stays on your device, and identifies nothing.
Legal pages. The privacy policy, terms, licence and third-party notices on this site are generated from the product's own repository, which is the copy its test suite checks against the code. Where the two could ever disagree, the repository copy is the one that has been verified.
7. Third parties
Nightjar Browser is not affiliated with the sites you visit. When you download a model or a runtime, that download is subject to the terms and privacy practices of the host (Hugging Face, GitHub) and the licence of the model itself — the Licence §5 lists the components that ship inside the application and the licences they arrive under. When you search or open a new tab, that is subject to Google's or DuckDuckGo's terms and privacy policy (depending on the search engine chosen in Settings).
8. Children
Nightjar Browser is not directed to children under 13, and collects no personal information from anyone.
9. Your rights
Because we hold no data about you, there is nothing for us to disclose, correct, export, or delete. Everything the software stores is on your computer and under your control. Requests of that kind should be directed to the sites you visited, not to us.
10. Changes
Material changes are listed here, newest first, with the date and the release they apply to. Because there is no account, we have no way to notify you individually. Each earlier version is kept at NightjarBrowser.ai, linked at the foot of this page.
- 2026-10-28 — The website loads a script from
purplecomet.cothat links Purple Comet's other products (§6a). It sets no cookie and sends nothing beyond the request for the script. The contact address is now contact@nightjarbrowser.ai (§11). - 2026-10-28 · 0.3.13 — Added DuckDuckGo as a search engine you can
choose in Settings; searches, and address-bar suggestions when they are on,
then go to
duckduckgo.cominstead of Google (§3, §7). Scribble's reminders can be opened as a Google Calendar event, which openscalendar.google.comonly when you press that button. - 2026-10-26 · 0.3.12 — Added that the page engine on Windows, Microsoft Edge WebView2, contacts Microsoft by itself for its own services such as SmartScreen (§3); it always has, and this policy did not say so. A local HTML file can no longer read other files on this computer. With private browsing off and "Remember the pages I visit" off, the page engine's own history is now cleared on close and at each start; before, it kept every page visited. A site's "Always allow" to open an app is no longer kept from a private session. A newer version found by the update check is now downloaded in the background and installed at the next restart, unless "Download updates automatically" is switched off (§3).
- 2026-10-25 · 0.3.12 — On Windows, the update check also downloads newer
versions of the built-in apps, such as Scribble, from
github.com(§3): only a list signed by us, and files matching it. It sends nothing more than the browser's own check, and is switched off with it. - 2026-10-24 · 0.3.12 — Better search in long pages also downloads and runs a second model on this computer, bge-reranker-v2-m3, which picks which of the passages found answer the question (§2), downloaded with the search model (§3). Nothing more is sent anywhere.
- 2026-10-19 · 0.3.8 — The website moved to NightjarBrowser.ai (§6a). The
browser fetches the model catalogue from there when Registry sync is on, and
opens its help, privacy and security pages there. trynightjar.com still
serves the same site. A few features' use is counted on this computer (§4),
and Send feedback can include those counts, shown in full (§5a); after a
week the browser asks once for two answers. Freezes are recorded in
stalls.logandfatal.log(§5), and Send feedback carries the last few days of crash and freeze logs unless you untick it (§5a); the next launch after a crash offers to send one. The browser can install an update itself when you press Update and restart (§3); it downloads only the new version and replaces only the program. - 2026-10-15 · 0.3.6 — Added Keep me signed in (§4): while any site is kept, the web engine uses its profile on disk instead of InPrivate, and everything not kept is deleted when the browser closes and at the next start. A site kept during a private session has its cookies saved, encrypted, until the next start.
- 2026-10-08 · 0.3.5 — Added voice input (§2): the microphone is used only while recording, audio is transcribed on this computer and never kept or sent. Its engine is downloaded once from Hugging Face (§3). Added Better search in long pages (§2): passages and questions are turned into numbers by a model on this computer, held in memory only; the model is downloaded once from Hugging Face when you agree to it (§3).
- 2026-10-04 · 0.3.4 — Added that password, one-time-code and payment-card fields are never read (§2). In 0.3.3 and earlier they were: the value of such a field could be included in what the assistant read from a page and in what the writing assistant was sent when you clicked into one.
- 2026-09-29 · 0.3.1 — The ad/tracker filter lists (§3) are refreshed only while "Update the blocklist automatically" is on, as it is by default; in 0.3.0 that setting did not control them. This page became the authoritative version, with each earlier one kept on the site.
- 2026-09-27 · 0.3.0 — With private browsing on, the web engine keeps browsing history, cache and site data in memory only; earlier builds wrote them to disk despite the setting. The addresses of open tabs are erased when the browser closes normally unless "Reopen my tabs" is on. Added the list of sites you have made a choice about (ads, pop-ups, autocomplete), encrypted on Windows.
- 2026-09-11 · 0.3.0 — The update check runs once at launch as well as on request, sending only the version you have; it can be switched off. Added §6a on the website itself.
- 2026-09-10 — Named the publisher, Purple Comet LLC, and the contact address.
- 2026-09-06 · 0.2.9 — Nothing is kept by default: browsing history, saved conversations and the download list are off. A new tab contacts no one; it used to open google.com.
- 2026-09-04 · 0.2.7 — Added the key the browser uses to talk to its own AI engine.
- 2026-08-28 · 0.2.6 — Described pointing the assistant at another AI engine, and that one on another machine receives what the assistant reads.
- 2026-08-24 · 0.2.5 — Named the licences and components that ship inside the application.
- 2026-08-20 · 0.2.0 — First version.
11. Contact
contact@nightjarbrowser.ai
Purple Comet LLC, a California limited liability company.