Repository navigation
docs: publish signing, privacy and uninstall policies - #14
Merged
Merged
Conversation
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
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.
EnvScope's signing application needs public code-signing, privacy and uninstall information. Add those pages and link them from the download section and documentation index, while explicitly preserving the current unsigned Windows and ad-hoc macOS status.
The signing policy identifies the single maintainer and the steps required before any Foundation signing can start. The privacy notice documents default GitHub update checks, optional diagnostic requests, credential-bearing local backups and removal controls. Correct the existing security notice so it no longer claims that user-entered address ranges cannot be stored.
Validation: reviewed all six changed Markdown files against the current source and documented behavior; checked 134 links, rendered the three new documents with GitHub GFM, and passed the repository's private-artifact, credential-pattern and pinned-source checks. No runtime, workflow or release-file changes.