Hello Arcjet team,
As part of our review of the arcjet plugin for the Claude plugin directory, we observed the following:
- The plugin connects to a remote MCP service declared in
.mcp.json.
- We were unable to locate a privacy policy link in the plugin's README or manifest.
For software that connects to a remote service, our directory inclusion standards require a clear, accessible privacy policy covering data collection, usage, and retention.
To complete our review, could you add a privacy policy link to the plugin? Either of the following works:
- A link in the README (e.g., your existing policy at arcjet.com/privacy), and/or
- A
homepage or privacy field in .claude-plugin/plugin.json pointing to the policy.
One note from the security portion of the review: the references to prompt-injection detection in your rules and skill content were recognized as descriptions of Arcjet's own detection features — no concerns there. The plugin installs and loads cleanly. Once the privacy policy link is in place, let us know (or reply here) and we'll re-run the review.
Thanks for building on Claude!
Hello Arcjet team,
As part of our review of the
arcjetplugin for the Claude plugin directory, we observed the following:.mcp.json.For software that connects to a remote service, our directory inclusion standards require a clear, accessible privacy policy covering data collection, usage, and retention.
To complete our review, could you add a privacy policy link to the plugin? Either of the following works:
homepageor privacy field in.claude-plugin/plugin.jsonpointing to the policy.One note from the security portion of the review: the references to prompt-injection detection in your rules and skill content were recognized as descriptions of Arcjet's own detection features — no concerns there. The plugin installs and loads cleanly. Once the privacy policy link is in place, let us know (or reply here) and we'll re-run the review.
Thanks for building on Claude!