Skip to content

docs(privacy): document provider data boundaries#23

Merged
iannuttall merged 1 commit into
mainfrom
docs/privacy-provider-boundaries
Jul 23, 2026
Merged

docs(privacy): document provider data boundaries#23
iannuttall merged 1 commit into
mainfrom
docs/privacy-provider-boundaries

Conversation

@iannuttall

Copy link
Copy Markdown
Owner

Summary

  • document every current outbound data boundary across Google, DataForSEO, Semrush, Bing, IndexNow, CrUX, crawling, telemetry, and agent clients
  • explain the explicit Search Console enrichment boundary and list what is never sent to a research provider
  • align the README, legal pages, setup and provider guides, cookie and telemetry copy, and the packaged SEO skill
  • remove the stale version number from the illustrative README help output
  • state the current reset and provider-keychain deletion behavior accurately

Verification

  • pnpm build
  • pnpm typecheck
  • pnpm test
  • pnpm lint
  • pnpm security:check
  • pnpm pack --dry-run
  • official external policy links return HTTP 200
  • 71 report ids, 71 eval files, 32 report surfaces, and one packaged skill remain in sync

Follow-up

The audit found that seo reset --yes does not remove DataForSEO, Bing, or IndexNow secrets stored in the operating-system keychain. This PR documents the current behavior accurately. The runtime reset fix stays separate so this remains a docs-only change.

Explain what each connected service receives, when selected Search Console query text can be sent for explicit enrichment, and how local and provider-side retention differ. Align the README, legal pages, setup guide, research guide, telemetry copy, and packaged router skill with the same local-first contract.
@iannuttall
iannuttall marked this pull request as ready for review July 23, 2026 08:37
@iannuttall
iannuttall merged commit 3a38d21 into main Jul 23, 2026
1 check passed
@iannuttall
iannuttall deleted the docs/privacy-provider-boundaries branch July 23, 2026 08:43
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