Repository navigation
Draft Reader extension privacy page - #57
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
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.
Scope
Publishes an extension-specific privacy page at
/apps/reader/extension/privacy/and links it from the general privacy page. The text is grounded in the Reader 0.2.0 candidate and Connect/deployment/recovery repositories. Callum Alpass confirmed the public contact (callum@mdbase.dev) and the three data-use commitments. Effective date: 27 September 2026.Store handoff (not a submission)
See
docs/reader-extension-privacy-review.mdfor sources and remaining checks. After deployment, verify the public URL without authentication before entering it in the Web Store. Dashboard categories and Chrome Limited Use compliance still require final review against the uploaded ZIP and service behaviour; no Web Store certification or submission is included here.Checks
pnpm check: passedpnpm build: passedbuild: passedpnpm check:linksbefore spec import: pre-existing/sdk/→/spec/#section-14missing-fragment result; deployment imports spec before link checking.