Blane Warrene

Subscribe
Book

Plugin Privacy Policy: Blane Warrene Plugins

Effective date: May 13, 2026
Last updated: May 13, 2026
Operator: Blane Warrene (sole proprietor)
Contact: Here

This plugin privacy policy covers the Claude Code plugins distributed under the marketplace at github.com/enalbenerraw/blanewarrene, including, but not limited to:

  • product-in-acquisitions-os
  • job-interview-meeting-preparation
  • comparative-landscape-brief

It applies to those plugins and to any future plugins published in the same marketplace.

Plain-English summary

These plugins run entirely inside your Claude Code or Claude Cowork session. They do not have a backend, do not call any servers I operate, do not collect analytics, and do not store your data anywhere I can see. What you type stays in your session with Anthropic. What the plugins produce stays on your device unless you choose to share it. Web searches and plugin triggers go through Anthropic’s built-in tools, not through any of my services.

If you stop using a plugin, there is nothing for me to delete because I never had it.

What the plugins do

Each plugin packages a structured workflow as a Claude skill. When you invoke one in your Claude Code or Cowork session, the plugin instructs Claude on how to:

  • Ask you for inputs (company names, audience, attached documents, etc.)
  • Read files you provide (such as a LinkedIn profile PDF in the meeting-prep plugin)
  • Perform web searches via Claude’s built-in web search tool
  • Produce a structured output document, typically markdown saved to your local disk

The plugin is a set of text instructions and reference templates. It is not an application I host or operate.

What data do the plugins process

During use, the following may be processed inside your Claude session:

  • Your prompts and answers to the plugin’s clarifying questions.
  • Files you attach (for example, a LinkedIn profile PDF, a company brief, or a roadmap document).
  • Public web content retrieved by Claude’s web search tool when the plugin asks it to research a company or person.
  • Output documents the plugin produces, which are saved to a location you specify on your own device.

This processing happens between you and Anthropic’s Claude. The plugin itself does not exfiltrate, log, or transmit any of this content to me or to any third party I control.

What data the plugins do NOT collect

I want to be explicit about what the plugins do not do, because the absence of a backend is part of the design:

  • The plugins do not phone home (to me). There is no telemetry, no usage tracking, no analytics, no crash reporting.
  • The plugins do not maintain user accounts, sessions, or any identifiers on my infrastructure.
  • The plugins do not transmit your inputs, files, or outputs to any server I operate.
  • The plugins do not advertise, share data with advertisers, or participate in any ad network (for me).
  • The plugins do not use cookies, since they have no website presence.

Third parties

Using the plugins necessarily involves these third parties, because the plugins run inside their products:

  • Anthropic. Claude Code and Claude Cowork are products of Anthropic, PBC. Your prompts, attachments, web search invocations, and Claude’s responses are processed in accordance with Anthropic’s privacy policy. I have no separate agreement with Anthropic that gives me access to your session.
  • Web search providers. When the plugins ask Claude to perform a web search, the request passes through the search provider Anthropic uses for Claude’s web search tool. That request and response are governed by Anthropic and the upstream provider, not by me.
  • GitHub. The plugin source code is publicly hosted on GitHub at github.com/enalbenerraw/blanewarrene. Installing or browsing the plugin involves GitHub, governed by GitHub’s privacy policy.

If any future plugin in this marketplace introduces a new third-party dependency that affects user data, this policy will be updated, and the change will be called out in the effective date section above.

Files saved to your device

Some plugins save output documents to a location on your local disk (typically ~/Documents/ on macOS, or whatever path you specify). Those files are yours. They live on your device, under your control, and I have no access to them. Deleting them is a matter of deleting the files locally.

The plugins do not write files outside the directories you explicitly authorize.

Children’s privacy

These plugins are professional tools intended for adult users (product managers, executives, advisors, analysts). They are not directed at children under 16. I do not knowingly collect any data from children. If you believe a child has used the plugins in a way that raises a concern, contact me at the address above.

International users

I am based in the United States. If you use the plugins outside the United States, you understand that the third parties involved (Anthropic, GitHub, search providers) may process data in jurisdictions other than your own. Their respective privacy policies cover their cross-border practices. I do not process or transfer your data separately.

The plugins themselves do not implement any region-specific data handling, as they do not handle your data at all, as far as I can tell.

Your rights

Because the plugins do not collect or store your data on my infrastructure, the standard “right to access,” “right to deletion,” and “right to portability” provisions of GDPR, CCPA, and similar laws do not apply to any of your data. If you want to:

  • Stop using a plugin, uninstall it from Claude Code or Cowork.
  • Remove the plugin’s outputs and delete them from your device.
  • Exercise rights regarding data Anthropic or GitHub holds about your usage, contact them directly using the policies linked above.
  • Ask a question about this policy, contact me.

Security

Because the plugins do not store data on my systems, there is no central data store to breach. The integrity of the plugin code itself is protected by:

  • Public version control on GitHub, with cryptographically signed commits.
  • Tagged releases that produce reproducible packaged artifacts (.plugin files).
  • A CI pipeline that validates manifests, checks frontmatter, and enforces style rules on every release tag.

If you ever encounter a security concern with the plugin code, please report it via GitHub.

Changes to this policy

I may update this policy as the plugins evolve or as new plugins are added. Material changes will be reflected by:

  • Bumping the “Effective date” and “Last updated” lines at the top.
  • A short change-log paragraph at the bottom of this page describing what changed and why.

For changes that meaningfully affect how the plugins handle your inputs, I will also note them in the next Substack post and in the GitHub repository’s CHANGELOG.

Contact

Change log

  • May 13, 2026: Initial publication covering product-in-acquisitions-os, job-interview-meeting-preparation, and comparative-landscape-brief.