Say that we analyse usage metadata, not where we keep it #278
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!278
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-kpi-labels"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.tsanderror-report.test.tsall 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