Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion security/privacy.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ Two helpers download on first use, and each is verified before it runs: the Clou

The execution log records every authorization decision the app makes, from the UI, an MCP client, the AI assistant, the import pipeline, or background maintenance. Each record holds a sequence number, a timestamp, the connection ID, the operation kind, which of those five callers asked, allowed or denied, whether it counted as a write, a SHA-256 digest of the statement, and the previous record's hash. The statement text is never stored, and neither is a caller-supplied label such as an MCP client name or an AI session ID, only the channel it came through.

The hash chain is tamper evident, not tamper proof: anyone who can write the file can recompute every hash after the record they changed. It is a JSON file in Application Support, no sync record type covers it, and no code path uploads it.
The hash chain is tamper evident, not tamper proof: anyone who can write the file can recompute every hash after the record they changed. It is a JSON file in Application Support, no sync record type covers it, and no code path uploads it. It has no size cap. A file cut short mid-record, after a crash, is closed after its last whole record, with a copy of it as found kept as `ExecutionAudit.damaged-<date>.json`. A file with no record TablePro can read is renamed to that name and kept, and a new chain starts beside it.

The table load history records how long each table load took, so a slowdown can be looked at after it happened rather than only while it is happening. One line per load, holding a timestamp, the app version and build, the macOS version, what started the load, the database type, whether the connection went through SSH, how long each phase took (schema, driver fetch, result conversion, grid reload, and the main run loop after it), how the load ended, any anomalies it reported, and four size ranges: rows, columns, result size, and open tabs. Sizes are ranges such as `101-1000` and `1-10MB`, never exact counts.

Expand Down
Loading