Repository navigation
Draft privacy policy for usage analytics disclosure #2624
Description
Summary
Draft a short privacy policy covering NodeSpace's opt-in usage analytics (feature usage + crash/error events via PostHog), to be linked from the onboarding consent screen and Settings.
Blocked by / related
- Set up PostHog account and project for NodeSpace usage analytics #2622 (PostHog account/project setup — data residency choice affects policy wording)
- Opt-in usage analytics: onboarding prompt + PostHog client integration #2623 (onboarding consent + client implementation — policy should be linked from the "Learn more" affordance in the consent copy, and should accurately describe what the shipped implementation actually does)
Why
Once any usage data leaves the device (even anonymous/pseudonymous events), a durable, linkable privacy policy is expected — separate from the short onboarding consent copy, which is UX, not the reference document. This applies regardless of open-source status.
Scope
- Draft policy covering: what's collected (feature usage, crash/error reports), what's explicitly excluded (note content, titles, file paths, embeddings, any user-generated text), where it's sent (PostHog — self-hosted/EU per Set up PostHog account and project for NodeSpace usage analytics #2622's decision), retention, that it's not sold/used for ads or marketing, and how to opt out
- Verify crash/error event payloads can't incidentally leak local file paths or in-memory user content via stack traces — confirm this against the actual implementation in Opt-in usage analytics: onboarding prompt + PostHog client integration #2623, don't assume
- Identify the data controller / contact point for privacy questions
- Avoid unverified compliance claims (e.g. don't assert "GDPR compliant" unless that's actually been checked against the real data flows)
- Human review of factual accuracy before publishing — an AI-drafted first pass is fine, but every factual claim (what's collected, where it goes, retention) must be checked against the shipped implementation, not assumed
- Publish to nodespace-docs (per repo convention — this repo carries no docs beyond root CLAUDE.md/README.md)
- Link from the onboarding consent screen's "Learn more" and from Settings
Out of scope
- Terms & Conditions — not needed yet; revisit if/when a hosted service (cloud sync, paid tier, accounts) is on the roadmap
Activity
malibio commentedon Oct 3, 2026
On hold: deferred until after the first release. The current direction is that the daemon and CLI never send telemetry; any analytics in the desktop app would be opt-in. Website and cloud-side analytics may be tracked later, outside core.
malibio commentedon Oct 11, 2026
Closing as not planned in a backlog triage. On hold since early October, and the stated direction is that the daemon and CLI never send telemetry, which this set was written against. If opt-in analytics in the desktop app comes back, it is refiled in that form.