Scibrarian Download

Privacy

Last updated: September 2026

This website

The site is static files. It has no analytics, no tracking pixels, no advertising, and sets no cookies of its own. Nothing you do here is recorded against you, because there is nothing here doing the recording.

The host that serves the files (Cloudflare Pages) keeps the ordinary request logs any web server keeps — IP address, time, and the file requested — and uses them to serve and protect the site. We do not build anything on top of those logs.

Downloads

Installers are served by GitHub, from the releases page linked on the download page. Clicking a download button sends you to GitHub, which receives that request the way it receives any other and counts it toward the release’s download total. We see the total; we do not see who.

Videos

Demo videos show a thumbnail, not a player. Nothing is requested from YouTube or Google until you click play — at which point an embedded player loads from youtube-nocookie.com and YouTube’s own privacy policy governs what happens inside it.

The enquiry form

The form on the agency page sends what you type in it — your name, email, organization, team size and message — to our inbox, by email, through a transactional email provider. It is used to answer you and to keep track of the conversation that follows, and it is not added to any mailing list or passed to anyone else. There is no account created and no cookie set.

The app

Scibrarian has no account, no sign-in, and no telemetry. It reports nothing to us — there is no “us” server for it to report to.

It does talk to the services it gets its data from, directly from your machine:

  • PubMed/NCBI (US National Library of Medicine) for papers and the MeSH vocabulary. If you set an NCBI API key in Settings for a higher rate limit, it is sent with those requests, as NCBI requires.
  • OpenAlex for journal impact metrics.
  • NIH iCite for citation counts.
  • GitHub, to ask whether a newer version has been released.

Those services see the requests your copy makes, as they would for any client. Your library — papers, topics, settings and any PDFs you add — is stored on your own disk, in your user application data directory, and is not sent anywhere.

Questions

Open an issue on the repository.