Understand where Choro stores data and what providers receive
Understand the difference between local workspace storage, project files, and provider processing.
Last updated 16 September 2026
Understand the difference between local workspace storage, project files, and provider processing.
Before you start
Treat project content, conversation context, and exported archives as potentially sensitive. The exact data sent to a coding provider depends on the task, selected tools, and that provider’s configuration.
Use Data & backups for the supported workspace archive. Keep repository backups and provider data-handling choices separate from this local workspace export.
Step by step
Keep your repository backup separate from Choro’s workspace backup. Adding a project points Choro at a local folder; a workspace export is not a full copy of every repository on disk.
Use Settings → Data & backups to export the supported workspace archive. Retain the resulting file securely and review the import guide before restoring it.
Expect Choro preferences and workspace records in its application data directory. The standard Mac location is under ~/Library/Application Support/com.ritmus.choro; isolated demo or development builds can use a different data root.
Before sending a request, review its attachments, references, and scope. Coding providers can receive prompts and the file or tool context used to carry out that request.
For Voice, distinguish audio from text. Choro’s voice settings describe audio as processed on the Mac and not retained; text used in Project Talk or an agent request can still be processed by the selected coding provider.
Review local transcript retention in Voice settings and check the provider’s own policies for its processing and retention. Local audio processing does not mean every downstream text operation stays on the Mac.
When sharing diagnostics, include the smallest useful evidence. Keep secrets, unrelated private files, and complete workspace archives out of public reports unless you deliberately intend to share them.
What to expect
You can make informed choices about backups, request context, and what to share with a provider or support.
Troubleshooting and useful details
Use the app’s supported export/import flow instead of editing its state database directly. Import replaces supported workspace state and may require a restart; it is not a routine way to repair an unrelated provider error. This guide describes product behavior, not a substitute for the selected provider’s current data policy.