Privacy Policy
Last updated: 20 July 2026
WebKaya is a local-first agent platform. Its entire purpose is that your data never leaves your device. You build AI agents grounded in your own files, and they run on your hardware. This policy explains, plainly, what that means.
What we collect
Nothing. WebKaya has no servers, no analytics, no telemetry, no crash reporting, and no accounts. The developer receives no data of any kind from your use of the extension. There is no “opt out” to configure because there is nothing being collected in the first place.
Where your data goes
- Files, pasted text, and web-page data are parsed and analyzed entirely inside your browser tab. Nothing is uploaded.
- AI processing happens on your device by default — either the built-in model (WebLLM, running in your browser via WebGPU) or your own local Ollama server at
localhost:11434. On the local tiers, your prompts, file contents, and results are never sent to any remote AI service. - Optional cloud AI (bring your own key): you can paste your own Anthropic or OpenAI API key in Settings and select a cloud model. Only then do your questions and the data previews needed to answer them go to that provider, directly from your browser, authenticated by your key. The interface makes this state unmistakable: the green “No data leaves this device” bar becomes an amber “Cloud Engine Active” banner, with a one-click switch back to local. Before anything is sent, a local masking pass (on by default) replaces name/ID columns with consistent aliases and masks card numbers, emails, and phone numbers; charts and all verified numbers are still computed on your device from the original data. The developer is never in this path — there is no proxy and no WebKaya server.
- Computation runs in an isolated in-browser sandbox (a WebAssembly realm) and, for very large files, a local columnar/WebGPU engine. All on-device.
- Google Sheets analysis works by asking the Sheets tab you are already viewing to fetch its own CSV export from Google, using your existing Google session. That request goes from your browser to Google — where the data already lives — and the result is parsed locally. WebKaya never sees your Google credentials and uses no Google API key or OAuth grant.
- Web page analysis (“Analyze current page”) reads the visible data table on a page you explicitly click to analyze. It can optionally follow pagination or run in a hidden background tab. The extracted table is processed locally and never uploaded.
- Public dataset imports (optional): if you import a dataset from Hugging Face or Kaggle, your browser downloads it directly from that provider to your device. A Kaggle API key or Hugging Face token you enter is stored only in your browser and sent only to the provider that issued it. Nothing about the download is visible to the developer.
- Semantic search & embeddings, when you have a local embedding model installed in Ollama, are computed on your device and cached in your browser’s local storage.
- Exports (dashboard reports, cleaned datasets, chart data/PNGs) are generated locally and saved as ordinary downloads on your device.
- One-time model download (built-in tier only): the first use of the built-in model downloads its runtime (a WebAssembly module) and model weights from the WebLLM CDN, so the AI can run entirely inside your browser via WebGPU. This transfer contains no user data, is initiated only when you choose the built-in engine, and is cached by your browser afterward. You can avoid it entirely by using your own local Ollama server, and Strict Privacy Mode blocks it outright.
- Live egress meter: the app instruments its own network calls and shows a running “bytes sent off-device” counter. Strict Privacy Mode goes further and blocks every non-local network request outright — including cloud AI and dataset downloads.
What is stored locally
Your preferences (chosen model, theme, display name, workspace), the agents you build or import (their instructions, tool settings, and the schema of the files they use), the local knowledge indexes built from files you attach to an agent, any memory rules you explicitly save, saved dashboards, imported datasets you chose to keep, finance watchlists, alert rules and formula scripts, cached embedding vectors, and any API keys you enter (Kaggle, Hugging Face, Anthropic, OpenAI) are stored in your browser’s local storage / IndexedDB / Origin Private File System, on your device only. Agents you export as .wkagent files carry only their configuration and the shape of the data they need — never your raw files. Keys are sent exclusively to the provider that issued them and never to the developer. You can delete memory rules in Settings → Memory, clear keys by emptying the fields in Settings, and remove sources and dashboards from within the app. Uninstalling the extension removes everything.
Permissions, in plain language
| Permission | Why it’s needed |
|---|---|
tabs | To see the address of your open tabs so “Analyze current page” knows which page you mean. Used only when you click that button. No browsing history is recorded or transmitted. |
scripting / activeTab | To read the visible data table on a page you explicitly ask WebKaya to analyze, and (optionally) to click through pagination. The extracted data is processed locally. |
sidePanel | The extension’s main interface is a browser side panel. |
Host access to localhost / 127.0.0.1 | To communicate with your own local Ollama AI server, and to let you analyze locally-served (dev/intranet) dashboards. Granted in advance for local addresses only. |
Optional site access (http(s)://*) | Requested at runtime, only for actions you initiate: analyzing/collecting a specific site, downloading a dataset from Hugging Face or Kaggle, or calling the cloud AI provider whose key you configured — never granted in advance or in bulk. |
Third parties
By default WebKaya talks only to software on your own machine — your browser, and optionally your local Ollama server. Three optional, user-initiated integrations involve a third party, always directly from your browser with your own credentials and never through any WebKaya server: Google Sheets (the Sheets tab you're viewing fetches its own CSV export using your existing Google session), dataset imports from Hugging Face or Kaggle (downloads to your device; your token/key goes only to that provider), and bring-your-own-key cloud AI (Anthropic or OpenAI, only while you have explicitly selected a cloud model — clearly indicated by the amber “Cloud Engine Active” banner, with local identifier masking on by default). Each provider's own privacy policy governs what it does with requests you send it. The developer never receives, proxies, brokers, or sells any of it — and never sees your keys.
Children
WebKaya is a general-purpose productivity tool and is not directed at children. Because it collects no data, it collects no data from anyone, including children.
Changes
If this policy ever changes, the updated text ships with the extension and appears on this page. The core promise — the developer collects nothing, and data leaves your device only through actions you explicitly take with your own credentials — is the architecture, not a setting.
Contact
Questions? Open an issue on the project repository or reach us through the store listing.