Privacy surface for friends #55
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TheAnachronism/tt-rss-viewer#55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Part of #41
Question
What must a friend be told before installing — especially password/sid storage for re-login (ADR-0001), network access to their tt-rss instance, and any other privacy-relevant behavior?
Resolution
Privacy surface for sideload 1.0 beta (criteria only — write later):
Must-disclose (install/update docs)
Plain-language list for installers / users (do not use the word “friend” in this prose):
sid) are stored on-device (secure storage) so the app can silently re-login when the session expires (ADR-0001).README
Keeps the short privacy blurb + link already locked by Contributor and user docs bar (substance unchanged; avoid “friend” wording there too).
Not must for beta
Why
Sideload testers need informed consent about stored credentials and where network traffic goes — not a legal privacy policy or in-app consent theater. Broader media/third-party detail is optional color, not a readiness gate.