Privacy

Privacy Policy

Last updated: 25 July 2026 · Applies to Archessa v0.1.0 and archessa.com

The short version

Archessa has no accounts, no telemetry and no servers. Your conversations are read, organized and stored entirely on your own computer.

This isn't a promise about our intentions. There is no Archessa server for your data to go to, so there is nothing to trust us about. The two places the app does touch the internet are listed below in full.

Who is behind Archessa

Archessa is built and run by an independent solo developer, operating as a sole trader and based in Taiwan. For data-protection purposes that person is the data controller. The app collects no personal data at all; the website holds one thing, and only if you hand it over — your email address, if you join the waitlist. Both are set out below.

Contact: vinvincode@gmail.com

What Archessa stores, and where

When you drop in an export from ChatGPT or Claude, Archessa reads it and builds an index on your own disk. On Windows:

That's it. Nothing is copied off your machine, because there is nowhere for it to be copied to. If you delete that folder, the archive is gone — permanently, and without anyone needing to action a request.

What we collect

From the app: nothing. Specifically, Archessa contains:

From the website: your email address, only if you type it into the waitlist form. Nothing on this site collects an email any other way, and you can read the whole page without giving one.

The AI runs on your computer

The organizing, tagging and summarizing that Archessa does is performed by a language model running locally on your own machine, through Ollama on localhost:11434.

Your conversations are never sent to OpenAI, Anthropic, or to us, for any purpose — including model training. If a local model isn't available, those features simply don't run. Archessa never silently falls back to a cloud service.

Where Archessa does touch the internet

Archessa is local-first, but it is not hermetically sealed, and we would rather tell you than have you discover it in a network log. There are exactly two outbound connections today, and neither one carries any part of your archive:

1. Saving a link, when you paste one into Grain

Grain's Add a link box asks Archessa to fetch a web page for you. When you use it, the app requests the address you pasted, and that website sees your IP address — exactly as it would if you had opened the page in your browser yourself.

This happens only when you paste a link and press Save. It never runs on its own, it never follows links found inside the page, and it sends nothing about you or your archive — just an ordinary request for that one page. Archessa refuses addresses on your own machine or your local network, so it cannot be pointed at your router or at anything else running on your computer.

The browser extension does not make this connection: it reads the page already open in your browser and hands it to Archessa on your own machine.

2. Prototype rendering, when a React prototype is displayed

If your archive contains React prototypes, Archessa renders them live. To do that it loads React, ReactDOM, Babel, Tailwind and Lucide from unpkg.com and cdn.tailwindcss.com. Those CDNs receive your IP address and can see which library files were requested.

Note that this includes thumbnails, not just prototypes you deliberately open — so scrolling a list that contains React prototypes can trigger it. Your prototype's own code is compiled and rendered on your machine; it is never uploaded.

What this means in practice: the first connection happens only when you ask for it, and only to the page you named. The second reveals that a computer at your IP address is running Archessa. Neither reveals anything about what is in your archive. We consider the prototype CDNs a wart on a local-first product and intend to bundle those assets into the app; when that ships, this section will shrink and this page will say so.

The app's typefaces used to be loaded from Google Fonts, and are not any more — they are bundled into the app, so opening Archessa now makes no outbound request at all. This page said otherwise for longer than it should have.

The website

archessa.com is a static page hosted by Vercel.

None of this is in the app. The website is a website; the app is where your conversations live, and the app measures nothing at all. The two are separate, and the section above about the app is the one that governs your data.

The waitlist

Archessa is not publicly downloadable yet. The only way to be told when it opens is the waitlist form, and joining is entirely optional.

Your rights

Data-protection law gives you rights to access, correct, export and delete the personal data a company holds about you. The app holds none of your personal data, so there is nothing to request there. If you joined the waitlist, we hold your email address and you can exercise every one of those rights over it by writing to vinvincode@gmail.com — we will action it by hand, at no cost.

Your archive is yours, on your disk, in an open SQLite database you can read with any SQLite tool. To remove it entirely: uninstall Archessa and delete %APPDATA%\Archessa.

Children

Archessa is not directed at children under 13, and we do not knowingly accept waitlist signups from them. The app itself collects no data from anyone of any age.

Changes to this policy

If any of this changes, we will update this page and the date at the top.

In particular: if we ever add crash reporting or usage analytics to the app, it will be opt-in, off by default, described here before it ships, and it will never include the contents of your conversations. If you would rather not take our word for it, the absence of network activity is something you can verify yourself with any firewall or packet inspector.

Contact

Questions about privacy, or something on this page that doesn't match what you observe? Email vinvincode@gmail.com — corrections are genuinely welcome.