From 9d62ba5d509792de9049ecb3158f62e1a9e654c8 Mon Sep 17 00:00:00 2001 From: Joan Xie Date: Fri, 12 Sep 2025 12:02:52 -0700 Subject: [PATCH] docs: clarify privacy_policies field description for external services Update the privacy_policies field description to be more specific about its purpose - linking to privacy policies of external services that handle user data, as required for extensions connecting to first- or third-party services. --- MANIFEST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MANIFEST.md b/MANIFEST.md index 6144eea..d129c75 100644 --- a/MANIFEST.md +++ b/MANIFEST.md @@ -186,7 +186,7 @@ A full `manifest.json` with most of the optional fields looks like this: - **prompts_generated**: Boolean indicating the server generates additional prompts at runtime (default: false) - **keywords**: Search keywords - **license**: License identifier -- **privacy_policies**: Array of privacy policy URLs describing data handling practices +- **privacy_policies**: Array of URLs to privacy policies for external services that handle user data. Required when the extension connects to external services (first- or third-party) that process user data. Each URL should link to the respective service's privacy policy document - **compatibility**: Compatibility requirements (client app version, platforms, and runtime versions) - **user_config**: User-configurable options for the extension (see User Configuration section)