Privacy Policy

Case Study Maker · Jacobus Company, LLC · Last updated July 16, 2026

Privacy Policy

Case Study Maker

Effective Date: February 26, 2026

Last Updated: February 26, 2026

Jacobus Company, LLC, a limited liability company organized under the laws of the United States, doing business as Jacobus Company ("Company," "we," "us," or "our"), provides this Privacy Policy to inform you of our practices regarding the collection, use, and disclosure of information in connection with Case Study Maker ("Software").

---

1. Overview

Case Study Maker is a local-first software plugin. It is designed to operate entirely on your machine within your project workspace. We do not operate servers that collect, process, or store your data.

2. Information We Do Not Collect

We do not collect, transmit, receive, or store:

Personal information (name, email, address, phone number)
Project source code or repository contents
Case study content, reflections, or development notes
Screenshots, media, or generated outputs
Usage analytics, telemetry, or behavioral data
IP addresses, device identifiers, or browser fingerprints
API keys, credentials, or authentication tokens

3. Local Data Processing

All data processing performed by the Software occurs locally on your machine:

Project data (source code, git history, reflections) is read from and written to your local filesystem within the project workspace.
Generated outputs (HTML, CSS, JS case study files) are written to the `OUTPUTS/` directory within your project.
Event logs are stored in `.case-study/events.json` within your project directory.
Media files (screenshots, images) are stored in `.case-study/media/` within your project directory.

No data leaves your machine through the Software itself.

4. Third-Party Services

The Software may interact with third-party services at your explicit direction. These interactions are initiated by you and governed by the respective third party's privacy policy:

|---------|-----------|-------------|-------------|

| Cursor IDE / Anthropic | AI-assisted content generation | Prompts and context sent to AI models | [Cursor Privacy Policy](https://cursor.com/privacy) / [Anthropic Privacy Policy](https://www.anthropic.com/privacy) |

| GitHub | Publishing, deployment, releases | Repository contents you choose to push | [GitHub Privacy Statement](https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement) |

We do not control and are not responsible for the privacy practices of third-party services. We encourage you to review their privacy policies before use.

5. AI Processing

When you use AI features through your IDE (Cursor or Claude Code), your prompts and project context may be sent to AI model providers as determined by your IDE configuration. This data transmission is:

Controlled by your IDE settings, not by the Software
Subject to your IDE provider's privacy policy and data retention practices
Your responsibility to configure according to your privacy requirements

The Software does not independently transmit data to AI providers. All AI interactions occur through the host IDE's established channels.

6. Credentials and API Keys

The Software may require API keys for companion plugin features (e.g., ElevenLabs for Demo Maker). These credentials:

Are stored locally in `.env` files or injected via secrets managers (e.g., 1Password CLI)
Are never collected, transmitted to, or stored by us
Are your responsibility to manage securely
Should never be committed to version control

7. Generated Content

Case study outputs generated by the Software may contain information derived from your project, including:

Project descriptions and architecture decisions
Development reflections and tradeoffs
Git commit history summaries
Screenshots and visual assets

This content is generated locally and remains under your control. You are solely responsible for reviewing generated content before publishing and ensuring it does not contain sensitive or confidential information.

8. Children's Privacy

The Software is not directed at children under the age of 13. We do not knowingly collect personal information from children. Since we do not collect any personal information from any users, this provision is stated for completeness.

9. Data Security

Because the Software operates locally and we do not collect or store your data, the security of your data depends on:

Your local machine's security configuration
Your IDE's security settings and sandbox configuration
Your credential management practices
Your version control practices (e.g., `.gitignore` configuration)

We recommend following the security practices documented in the Software's README and SECURITY_LOG.md.

10. Your Rights

Since we do not collect or store your personal data, traditional data subject rights (access, deletion, portability) are not applicable to our processing. All your data resides on your local machine under your full control.

If you have published content using the Software and wish to remove it, you are responsible for removing it from any platforms where you published it (e.g., GitHub, personal websites).

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted in the Software repository with an updated "Last Updated" date. Your continued use of the Software after changes are posted constitutes acceptance of the updated policy.

12. Governing Law

This Privacy Policy shall be governed by and construed in accordance with the laws of the State of Delaware, United States, without regard to its conflict of laws principles.

13. Contact

For questions about this Privacy Policy:

Jacobus Company, LLC (dba Jacobus Company)

GitHub: [github.com/julieclarkson](https://github.com/julieclarkson)

Questions? Contact contact@julieclarkson.com.