Local-first product data
Long-term memory, workspace context, extension preferences, and account connection metadata are stored locally first. Server sync, when introduced, will be explicit and reversible.
Privacy
Jingle is designed around local ownership and explicit connections.
Our privacy model starts with local control: users should know what is stored, what is connected, and what an agent or extension can access.
Sensitive credentials
Account credentials belong in secure storage and stay separate from plain settings files, logs, telemetry, and extension-visible preference objects.
Extension boundaries
Extensions only receive the capabilities and connection state needed for the command they are running. Jingle owns account connection, refresh, revocation, and provider responses.
User control
Users can inspect connected accounts, revoke access, delete local memories, and distinguish local data from synchronized data.