What the app never does
A short list of things Context Raven deliberately never does, so you know exactly where the edges are.
Network
While you're signed out and none of your files are shared, the desktop app makes only two requests of its own. Neither carries your notes, file names, paths or keystrokes. The editor works fully offline.
- The check for a new version. The app asks
downloads.contextraven.com, a server we run, whether a newer version exists: when it starts, about every four hours while it stays open, and when its window comes back into focus and the last check was more than an hour ago. Check for Updates… in the File menu asks at once. The server sees your IP address and a label naming the update component and its version. The request carries no account, no identifier and not even the version of Context Raven you run. If a newer version exists, the app downloads it from the same server and installs it only after you click Restart to update. There is no setting to turn the check off. - One anonymous install signal. On the first launch of a released app, it sends a random
number the app made up for itself, your platform and the app version, to
api.contextraven.com. It is sent once; if the server could not be reached, the next launch tries again with the same number. There is no setting to turn it off.
The desktop app loads no analytics or tracking script and has no error-reporting service: it sends no usage statistics, no page views and no crash reports. The web app is different: it reports errors and page-load timings to Sentry, our error-reporting service, through our own server, and it has no setting to turn that off. Website analytics is covered below.
Signing in adds your account's own requests; the plan label in the top-right corner of the Local view is read from your account once after the app starts, once after you sign in, and once when you come back to the app after it sent you to the payment or billing page.
The desktop app has no cookie banner because it sets no analytics cookies. Only public website pages count visits, and only while you are signed out. Shared-note pages and the signed-in web app have no analytics or cookie banner.
On public website pages, analytics loads only after you press Accept in the cookie banner. Reject loads nothing. This browser remembers your choice until the policy changes. If storage is unavailable, it asks again on the next visit. To change your choice, press Cookie settings in the footer of a public website page while signed out.
Leaving those pages or signing in stops further analytics from being sent. Your stored choice stays the same. Returning while signed out resumes analytics only if you accepted, once the public page has opened. Moving between public pages keeps analytics and an open banner active. A page with sign-in tokens, codes or sign-in errors in its address keeps analytics off.
Analytics cookies are removed when you leave the public website pages. They are cleared again shortly after you open another page, and when the page is hidden or left. A reply to analytics sent just before you left can arrive later and restore some cookies. While analytics stays off, these are removed when you next open another page or hide the page. Typing or clicking in the app does not clear them. Opening any page without a stored Accept clears leftover analytics cookies.
Withdrawing consent also stops further analytics from being sent. On public website pages, analytics that was already loaded can still restore cookies when you open another page or click a link. They are removed again right after. A page opened afterwards does not load analytics at all. Your notes are never part of this.
A remote image referenced by a URL is never loaded just by opening or viewing a note. It stays a chip showing the URL. Exporting the note to PDF does fetch its images, so they appear in the file. An HTML file you open loads whatever that file itself references.
We checked this list on a running app on 19 October 2026: a release build of the desktop app was started for the first time, signed out, with every connection it opened recorded. It contacted
downloads.contextraven.comandapi.contextraven.com(the install signal), and no other server, until a note was exported, an HTML file was opened, feedback was sent or someone signed in.
Your files
- Opening a file to read it never writes to it. The first keystroke you make is what unlocks saving, not opening the file.
- Nothing is permanently deleted from this app. Move to Trash always sends a file to the Trash, where the normal recovery applies.
- A path you've excluded for a folder is never read: not scanned, not watched, not searched.
- Renaming or moving a note never changes text you have not saved yet: the open note keeps it exactly as you typed it, and its links are reported instead of updated. See Rename, move and trash.
- Malformed YAML in the frontmatter block is never auto-corrected. It's written back exactly as you typed it.
- A missing file is never recreated automatically, and your unsaved edits for it are never discarded; both only happen if you choose to, from the recovery banner. See When a file goes missing.
Git and the cloud
- Context Raven never writes into your Git repository. Local file history reads your existing commits; it never creates one on your behalf.
- Share to cloud only pushes from your disk outward. Nothing is ever written back from the cloud workspace into a local file.
What starts only when you act
These make a network request, and each one starts with something you do:
- Signing in and using the cloud workspace. Your cloud notes are loaded, and while you are signed in the app keeps one open connection to the server that delivers change notices. In a shared organization space, an open note also tells the server every 20 seconds that you are viewing it, so other members can see it. See Local, Cloud and Sync views.
- Share to cloud sends the file's full text, its name, its full path on your computer and the local images it uses. The path is kept with the cloud note in your own space and is not shown on the public link. The full text is sent again on every change of the file, including a change made by another program, until you stop sharing. See Share to cloud.
- Send Feedback… sends your message, the address you enter, any images you attach, the app version, the platform and, if you are signed in, your account. See Send feedback.
- The form in the Sync view ("Tell me when sync ships") sends the address you type and, if you are signed in, your account. See Raven Sync.
- Download as PDF and Download as Word fetch any remote images the document references, with a 10-second timeout, so they can appear in the exported file. See Export.
- Pull repository contacts the remote of your own repository. See Folder watch and external changes.
- Opening an HTML file runs the file's own scripts, which can load scripts, images and fonts from the internet and contact servers the way a web page can. What such a file sends is decided by the file, not by Context Raven. See HTML files.