Repository navigation
docs(governance): add compatibility, data residency, erasure and consent policies - #1788
Merged
Merged
Conversation
|
@Mordy7 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Governance/policies/COMPATIBILITY.md- supported toolchain/browsers/frameworks, window length per category, and drop criteria.Governance/policies/DATA_RESIDENCY.md- approved storage locations, transfer restrictions, and the exception process.Governance/policies/DATA_DELETION.md- how erasure requests are handled, timelines, and identity verification.Governance/policies/CONSENT_MANAGEMENT.md- what requires consent, how consent is recorded, and withdrawal.Each issue is limited to its single new document inside
Governance/(no application code touched), written in the style and section layout of the existing governance policies. No companion test files were added: the issues ask for tests only "where applicable", and several comparable policy documents in this folder (for exampleCOMMUNICATION_NORMS.mdandDCO.md) have none. Cross-references point only at documents that already exist in the repository.These are policy statements for maintainers to adopt; where they describe operational records (for example the data-location register or the erasure request log) they define the practice but do not create the records. They are not legal advice.
Nothing was installed, built or run; please verify in CI/review.
Closes #1755
Closes #1756
Closes #1757
Closes #1758