Privacy & Data Handling

Privacy Policy

Last updated: November 12, 2026

Limitcode Pro and the open-source Limitcode plugin are built by Jawuil at jawuil.dev. This policy separates what happens locally inside the Sublime Text plugin on your machine from what happens when you visit limitcode.jawuil.dev.

Summary (TL;DR)


1. Data Handled by the Sublime Text Plugin

1.1 Source Code, Prompts, and AI Provider Requests

Limitcode runs locally inside Sublime Text's plugin host. When you send a message or approve a tool call, the plugin makes direct HTTPS requests from your machine to the API endpoint of the provider you configured (such as OpenAI, Anthropic, Google Gemini, OpenRouter, DeepSeek, GitHub Copilot, or a local endpoint).

1.2 API Keys and Account Sign-In (OAuth)

1.3 License Activation (Limitcode Pro)

When you activate Limitcode Pro or when the plugin refreshes its periodic offline lease (every few days, with a 30-day offline grace window), the plugin sends an HTTPS request to the Limitcode license verification endpoint containing only:

No source code, project paths, environment variables, or editor contents are ever included in license verification requests.


2. Data Collected on the Website

2.1 Website Analytics and Session Heatmaps

On limitcode.jawuil.dev, we use analytics tools to understand how pages are used and improve the site:

Note: These web analytics scripts run only on limitcode.jawuil.dev and never inside the Sublime Text plugin.

2.2 Purchases, Billing, and Invoicing (Gumroad)


3. Open-Source Transparency

If you want to inspect how Limitcode interacts with Sublime Text views, settings, and provider APIs, you can audit the open-source pair-programming edition at any time on GitHub: github.com/Jawuilp/Limitcode.


4. Your Rights & Contact

You can request information about your purchase/license records, ask to reset device activations, or request deletion of your support correspondence at any time by contacting: