Private by design

✓ functional

No app telemetry today, full stop. SQLly stays quiet unless you explicitly ask it to connect somewhere.

SQLly does not phone home: there is no telemetry in the app today. No usage analytics, no crash beacons, no “anonymous” event stream, no background check-in that happens to carry your table names with it.

What that means in practice

Your SQL stays local. Query text, schema, results, and history are read and written on your machine. Nothing about them is sent anywhere as a side effect of using the app.
Everything is a file you own. Connections, history, snippets, and rules live as plain files in your own SQLly folder - inspectable, backupable, and deletable without the app's permission.
Credentials live in the OS keychain, not in a config file and not in our reach.

The connections SQLly does make

Being private is not the same as being offline, so here is the complete list of things that can talk to the network - every one of them because you asked:

What	When
Your databases	When you connect to one. Obviously - but worth saying, because for most sessions it is the only network traffic SQLly generates.
Licensing	When you sign in, activate, or manage your devices against your account. It carries your account and device, not your work.
IntelliSense feedback	Only when you press `F2` and send a report. You see exactly what it contains before it goes, and it exists so a completion that annoyed you can become a test.
AI features	Only with a provider profile you created. On-device options send nothing at all; a cloud profile is labelled `cloud` everywhere it appears.
The relay	Only for a connection you explicitly routed Via Relay, and the relay cannot read what it carries.

If that ever changes. If opt-in check-ins arrive, the privacy policy changes first, the feature ships off by default, and its purpose is stated plainly. Your data and your habits remain yours.