Skip to content

Add the listing's privacy, terms and support links, and soften the beta note - #9

Merged
j127 merged 3 commits into
mainfrom
claude/sessionpad-mod-865578
Oct 30, 2026
Merged

j127 merged 3 commits into
mainfrom
claude/sessionpad-mod-865578

Conversation

@j127

@j127 j127 commented Oct 30, 2026 •

Copy link
Copy Markdown
Owner

The developer portal now passes the mod, with three warnings: plugin.json has no privacy policy, terms or support link. This adds all three, and softens the READMEs' beta note.

What changes

  • privacyPolicyUrl points to the new PRIVACY.md. It says:
    • the author collects nothing: no server, account, analytics or telemetry;
    • what the mod keeps on the machine, and where;
    • that only the opt-in summary lines leave it, what each request carries, and whose privacy policy covers that request;
    • how to delete what the mod keeps.
  • termsOfServiceUrl points to the MIT LICENSE.
  • supportUrl points to the repository's GitHub issues, which are enabled.
  • The beta note at the top of both READMEs is a plain paragraph now, not a warning callout, and no longer says to use the mod at your own risk, which read as a reason not to install it.
  • Docs: both READMEs link to the policy and the issues page, and the CHANGELOG's 0.4.0 entry lists the links. PRIVACY.md joins the format check.
  • Test: scripts/listing.test.ts checks that each listing link is an https URL into the repository and that a file it names exists here. Moving PRIVACY.md away fails it.

The links to PRIVACY.md and LICENSE point at main, so they resolve once this is merged.

How it was checked

just check passes: formatting, strict validation of the mod and the marketplace, the type check, dollar_check, 27 script tests and 366 mod tests. Validation with the directory profile passes too.

Review

A reviewer subagent with fresh context read 244f0c2 and asked for changes to the privacy policy. Its findings, and what changed in 5695576:

  • Important: the policy said only the summary lines leave the machine. The notes_read tool hands the model the headline and the newest notes (up to 50, or 20,000 characters) when the user asks about the pad, and they go out with the conversation. The policy now names both cases. The same claim in both READMEs and the CHANGELOG is corrected.
  • Important: it said the requests go to the vendor under its consumer privacy policy. That isn't true for sessions on a cloud provider or behind a gateway. It now says they go wherever the session's other requests go, under the same terms, and links the vendor's policy for its own plans and API.
  • Important: the deletion steps were vague. They now come in order: uninstall or close every session (an open one writes again), delete the mod's folder (exports saved elsewhere stay), and delete each store file whose name starts with sessionpad_, leaving other plugins' files alone.
  • Minor: the pruning paragraph now names the unreadable copies, the sizes and unowned files it removes, the emptying where there is no rm, that exports are never pruned, and retentionDays 0. The policy also says what the mod looks at (prompts and four kinds of tool call, and that command text is never kept) and that git and du output stays local. One sentence now covers the config-folder variable for every path, and the summary request is described exactly (after turns that did some work, up to 10 file names, the phrase for a turn the tool started itself).
  • Minor: the links test could pass with a broken link. It now pins the privacy and terms URLs, checks the files with git ls-files --error-unmatch (tracked, exact case), refuses a URL that only starts like the repository's, and runs from any folder.
  • Nits:
    • The policy says the version it applies from, and asks people to keep private details out of public issues.
    • Kept: the root README's beta note says "sessionpad", as that README names the mod throughout, while the plugin README's note is the owner's text word for word.

The script tests went from 25 to 27, and just check passes.

Before merging

  • A reviewer with fresh context reads the diff (above), and its findings are fixed.
  • CI green.
  • The owner's OK to merge into main.

j127 added 2 commits October 29, 2026 17:41
The plugin directory warns about a listing without a privacy policy,
terms or a support link. plugin.json now names all three:

- privacyPolicyUrl: PRIVACY.md, which says the author collects nothing,
  what the mod keeps on the machine and where, that only the opt-in
  summary lines leave it (what each request carries, and whose policy
  covers it), and how to delete what it keeps;
- termsOfServiceUrl: the MIT license;
- supportUrl: the repository's GitHub issues.

Both READMEs and the CHANGELOG link to them, and PRIVACY.md joins the
format check. scripts/listing.test.ts checks that each listing link is an
https URL into the repository and that a file it names is here.
The READMEs opened with a warning callout that said to use the mod at
your own risk, which reads as a reason not to install it. They now say
it is beta software in a plain paragraph, with the same advice to keep
what you can't lose elsewhere and the same pointer to /pad-export.
@j127 j127 changed the title Add the listing's privacy, terms and support links Add the listing's privacy, terms and support links, and soften the beta note Oct 30, 2026
The review found that PRIVACY.md said only the summary lines leave the
machine, but the notes_read tool hands the model the headline and the
newest notes when the user asks about the pad, and those go out with the
conversation. Both cases are now named, along with where those requests
actually go: wherever the session's other requests go, under the same
terms. The READMEs and the CHANGELOG said the same and are corrected.

The policy also now says what the mod looks at, names the store file
(sessionpad_..json, one per copy), gives the steps to delete everything
in order, says what pruning removes and that exports are never pruned,
says when it takes effect, and asks for no private details in public
issues.

scripts/listing.test.ts pins the privacy and terms links exactly, checks
the files with git ls-files (tracked, spelled the same), refuses a URL
that only starts like the repository's, and runs from any folder.
@j127
j127 marked this pull request as ready for review October 30, 2026 00:48
@j127
j127 merged commit 6dfbe3d into main Oct 30, 2026
2 checks 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