Skip to content

docs(plugin): privacy section and privacyPolicyUrl for the directory listing - #39

Merged
MyPrototypeWhat merged 1 commit into
mainfrom
claude/plugin-privacy
Oct 22, 2026
Merged

MyPrototypeWhat merged 1 commit into
mainfrom
claude/plugin-privacy

Conversation

@MyPrototypeWhat

Copy link
Copy Markdown
Collaborator

Why

The compliance step of the Anthropic directory submission asks the submitter to confirm that "the plugin's privacy policy accurately describes the data it handles". The plugin had no privacy policy: 4 of the 6 listing links were filled, and privacyPolicyUrl was one of the missing two.

What changes

  • plugins/refkit/README.md gets a ## Privacy section stating that:
    • there is no refkit server, and no accounts, telemetry or analytics;
    • search queries go only to the sources the README lists, each under its own policy;
    • nothing is written to disk and nothing is cached;
    • a key from the environment is sent only to its own source's API.
  • .claude-plugin/plugin.json sets privacyPolicyUrl to that section.
  • plugin-manifest checks the URL and that the README really has the ## Privacy heading.

Verification

  • The plugin-manifest and sync-plugin-version tests pass: 38 tests.
  • claude plugin validate --strict plugins/refkit (Claude Code 2.1.308) passes. Its one warning is a local, untracked .DS_Store, which .gitignore keeps out of the repository.

After merge, Re-validate in the developer portal so the listing picks up the link.

…listing

The directory's compliance step asks the submitter to confirm that the plugin's
privacy policy describes the data it handles. The plugin README now has one
(no server, no telemetry, queries go only to the listed sources, nothing on
disk, keys only to their own source), and plugin.json links it.
@MyPrototypeWhat
MyPrototypeWhat merged commit 5a63b97 into main Oct 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant