wdid privacy

Last updated: 2026-07-18

wdid (What did I do) is a local-first personal work ledger. Your evidence, summaries, and indexes live on your Mac. Sync pulls activity from tools you already use; processing stays on your machine. We do not host your ledger and we do not receive your Markdown.

Your ledger stays on your machine

Your workspace (collections, evidence Markdown, indexes, summaries) lives in a folder you choose on disk.
App settings live in the operating-system app support directory for dev.noaa.wdid.
Source and AI credentials are stored encrypted with the operating-system keychain / safeStorage APIs. They are never written into the workspace folder.
There is no cloud sync of your ledger, no analytics SDK, and no crash-upload service.

Deleting the app does not delete your workspace. Optionally remove the app support folder if you also want settings and encrypted credentials gone.

How sync works (pull in, not upload out)

wdid authenticates with that provider (using a token or OAuth flow you control).
It downloads your own activity into local evidence files.
It builds Today / Week views, indexes, and (optional) AI drafts on your Mac.

Your ledger Markdown is not uploaded to Noaa, Polar, or any wdid backend. Source credentials are presented only to the providers you chose so those APIs can return your data. They are not forwarded to us.

Local AI (for example Ollama on loopback) also stays on your machine: prompts go to the endpoint you configure on your network, typically 127.0.0.1.

Optional network paths (not your ledger)

These are the only product paths that talk to the internet beyond source pull and local AI. None of them send evidence bodies or ledger Markdown unless you explicitly enable remote AI.

Path	When	What leaves
Remote AI	Only if you switch AI mode to remote and acknowledge the privacy notice in Settings	Evidence / prompt text to the remote base URL you configure (your chosen provider, not a Noaa upload)
App updates	When you check for updates in a packaged build	Version metadata to the configured update feed HTTPS URL
License checks (commercial builds)	When you activate or refresh a license	License key / activation identifiers and Polar-required metadata only; never ledger Markdown or source tokens

Licensing metadata is stored encrypted in the app support directory (license.enc.json), not inside your workspace folder. A lapsed subscription never deletes workspace data.

Diagnostics you export

Help → Export Diagnostics… writes a local archive you can share with support. It redacts credential values, email addresses, token-like strings, and evidence Markdown bodies. You choose where the archive is saved; nothing is uploaded automatically.

Backup and restore

Backup and restore are user-owned folder operations: copy or zip your workspace directory (and restore by opening that folder again). The app does not provide a cloud backup product. Schema migrations may write timestamped backups under .wdid/backups/ inside the workspace before changing files.

Setup guides

Connecting sources: wdid setup docs.

Contact

Questions about this policy: use the support channel published with your download or license purchase.

Your ledger stays on your machine

Your workspace (collections, evidence Markdown, indexes, summaries) lives in a folder you choose on disk.

App settings live in the operating-system app support directory for dev.noaa.wdid.

Source and AI credentials are stored encrypted with the operating-system keychain / safeStorage APIs. They are never written into the workspace folder.

There is no cloud sync of your ledger, no analytics SDK, and no crash-upload service.

Deleting the app does not delete your workspace. Optionally remove the app support folder if you also want settings and encrypted credentials gone.

How sync works (pull in, not upload out)

wdid authenticates with that provider (using a token or OAuth flow you control).

It downloads your own activity into local evidence files.

It builds Today / Week views, indexes, and (optional) AI drafts on your Mac.

Local AI (for example Ollama on loopback) also stays on your machine: prompts go to the endpoint you configure on your network, typically 127.0.0.1.

Optional network paths (not your ledger)

These are the only product paths that talk to the internet beyond source pull and local AI. None of them send evidence bodies or ledger Markdown unless you explicitly enable remote AI.

Path	When	What leaves
Remote AI	Only if you switch AI mode to remote and acknowledge the privacy notice in Settings	Evidence / prompt text to the remote base URL you configure (your chosen provider, not a Noaa upload)
App updates	When you check for updates in a packaged build	Version metadata to the configured update feed HTTPS URL
License checks (commercial builds)	When you activate or refresh a license	License key / activation identifiers and Polar-required metadata only; never ledger Markdown or source tokens

Licensing metadata is stored encrypted in the app support directory (license.enc.json), not inside your workspace folder. A lapsed subscription never deletes workspace data.