docs: fold readme Privacy section into a FAQ entry#1203
Conversation
Remove the standalone == Privacy == section and move the external-services disclosure (jsDelivr, opt-in analytics, Pro license activation) into one FAQ answer. Satisfies WordPress.org Guidelines 6 & 7 without a wall of privacy text competing with the marketing copy.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
kilbot has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: wcpos/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe readme.txt file's privacy documentation was restructured. The standalone "== Privacy ==" section was removed and replaced with a new FAQ entry explaining external services contacted by WCPOS, including translation CDN, opt-in analytics, and Pro license validation data. ChangesReadme documentation update
Estimated code review effort: 1 (Trivial) | ~2 minutes Compact MetadataRelated issues: None found Curious paws tap gently on the keys, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9235ae5bda
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Review-fix triage before changes:
Skipped threads: none. Fresh GraphQL review-thread inventory returned 1 unresolved thread, and this is the thread being fixed. |
There was a problem hiding this comment.
kilbot has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Review-fix triage after push:
Excluded threads:
|
1 participant
Summary
Follow-up to #1202. Removes the standalone
== Privacy ==section fromreadme.txtand folds the required external-services disclosure into a single FAQ entry ("What data does WCPOS send outside my site?").Design decisions (preserve through rebases)
== Privacy ==heading is intentionally removed — WordPress.org mandates the disclosure, not a dedicated section. Folding it into the FAQ is deliberate, not an accidental deletion of a compliance section.Test plan
readme.txtthrough the wordpress.org readme validator/preview; confirm the FAQ shows the new entry and there is no== Privacy ==section.🤖 Generated with Claude Code
Summary by CodeRabbit