Repository navigation
Correct MailProcessor data-flow and privacy disclosures - #5
Merged
Merged
Conversation
lukisch
marked this pull request as ready for review
October 3, 2026 22:13
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
1 participant
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.
What changed
Corrects MailProcessor's current documentation to describe the launcher data flows observed in source: local launcher configuration, user-started GitHub release downloads, and separate data flows for launched tools. Snapshot guidance now notes that some trailing folder names can remain.
Adds a factual bilingual support guide and a bilingual privacy-notice draft. The privacy notice remains explicitly a draft because the repository does not identify a verified privacy contact or legal operator; this PR does not claim legal compliance or Store readiness.
Updates documentation contract tests to reject the unsupported zero-egress claims and check the actual network-scope wording.
Validation
python -B -m pytest -q -p no:cacheprovider tests/test_metadata.py tests/test_store_readiness.py— 13 passedgit diff --check— passedStore identity, privacy-contact and legal-operator details, MSIX packaging, and WACK remain separate open gates.