AI data policy
Every DevHub tool runs locally in your browser. AI assistance is optional, disabled by default, and uses a provider you configure yourself.
Bring your own provider
DevHub ships no AI key and runs no AI server. On the Assistant page you supply an OpenAI-compatible endpoint, a model name, and, when the provider requires one, your own API key. Those values are stored in this browser's local storage only and are sent only to the endpoint you entered. Removing them from the Assistant page or clearing site data deletes them.
What is sent
Workflow planning sends the goal text you type plus the DevHub tool catalog (tool ids, descriptions, and accepted value types). Error explanation sends the selected tool id and the error message you paste, truncated to 400 characters. Tool input, tool output, favorites, recent activity, and saved recipes are never sent.
Explicit consent
Each request requires you to tick a consent checkbox that names the destination model and host. The checkbox resets after every request, so no request leaves the browser without a fresh confirmation.
Local models
Choosing a local endpoint such as Ollama keeps AI requests on your own machine. Hosted providers are labelled as hosted and are never described as local processing.
No hidden reuse
DevHub does not log, store, or reuse prompts or responses. Retention and training behaviour on the provider side are governed by that provider's own terms, which you should review before sending anything sensitive.
Nothing is executed automatically
A proposed workflow is validated against the local engine registry and shown to you as a list of steps. It only runs after you save it as a recipe and run it yourself, entirely in the browser.