Privacy
What Shiplogue stores, reads, and sends.
Local by default
The extension stores IDE activity locally as daily JSON files. Private paths,
.env files, credential stores, and .gitignored paths are filtered before an
event is written.
Provider API keys and Shiplogue connector keys live in the editor's SecretStorage, backed by the OS keychain.
What leaves your machine
- Local model — Ollama stays on your machine unless you point it at a remote host.
- BYOK — the assembled activity context goes to the provider you configured.
- Cloud sync — after you connect a connector key, the finished stand-up
draft, date, title, model label, and estimated minutes saved are sent to
shiplogue.cloud.url(defaulthttps://shiplogue.dev). - API activity sync — only if enabled for the workspace; normalized, redacted metadata only.
What the cloud stores
Postgres stores accounts, workspaces, connector-key hashes, stand-ups, delivery records, integrations, subscriptions, and usage events. Raw prompts, source code, and file contents are not stored by the current extension sync.
Turn it off
Run Shiplogue: Disconnect Cloud, or set shiplogue.cloud.enabled to false,
to keep drafts entirely local. Local generation does not require a Shiplogue
account.