Last updated: September 2, 2026
Chatrove stores everything locally in your browser. We do not collect, transmit, sell or have access to any of your data. There is no server, no account and no telemetry.
Chatrove reads the conversations you open on supported AI platforms (claude.ai today; chatgpt.com and gemini.google.com in future versions) and stores them in your browser's local storage (IndexedDB) so you can organize, search and export them. This data never leaves your device.
To read a conversation completely, Chatrove asks the platform itself for it, from inside the platform's own page and using the session you are already signed in to — the same request the site makes to display the conversation to you. It reads only your own conversations, and only the ones you open.
Nothing. Chatrove has no backend and no account system. It sends no data to us and no data to any third party — there is nowhere for your conversations to go, because we do not operate a server.
To be precise about network activity: the only requests Chatrove makes are to the AI platform you are already using (for example claude.ai), to read your own conversations. It makes no request to any other destination, and no analytics or telemetry of any kind. We cannot see your conversations, your searches, your folders or anything else.
Chatrove requests the minimum permissions required to work: access to supported AI platform sites only (to read conversations as you browse them). It requests no other browser permissions. Your library is stored in standard browser IndexedDB, which requires no special permission.
If you purchase Chatrove Pro, payment is processed by our merchant of record. We never see or store your card details. The payment provider's privacy policy applies to the transaction.
Uninstalling the extension permanently deletes all locally stored data. You can also clear the library at any time from the extension.
If this policy changes, the new version will be published at this address with an updated date. Material changes will be noted in the extension's changelog.