Privacy

Local-first privacy for QueryFleet on macOS

QueryFleet is built so database work stays on your Mac unless you intentionally send it to a service you configured.

Effective scope

This page summarizes the shipped QueryFleet 1.0 data-handling posture for the public product site and App Store review context.

Data QueryFleet Handles

The app works with the information you choose to use

QueryFleet handles operational connection and query data because it is a database workspace, but that does not mean Trieflow receives it.

Handled data

  • Connection details and credentials
  • Schema metadata, queries, and query results
  • Saved SQL, app settings, and files you choose

Boundaries

What QueryFleet does and does not transmit

The app keeps local services constrained to your Mac and separates optional integrations from Trieflow's own data collection.

Privacy boundaries

  • QueryFleet processes this data on your Mac or sends it directly to the database, AI provider, or other service you configure.
  • AI features stay optional, and QueryFleet does not automatically widen access just because an MCP client is configured.
  • The governed MCP bridge and Redis Pub/Sub listener expose services only on 127.0.0.1 over IPv4 loopback.
  • QueryFleet does not automatically send crash reports, analytics, database contents, or query contents to Trieflow LLC.

Contact

Privacy questions stay on a public Trieflow channel

Contact Trieflow directly if you need clarification about QueryFleet's privacy posture or a public correction.