Privacy

Local by defaultCopy Anchor Link

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 machineCopy Anchor Link

• 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 (default https://shiplogue.dev).
• API activity sync — only if enabled for the workspace; normalized, redacted metadata only.
• Product telemetry — only if you opt in with shiplogue.telemetry.enabled and have a connector key. The extension sends an anonymous installation ID, extension version, editor/provider labels, and allowlisted events with coarse counts or durations (generated, copied, regenerated, failure, connector, sync). It never sends stand-up text, prompts, file paths, repository names, or raw error messages.

What the cloud storesCopy Anchor Link

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 offCopy Anchor Link

Run Shiplogue: Disconnect Cloud, or set shiplogue.cloud.enabled to false, to keep drafts entirely local. Telemetry also stops when you disconnect, and shiplogue.telemetry.enabled can be turned off at any time. Local generation does not require a Shiplogue account.