Say that we analyse usage metadata, not where we keep it #278

Merged
cruelacid merged 3 commits from worktree-kpi-labels into main 2026-10-08 12:51:29 +01:00
Owner

Rewords two published documents. There are no code changes.

  • docs/security-model.md, usage metrics: the paragraph now opens "To see how the service is used, we analyse some of the metadata listed above: …". It no longer describes copying metadata to a machine of our own and keeping history there. The sentence "People appear there under a random identifier, not their email or name" is removed. The paragraph now ends: "We don't store any data that is purely for tracking - all data that is in the system exists as part of a feature of our product."
  • docs/privacy.md, "What we hold": adds the purpose "Understanding how the service is used, including which features are most active."

security-model-claims.test.ts, device.test.ts and error-report.test.ts all read these documents, and all pass.

Changelog

The privacy policy now says we analyse service metadata to understand how the service is used.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MY63BZ4UVtMHFcADNr1jFg

Rewords two published documents. There are no code changes. - **`docs/security-model.md`, usage metrics:** the paragraph now opens "To see how the service is used, we analyse some of the metadata listed above: …". It no longer describes copying metadata to a machine of our own and keeping history there. The sentence "People appear there under a random identifier, not their email or name" is removed. The paragraph now ends: "We don't store any data that is purely for tracking - all data that is in the system exists as part of a feature of our product." - **`docs/privacy.md`, "What we hold":** adds the purpose "Understanding how the service is used, including which features are most active." `security-model-claims.test.ts`, `device.test.ts` and `error-report.test.ts` all read these documents, and all pass. ## Changelog The privacy policy now says we analyse service metadata to understand how the service is used. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01MY63BZ4UVtMHFcADNr1jFg
Say that we analyse usage metadata, not where we keep it
Some checks failed
Release note / release-note (pull_request) Successful in 15s
CI / promote (pull_request) Has been cancelled
CI / e2e (pull_request) Has been cancelled
CI / build (pull_request) Has been cancelled
c3ac1c3526
The security model's usage-metrics paragraph described copying metadata to a
machine of our own and keeping its history there, and said people appear
there under a random identifier. It now says what is analysed and why, and
that nothing is built just for tracking: every piece of data exists as part
of a product feature. The privacy policy gains the matching purpose:
understanding how the service is used, including which features are most
active.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MY63BZ4UVtMHFcADNr1jFg
Say we store no data purely for tracking
Some checks failed
Release note / release-note (pull_request) Successful in 13s
CI / promote (pull_request) Has been cancelled
CI / build (pull_request) Has been cancelled
CI / e2e (pull_request) Has been cancelled
25535afc40
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MY63BZ4UVtMHFcADNr1jFg
Call the paragraph just Usage metrics
All checks were successful
Release note / release-note (pull_request) Successful in 15s
CI / build (pull_request) Successful in 5m24s
CI / e2e (pull_request) Successful in 9m55s
CI / promote (pull_request) Has been skipped
Deploy site / deploy (push) Successful in 54s
CI / build (push) Successful in 5m40s
CI / e2e (push) Successful in 9m56s
CI / promote (push) Successful in 32s
52b3007879
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MY63BZ4UVtMHFcADNr1jFg
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!278
No description provided.