Back to About

Privacy

Quarry · Last updated 21 November 2026

Quarry saves your notes in your browser on your device. A note leaves it when you use a feature that sends it: saving to your GitHub repository, asking an AI whose key you added, or one of the other services listed on this page.

What's Stored on Your Device

Notes, Drafts & Attachments

Everything you write and attach, with the search index Quarry builds from it. Saved unencrypted.

Stored in: IndexedDB

Content Growth Metrics

Tracks how your knowledge base grows over time - thread counts, word counts, tag evolution.

Stored in: IndexedDB

Reading History

Which threads you've visited and when, and how far you read each one.

Stored in: localStorage and IndexedDB

Bookmarks

The threads you bookmark, with your notes on them.

Stored in: localStorage

Highlights & Annotations

Your highlights and annotations on threads.

Stored in: localStorage

Preferences & Settings

Theme, font size, sidebar mode, and other display preferences.

Stored in: localStorage

What Quarry Encrypts, and What Leaves Your Device

Saved encrypted

Your AI provider keys, the GitHub token you save in Settings and the passwords of database connections: AES-256-GCM through the Web Crypto API, under a key derived from this browser with PBKDF2-SHA256 (100,000 iterations). A GitHub token you enter in the viewer's API Access panel or when you publish a table stays in that tab until you close it; tick Remember on this device and it is saved encrypted with AES-256-GCM, under a random key that stays in this browser.

Saved unencrypted

Your notes, drafts, bookmarks, reflections, search index and reading history, in this browser. Anyone who can open this browser profile can read them; a Quarry password locks the app, and your device's disk encryption protects its files.

Sent when you use a feature

Saving to a connected GitHub repository sends your notes to GitHub. Asking an AI sends your text to the provider whose key you added; with Ollama it goes to the Ollama server at the address you set, which is your own machine unless you change it. The list below names every feature that sends something. Quarry keeps no copy of your notes on a server of its own.

What Each Feature Sends

Each of these runs when you use it, and sends from your browser to the service named, over HTTPS.

Saving to GitHub
Sends: The notes and files you save
To: GitHub, in the repository you connect
Asking an AI
Sends: Your question and the note text sent with it
To: The provider whose key you added: OpenAI, Anthropic, OpenRouter or Mistral. With Ollama, the Ollama server at the address you set: your own machine unless you change it
Web research
Sends: Your search words
To: The search service you pick: DuckDuckGo, a SearXNG server, Brave, Serper, SerpAPI, SearchAPI or Google. Paper searches go to Semantic Scholar
Citations
Sends: The DOI, arXiv ID or title you look up
To: Crossref and arXiv
Dictionary
Sends: The word you look up
To: Free Dictionary API and Datamuse
Cloud voices
Sends: The text read aloud, or the audio you dictate
To: OpenAI or ElevenLabs, with your key. Your browser's own voices and speech recognition are run by the browser, which may send audio to its maker's service
Importing or previewing a web page or PDF by its address
Sends: The address
To: A public relay that fetches the page: AllOrigins or corsproxy.io
Running Go or Rust code
Sends: The code block
To: go.dev and play.rust-lang.org
Google Calendar
Sends: The planner events you sync
To: Google Calendar, after you connect your Google account
Importing from Google Docs
Sends: The folder you pick, and a request for each document in it
To: Google Drive, after you connect your Google account
Checking a license key
Sends: The key
To: Gumroad
Opening Quarry
Sends: A request for each page and file, which shows your IP address
To: Cloudflare and GitHub Pages, which serve quarry.space. Some features were built for a Quarry server and send their request to quarry.space itself (image analysis and generation, voice-note transcription on the canvas and email sign-in among them). Quarry runs no server, so quarry.space refuses those requests and passes nothing of them on
Embedded media and the search model
Sends: A request for the file, which shows your IP address
To: The site whose media you embed (YouTube, Vimeo, Spotify, SoundCloud and others), and Hugging Face and jsDelivr for the search model

You're in Control

Password Lock

Lock Quarry on this device with a password, kept only as a salted SHA-256 hash.

Export Anytime

Export your notes from Settings as Markdown files in a ZIP, a Word document or one JSON file with their metadata. Attachments are not in the export.

Delete Everything

Clear all local data from Settings. Notes you saved to GitHub stay in your repository until you delete them there.

Analytics

Quarry's pages about Quarry (the home page, About, FAQ, Privacy, Changelog, Architecture and the API reference) run Google Analytics without cookies until you choose in the cookie bar, and with cookies once you accept. Microsoft Clarity runs only after you accept. With Do Not Track on, neither runs. The app runs neither.

FeatureThe appPages about Quarry
Google AnalyticsOffCookieless; cookies after you accept
Microsoft ClarityOffOnly after you accept
Cookie BarNot shownShown
Usage AnalyticsIn this browser (IndexedDB)Google and Microsoft

Who Runs Quarry

Quarry is made and run by Manic Agency LLC.

Manic Agency LLC2831 St Rose Parkway, Suite 200, Henderson, NV 89052, United States

Questions about privacy? Email team@manic.agency.

Open Quarry

Changes to This Page

  • Says that a GitHub token you enter in the viewer's API Access panel or when you publish a table stays in that tab until you close it, and is saved encrypted only when you tick Remember on this device. Earlier versions kept it as plain text with your preferences; Quarry moves a token kept that way into the encrypted form and deletes the plain copy. Says that bookmarks, highlights and the list of threads you visited are kept in this browser's local storage, and how far you read each thread in its database.
  • Says that Ollama receives your text at the address you set for it, which is your own machine unless you change it, and adds importing from Google Docs to the list of features that send something.
  • Says where Quarry keeps your notes (this browser's database, unencrypted, and your GitHub repository when you publish notes to it), what it encrypts (AI provider keys, the GitHub token you save in Settings and database connection passwords) and what leaves your device, with a list of every feature that sends something, what it sends and to which service. Earlier versions of Quarry's pages said every note was encrypted and that a private sync service was coming; Quarry encrypts only those keys and passwords, and runs no sync service. Names Manic Agency LLC, which makes and runs Quarry, with its address, and says how the analytics on Quarry's pages about Quarry run.