Use at your own risk

Practical caveats. Not a legal disclaimer dump — actual things you should think about before installing.

Vendor terms of service

Kept is a browser extension that reads conversations from chat platforms you're authenticated to. Every chat platform has terms of service that govern what's allowed.

We don't make a legal claim about whether using Kept is or isn't compliant with any specific platform's ToS. That depends on:

• The platform (each ToS is different)
• Your account type (consumer, team, enterprise — different terms apply)
• Your jurisdiction
• How you use the captured data

We've designed Kept to do as little as possible: it reads what your browser already has access to via your existing session, never proxies through a third party, never stores credentials, and never sends anything back to the platform. It's the same pattern as exporting a chat through the platform's own export feature, just continuous.

But "doing as little as possible" doesn't equal "guaranteed compliant." If you're using Kept in a regulated environment, on a corporate account with a strict acceptable-use policy, or in a way that might raise eyebrows, read the relevant ToS yourself and make your own call.

Things that could break

Platform API changes

Kept's extension uses each chat platform's API — the same one their web UI uses. The platforms aren't obligated to keep those APIs stable. When ChatGPT or Claude or any of the others change their endpoints, Kept's capture for that platform breaks until the corresponding extension/platforms/<vendor>.js is updated.

We try to keep up. Updates ship via Tauri's auto-updater. But there's a window between a platform changing things and us shipping a fix. During that window, captures from that platform fail silently or with errors in the extension popup.

If a platform's web UI stops working entirely, Kept can't capture from that platform either.

Model deprecation

Continuing a captured conversation with a model that no longer exists won't work. The original conversation is preserved (it's just markdown), but you can't run the same model against it. You can choose any other model your provider offers — the message history is still valid context.

Chrome / Manifest V3 changes

Chrome's extension platform evolves. Manifest V3 introduced restrictions that some V2 patterns depended on. We're MV3-compliant today, but future Chrome changes could require rework. If the extension breaks because of a Chrome update, it's a Chrome update, not data loss — your existing vault is fine.

File system migrations

If you move your home directory, change your username on disk, or restore from a backup that puts ~/.kept/ in a different location, the index and the graph won't find the vault. The fix is Settings → Vault → Vault directory to point Kept at the new location. The vault re-indexes; nothing's lost.

Things to think about

What's in your archive

Your captured conversations contain whatever you put into them. If you've shared credentials, secrets, internal customer data, anything sensitive in a chat — that data is now also on your filesystem. The same set of "should I have shared this" questions apply to the local copy.

The vault is plain markdown. If it's on a shared machine, anyone with filesystem access can read it. If it's synced to a personal cloud (iCloud, Drive), it's where that cloud takes it. Kept doesn't encrypt the vault at rest. That's a tradeoff for "your files, any tool can read them" — but it means you're responsible for filesystem-level protection (full-disk encryption, drive permissions, etc.).

Code execution

The agent's code execution feature runs LLM-generated Python against your vault. It's sandboxed (no internet, restricted file access) but it's still arbitrary code on your machine. Each run prompts for explicit consent.

If you don't want that surface at all, leave it disabled in Settings → Agent → Code execution.

Filesystem context

Same caveat for Filesystem context. When you point Kept at a directory of files, the agent can read those files when it decides to during a conversation. The reads go to your selected model provider as context. Don't add directories with secrets you wouldn't paste into a chat.

MCP server

The MCP server exposes vault read, write, and search to any MCP-aware client you've registered it with. That client now has access to your archive. Registering kept-vault with a model running on a service you don't trust is a bad idea.

Updates

Auto-updates run via Tauri's signed-update mechanism. Signed by us, verified by Tauri. If our signing key were compromised, an attacker could ship a malicious update. The signing key is offline-stored and rotated periodically — not infallible, but standard practice.

Disable auto-updates in Settings → Updates if you'd rather review releases manually before installing.

License & no warranty

Kept is MIT licensed. The license includes the standard "AS IS" warranty disclaimer:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

In plain English: it's open source, you can use it however you want, but if it breaks something or doesn't do what you expected, that's your problem to solve. We're not on the hook.

Reporting issues

Found a bug, a security issue, or something Kept does that surprised you? File an issue on GitHub. For security reports specifically, see the repo's SECURITY.md (if present) or email the maintainers directly.