Repository navigation
Data retention and privacy reference #554
Description
Write docs/data-retention.md: for every category of data the system stores, what is retained, for how long, what deletes it, and what a user-initiated erasure can and cannot reach. Covers messages and envelopes, files (soft then hard delete), device and prekey records, audit logs, presence and resume streams in Redis, and push subscriptions.
Acceptance criteria:
- A table of data category → store → retention window → the job or action that removes it
- Documents the GC jobs that enforce each window and their schedules
- States plainly what erasure cannot reach: audit rows are deliberately append-only and not FK-linked, and on-chain transaction data is permanent
- Distinguishes content (E2E encrypted, unreadable by the server) from metadata (visible), cross-linking
docs/threat-model.md
Activity
aigbagbobila commentedon Aug 28, 2026
@aigbagbobila has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @aigbagbobila to this issue.
LohdGordon commentedon Sep 25, 2026
@LohdGordon has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @LohdGordon to this issue.
KodeSage commentedon Sep 28, 2026
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @KodeSage to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
github-actions commentedon Sep 29, 2026
Closed by #613, merged into
dev.drips-wave commentedon Sep 29, 2026
This issue has been completed by @KodeSage as part of the Stellar Wave Program's 9th Wave 🥳
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.