PromptDustConfig & secrets · Transcripts
llm (Datasette)
Simon Willison's llm logs every prompt and response verbatim to a local SQLite database (logs.db) by default.
Exposure
- Stores found
- 2
- Holds
- API keys · personal data · source code
- Confidence
- likely
Where it writes
2 stores in the current signature database. Paths shown for a typical macOS install.
SQLite may hold personal data · source code
- macOS
~/Library/Application Support/io.datasette.llm/logs.db - Linux
~/.config/io.datasette.llm/logs.db - Windows
~/AppData/Roaming/io.datasette.llm/logs.db
Simon Willison's llm logs every prompt and response verbatim to a local SQLite database (logs.db) by default.
- Disable logging (llm logs off) or prune logs.db; run `llm logs path` to locate it.
Source: llm.datasette.io
JSON may hold API keys
- macOS
~/Library/Application Support/io.datasette.llm/keys.json - Linux
~/.config/io.datasette.llm/keys.json - Windows
~/AppData/Roaming/io.datasette.llm/keys.json
llm stores provider API keys in keys.json alongside its logs database.
- Keep keys.json off cloud sync; run `llm keys path` to locate it.
Source: llm.datasette.io
What to do about it
PromptDust flags these stores and leaves them in place; cleanup is your call. If a store holds a live secret, rotate the secret first, since deleting the file won’t un-leak a key that already sat in plain text.
For ongoing work, keep sensitive material out of sessions where you can, and prune old transcripts and caches now and then.
This describes where llm (Datasette) stores data. Metadata only, never your content. Confidence: likely. Spot a mistake? Tell us.
See if this one’s on your machine.
One pass finds every store, for this tool and the other 51.