Repository navigation
Add a right-to-erasure policy for TeachLink Mobile #1497
Description
Background
The Governance/ folder does not yet include a Governance/policies/DATA_DELETION.md document. This is a governance gap: contributors and maintainers lack a clear, versioned reference for this area of governance. Adding the document closes the gap and keeps the change self-contained within the Governance folder.
Implementation Plan
- Create
Governance/policies/DATA_DELETION.mdand document how deletion requests are handled. - Specify the timelines.
- Define the verification.
- Add regression tests where applicable
- Document the change
Acceptance Criteria
- Governance requirement is implemented successfully
- Scope is limited to a maximum of two files
- No changes are made outside the Governance folder
- No regression in existing functionality
- Tests pass and code follows project standards
- Change is documented
Activity
rupesh-kumar-sah commentedon Oct 12, 2026
Hi maintainers,
I reviewed "Add a right-to-erasure policy for TeachLink Mobile" and have a structured approach ready for implementation:
Technical Implementation Outline:
Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
DEV-CHIDIOFFICIAL commentedon Oct 15, 2026
@DEV-CHIDIOFFICIAL has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @DEV-CHIDIOFFICIAL to this issue.
ustaxs commentedon Oct 15, 2026
@ustaxs has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @ustaxs to this issue.
pharwasz commentedon Oct 15, 2026
@pharwasz has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @pharwasz to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @ustaxs! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @ustaxs: 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 🌊
docs: add erasure, consent, vendor risk, and retention policies
grantfox-oss commentedon Oct 17, 2026
🎉 This issue has been marked as completed on GrantFox!
@ustaxs's PR #1553 was approved and merged by @RUKAYAT-CODER.
🏆 @ustaxs: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,668 total points). Track your full progress on GrantFox.
👏 Great work, @ustaxs! Keep contributing to rinafcode.
drips-wave commentedon Oct 17, 2026
This issue has been completed by @ustaxs as part of the Stellar Wave Program's 10th Wave 🥳
😎 @ustaxs: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.