seo 0.9.0 → 0.11.0

package/PRIVACY.md

@@ -38,8 +38,8 @@ Cloudflare D1 with only these things:
 - **Your linked Bing account, if you link one.** Its refresh and access
   tokens, with read-only access to Bing Webmaster Tools, and a name made
   from its sites.
-- **Your API keys, if you save them.** A DataForSEO login and password and an
-  Ahrefs key.
+- **Your API keys, if you save them.** A DataForSEO login and password, an
+  Ahrefs key and a TypeSafe key.
 - **Your Clicky sites, if you save them.** Each site's numeric site ID,
   sitekey and domain. The domain comes from Clicky when you save the site,
   so agents can name the site.
@@ -227,6 +227,16 @@ DataForSEO requests use your login and API password. Ahrefs requests use your AP
 target mode and country filter. Each provider also receives ordinary network
 metadata.
 
+`seo internal-links` sends page text to TypeSafe when a TypeSafe key is set
+(`TYPESAFE_API_KEY` on your machine, or saved on your seoskill.dev account
+and delivered by `seo login`). For each crawled page it sends the URL,
+title, description, headings and opening sentences, and for each link it
+judges, the source sentences that could hold the link and the target's
+title, description and opening. The requests go from your machine with your
+key, and TypeSafe processes them under the
+[TypeSafe privacy policy](https://typesafe.ai/legal/privacy-policy). Without a key, nothing
+is sent to TypeSafe.
+
 The project maintainer does not receive these credentials, inputs, or
 responses. DataForSEO processes them under its
 [privacy policy](https://dataforseo.com/privacy-policy). As of the date of this
@@ -321,9 +331,17 @@ contain the raw error or command arguments. Nothing is sent to GitHub unless
 you open the link, and you can review the form before submitting it.
 
 Aggregate event counts are public at
-[seoskill.dev/stats](https://seoskill.dev/stats). They are described as
-installs, active machines, and audits, never users. One person can have several
-installs, and clearing local state creates a new install.
+[seoskill.dev/stats](https://seoskill.dev/stats). Failure counts are not
+shown there; the maintainer reads them privately to find and fix bugs,
+including a weekly Telegram message with failure totals by version. The
+public counts are described as installs, active machines, and audits, never
+users. One person can have several installs, and clearing local state creates
+a new install.
+
+Once a day the CLI and local MCP server ask the npm registry for the latest
+version number of `seo`, so they can say when an update is out. The request
+sends nothing about you or your sites. Set `NO_UPDATE_NOTIFIER=1` to turn it
+off.
 
 Installing the package through npm or using GitHub is covered by the policies
 of those services.

package/README.md

@@ -150,7 +150,7 @@ ends with the command to run next, so your agent always knows where to go.
 | [`seo data`](https://seoskill.dev/docs/data) | Raw Search Console or Bing rows |
 | [`seo analytics`](https://seoskill.dev/docs/analytics) | Landing pages from Google Analytics or Clicky |
 | [`seo crawl`](https://seoskill.dev/docs/crawl) | Technical issues and AI agent access across a site (CLI only) |
-| [`seo internal-links`](https://seoskill.dev/docs/internal-links) | Pages that could link to a page (CLI only) |
+| [`seo internal-links`](https://seoskill.dev/docs/internal-links) | Internal links to add across a site or to one page (CLI only) |
 
 Every command is also an MCP tool, such as `seo_report`. Add `--json` to any
 command when you're scripting it.