Privacy Policy
Last updated
Curio is a local-first application. It has no accounts, no servers we operate, and no analytics. Everything you capture is stored on your own computer. The one case in which data leaves your machine is described in Assessment by Anthropic, and it happens only if you choose to supply your own API key.
Who this covers
This policy covers the Curio desktop application and the Curio Capture browser extension. They are one product: the extension captures pages and hands them to the application running on the same computer.
What the extension collects
Only when you actively capture a page — by clicking the extension's button. Nothing is collected in the background, and the extension does not read pages you have not asked it to capture.
| Data | Why |
|---|---|
| A screenshot of the page (PNG) | It is the design reference you are saving. |
| The page address | So you can return to the original later, and so duplicates are recognised. |
| The page title | Used as the capture's default name, which you can change. |
| The viewport width and height | Needed to stitch a full-page capture from several frames. |
The extension does not collect browsing history, form contents, passwords, cookies, or any personal identifiers, and it has no access to pages other than the one being captured.
What the extension stores
Three values, in the browser's local extension storage: the port the local application is listening on, the per-run token used to authenticate to it, and whether it is currently accepting captures. Nothing else persists, and none of it describes you or your browsing.
Removing the extension deletes that storage.
Where captures go
To the Curio application on the same computer, over the loopback interface. The extension is only permitted to contact 127.0.0.1 and localhost — that restriction is declared in its manifest and enforced by the browser, so it is not able to send a capture to any other destination. It also uses the browser's native-messaging channel to ask a small local helper which port the application is on.
Captures are written to your own disk:
- Windows —
%USERPROFILE%\Curio - macOS —
~/Curio
That folder holds the SQLite database, the screenshots and the prompts. It is yours: no copy of it is made anywhere else.
Assessment by Anthropic
This is the only case in which anything leaves your computer, and it is off unless you turn it on.
If you supply an Anthropic API key, Curio asks Anthropic's vision model to describe each capture so it can be searched and organised. For each capture it sends, to api.anthropic.com:
- the screenshot, resized;
- the address the capture came from;
- your own vocabulary terms and rubric, so descriptions use your words.
The request is made from your computer, with your key, against your own Anthropic account. Anthropic's handling of it is governed by Anthropic's privacy policy and the terms of your account with them, not by this policy.
Without a key, nothing is sent. Captures still work and stay browsable; they simply wait, and are described only if you add a key later.
Your API key
Stored in your operating system's credential store — DPAPI on Windows, Keychain on macOS. It is never written to the database, the configuration file, or the logs, and it is never transmitted anywhere except to Anthropic as part of a request you triggered.
No telemetry
Curio makes no network calls except the model calls described above. There is no analytics, no crash reporting, no update check, and no usage measurement of any kind. We do not operate a server that your copy of Curio talks to, so there is nothing for us to collect even in principle.
This is a fixed property of the product rather than a current setting: introducing any phone-home would require a major version change and a recorded decision in the project's public architecture register.
We do not sell or share your data
We do not sell your data, share it with third parties, transfer it for advertising, or use it to build profiles. We never receive it in the first place.
Deleting your data
Delete individual captures inside the application, or delete the data folder above to remove everything at once. Uninstalling Curio removes the application, its browser integration and its run-state file, and deliberately leaves your library in place — deleting a library is your decision, never a side effect of removing software. Remove the folder yourself if that is what you want.
Children
Curio is a tool for design work and is not directed at children. It collects nothing from anyone, of any age, beyond what is described above.
Changes to this policy
Any change is published on this page with a new date above. Because the site is part of the public repository, every past version of this document remains readable in its history.
Contact
Questions about this policy: rescueahero@gmail.com. Security issues should go through private vulnerability reporting rather than a public issue.