Privacy

Updated 22 October 2026

Your vault is a folder of plain Markdown files on your computer. The app works on them there and never sends them to us. This page says what the app, Vaultite Cloud and this site do keep, and who else sees anything.

Who runs Vaultite

Vaultite is run by Lucas Takayasu. It's open source under the Apache License 2.0: the code is at github.com/Vaultite/vaultite, so you can check what this page says against it.

The app

• No account, no telemetry, no analytics and no ads.
• Errors stay on your computer. The app keeps a record of its own errors and crashes, for 30 days, so you and your agents can read it (vau errors). It's never sent anywhere.
• Updates: the desktop app checks vaultite.com/updates for a new version when it starts and every few hours. Like any download, the request carries your IP address. We don't log these requests.
• Plugins: if you've installed plugins from the directory, the app reads its list (and which versions are blocked) from GitHub, at most once a day. Otherwise only when you browse it.
• Browser: once you open a web page in the desktop app's Browser, Shields download the ad and tracker lists uBlock Origin uses (from uBlock Origin's servers, pgl.yoyo.org and GitHub) and refresh them once a day.
• Everything else it fetches is something you asked for: a page you clip or open in the web viewer, a plugin you install.

AI apps you connect

When you connect an AI app (Claude, ChatGPT, Muse, Grok and others) or run an agent like Claude Code or Codex on your vault, what it reads goes to that company under its own privacy policy. Vaultite decides what they can reach; what they do with it is up to them.

Vaultite Cloud

Vaultite Cloud is optional. You sign in at cloud.vaultite.com with Google or GitHub, and it gives your computer an address at <handle>.vaultite.app, so AI apps can reach your vault over MCP while your computer is on. You don't need it to use Vaultite. What it keeps:

• The Google or GitHub account you sign in with: its id and its verified email address.
• The handle you choose.
• The computers you connect: the name each one gives, when it was added and last seen, and a hash of its token.
• A hash of each browser session, for 30 days.
• Counts per handle and day: how many requests, their size, errors, and which AI app signed in. Never what a request carries, its path or who sent it. Kept for 90 days.

Requests from AI apps to your address pass through the relay to your computer, and its answers come back the same way. They're encrypted on the way (HTTPS), but not end to end: the AI apps have to read your vault, so the relay handles each request in the clear as it forwards it. It doesn't store or log them.

You can delete your account on the account page at any time: your account, its devices and sessions go with it. The handle's name is kept so no one else can take it, and the daily counts expire after 90 days.

This site

vaultite.com has no analytics, no tracking and no cookies, and serves its own fonts. The home and download pages ask GitHub for the latest release, so GitHub sees your IP address. The web demo runs in your browser on a made-up vault; what you change in it stays in your browser. The plugins and bundles pages read the directory from GitHub, and a bundle's page (vaultite.com/b/…), or a bundle you import in the demo by its repository, is fetched by your browser from GitHub, so GitHub sees your IP address.

Who else

Cloudflare hosts this site, the update feed and Vaultite Cloud, including its database. Google or GitHub sign you in, if you use Vaultite Cloud. We don't sell or share your data with anyone else.

Changes and questions

If this changes, this page and its date will say so. Questions about your data: support@vaultite.com. To report abuse of a vaultite.app address: abuse@vaultite.com.