grainulatorPrivacy & data flow
Your work.
Your call.
Where your research goes, what stays on your machine,
and what you take with you.
01 / Model requests
Your research goes to the provider you choose.
The public playground lets you configure, inspect, and export sessions. It does not call models or accept API keys. To run research, open the playground through your local Grainulator server. When you start research locally, it sends your question, context, instructions, and previous completed passes to the provider you select: OpenAI, OpenRouter, or your configured compatible endpoint. Enabling web search allows the selected model to use OpenAI's search tool. Provider data policies and charges apply.
Choosing OpenRouter in the local playground loads its public model catalog. This request does not include your research question or API key.
02 / Credentials
Your key stays out of your exports.
A key entered in the local playground stays in page memory and is sent to the local server with model requests. The server forwards it to the selected provider. The playground does not save that field in browser storage, session exports, or briefs. Switching providers uses a separate key field for each provider. Opening an imported session clears the entered keys.
For the fixed OpenAI and OpenRouter connections, the local server can use OPENAI_API_KEY or OPENROUTER_API_KEY from its environment. Custom endpoints never receive those environment keys automatically. The CLI also accepts an explicitly named key environment variable.
03 / Your work
You decide what to keep and share.
Playground work stays in page memory until you export it. A session export contains the question, context, instructions, model settings, completed responses, and returned source links. It can contain sensitive research material you supplied or that the model returned; inspect it before sharing. Refreshing the page clears work that has not been exported.
The research CLI writes session.json and SESSION.md, plus claims.json and compilation.json when a claims ledger exists, to the local directory you select. Existing evidence tools store their ledgers and artifacts locally. Optional external connectors send their requests to the services you configure.
04 / This website
No analytics or tracking cookies.
The homepage and new playground do not add analytics, cookies, browser-storage tracking, or remote error reporting. The homepage's example is a recorded local compiler trace using synthetic release evidence. It makes no model requests.
Static website delivery is separate from model execution. The local server listens on your machine and checks browser origins before accepting model requests.
Ready to put your model to work?
Open the playground