Privacy and Your Data
PRIMA CRM keeps every record on your own machine, in a folder inside your workspace. The server has no code that sends anything over the internet.
Where Your Data Lives
Section titled “Where Your Data Lives”All CRM data sits in the .prima-crm/ folder in your workspace root.
| File | What it holds |
|---|---|
crm.db |
Companies, contacts, interactions, engagements, project links, project relations, segments and the sync tables |
crm.db-wal and crm.db-shm |
Recent writes that SQLite has not yet folded into crm.db |
config.json |
Your contact cadences |
crm-dashboard.html |
The dashboard, when you build it with the default path |
The records include names, email addresses, phone numbers, engagement values and summaries of your conversations. Treat the folder as confidential business data.
What Stays Local and What Reaches Claude
Section titled “What Stays Local and What Reaches Claude”The CRM server and the dashboard script make no network requests. The dashboard file loads nothing from the internet when you open it, and your browser visits a company’s website only when you click its link.
When Claude calls a CRM tool, the tool’s answer becomes part of your Claude Code conversation. Claude Code sends the conversation to Anthropic so that Claude can respond, as it does with any file Claude reads in your workspace. Ask only for the records you need in a conversation, and see your Claude plan’s data terms for how Anthropic handles conversation content.
Keep the Folder Out of Git
Section titled “Keep the Folder Out of Git”AI Business OS does not exclude .prima-crm/ from git for you. Add the line below to the .gitignore file in your workspace root, so that a commit or a push to a shared repository never carries your CRM.
.prima-crm/If you build the dashboard to another folder, make sure git ignores that folder too.
Backing Up the Database
Section titled “Backing Up the Database”SQLite keeps recent writes in crm.db-wal until it folds them into crm.db. A copy of crm.db on its own can therefore miss your latest changes.
- Close Claude Code, so that the CRM server stops and finishes its writes.
- Copy all three database files,
crm.db,crm.db-walandcrm.db-shm, if the last two exist. - Copy
config.jsonas well, so your cadences come back with the records.
To restore, put the files back in .prima-crm/ before you start Claude Code.
Correcting and Removing Records
Section titled “Correcting and Removing Records”You can correct any company, contact or engagement by telling Claude what changed. Version 1.6.1 has fewer ways to remove records.
| Record | How to remove it |
|---|---|
| Company | Merge it into another company. No action deletes a single company |
| Contact | No action removes a contact |
| Interaction | No action edits or removes an interaction |
| Engagement | No action removes an engagement. Move it to lost to close it |
| Project link | Unlink it |
| Project relation | Unrelate it |
| Segment | No action removes a segment |
To remove everything, close Claude Code and then delete the .prima-crm/ folder. The server creates a new, empty database the first time Claude uses the CRM after you start Claude Code again.
The Sync and Your Mailbox
Section titled “The Sync and Your Mailbox”Version 1.6.1 reads only your connector settings in .claude/config/integrations.json. It does not read your email, calendar or meetings, and it stores nothing from them. See Email, Calendar and Meeting Sync.
What the Server Logs
Section titled “What the Server Logs”The server writes a few status lines to its log, such as the start-up message, a schema upgrade or a problem with config.json. These lines name files and versions and contain none of your records.

