Privacy Policy

Effective November 20, 2026. Version 2026-11-20.

This policy explains how the operator of Puffin Coder handles personal data when you use Puffin Coder. It describes what the software actually does today.

What we collect

DataWhyWhere it lives
Account: email, password hash, sign-in provider, creation and last sign-in time, plan, terms acceptanceCreate and secure your account; apply your planSupabase Authentication
Usage records, one per managed model request: time, your account ID, task ID, plan, provider, model, success or failure, latency, input (uncached and cached) and output token counts, and the cost of the callEnforce allowances and rate limits; show your usage; operate and secure the serviceSupabase database
Support messages you send from the dashboard: your message, topic, account ID and emailAnswer youSupabase database
Browser data on this website: your sign-in session and theme choiceKeep you signed in; remember your themeYour browser's local storage (see Cookies)
Technical request data (IP address, user agent) seen by the hosts and providers in the path of a requestDeliver the service; securityWebsite host, backend host, Supabase, model providers (their own logs)

The current extension gateway does not persist prompt or response content. Existing accounts may also have cloud chat history, generated images, and encrypted provider connections from earlier Puffin Coder clients. Those records are included in applicable export and deletion flows.

Code and prompts sent for inference

Managed access. When you use Puffin Coder-managed models, the extension sends the conversation for that step (your instructions, the parts of your files and command output the agent chose to include, and the agent's own messages) to the Puffin Coder backend over HTTPS. The backend checks your sign-in, forwards the request to a model provider, and returns the response. It is held in memory while the request is processed and is not stored by the backend. The providers process that content under their own terms. Free tiers of some providers may retain inputs and outputs and may use them to improve their models. Do not use managed access for code you cannot share with them; use your own key with a provider whose terms suit you, or do not use the Service.

Your own key. Locally saved keys send requests directly from VS Code to the provider. Website connections use the hosted gateway to contact your selected provider, except custom compatible endpoints, which the extension calls directly.

Who receives data

We do not sell personal data and we do not use advertising or analytics trackers on this site.

Where your API keys are stored

Keys you add for your own providers are stored in VS Code's secret storage on your computer (the operating system's credential store). Website connections store your keys encrypted on the hosted service. Connection screens display only key suffixes. The extension receives the selected model catalog and sends requests through the gateway for these connections. Hosted provider connections use a fixed supported-provider catalog; users cannot configure arbitrary backend URLs. Model discovery sends the key to the provider you select. Keys are excluded from account exports and extension packages.

Website chat and task-driven connectors

Website chat titles, messages, responses and action confirmations are stored with your account until you delete the conversation or your account. Puffin Coder can search the official MCP Registry and suggest a connector for a task. A registry listing identifies its publisher; it is not a security endorsement. You see the connector identity, endpoint or package, access description and reason before approving. Hosted chat connects to remote MCP servers over HTTPS and does not execute downloaded MCP packages. In VS Code, approved local MCP packages are downloaded from the npm registry and run on your computer with your operating system permissions. They can access data available to your user account. Connector tool arguments are sent to the selected MCP service or local process after approval, and relevant results go to your selected AI model. Optional hosted connector tokens are encrypted. Third-party accounts may require their own credentials or authorization.

Connectors and skills

Connector settings, optional bearer tokens, and skill instructions are stored with your account. Bearer tokens are encrypted. Enabled settings are sent to your signed-in extension. MCP tool calls run from VS Code after approval and may disclose the arguments and workspace data you choose to send to that server. Enabled skill instructions are included in requests to the selected model. Removing an integration stops its use in new tasks.

Retention

Your choices: export and deletion

In Settings you can download a JSON export of your account details, usage summaries, saved web chats, connection metadata and support messages, change your email or password, sign out of all devices, and delete your account. Deleting requires typing your email to confirm. It permanently deletes your Supabase account and removes your usage records and support messages from the backend. It cannot be undone, and it does not remove copies held by model providers, which you must request from them. Where the law gives you further rights (access, correction, objection, complaint to a regulator), use the Support form in your dashboard (Help > Support).

Security

Traffic uses HTTPS. Plans and administrator status are stored where users cannot edit them and are checked on the server for every request. No system is perfectly secure; tell us promptly if you suspect a problem.

Children

The Service is not directed to children and we do not knowingly collect their data.

Changes

If this policy changes materially, we will update the date above and ask you to accept the new version in your dashboard.

AI support assistant

The optional support bubble sends your question and up to four recent messages to our hosted support service. Detailed questions are processed by Groq to generate a product-help answer; common questions may use built-in answers. Do not share passwords, API keys, sensitive code or personal information. The assistant cannot access your private account or take actions for you. Support messages are held in browser memory during your visit, and the support backend does not store conversation transcripts. Hosting and model-provider services process request data under their own retention policies.

To prevent abuse, the service retains keyed hashes of network addresses and request counts for up to three UTC days. Raw IP addresses are not stored in the support counter database. These limits apply across a shared network. Existing dashboard support messages follow the retention rules above.

Contact

For privacy questions, use the Support form in your dashboard (Help > Support).