Tool inputs
Tool inputs, generated outputs, prompts, token IDs, passwords, hashes, and other tool content are processed in your browser. They are never sent to KitVerse servers. Inputs stay in page memory by default and are not saved when you refresh. Use Clear to remove them from the current workspace.
Explicit saves and sharing
Prompt Diff writes prompt bodies to this browser’s localStorage only when you click Save version. Structured Prompt Builder separately writes field bodies only when you click Save template or explicitly import templates. Their delete and clear-saved controls manage only each tool’s own saved records and do not clear unsaved editor drafts. Browser site-data controls can remove them too. No other tool body is persisted by default.
Prompt Diff creates a #share= URL fragment only after you explicitly generate a link. The fragment contains your prompts, is encoded or compressed rather than encrypted, and has strict size limits. Fragments are normally not sent in HTTP requests, but anyone with the link can read them and they may remain in browser history, screenshots, or messages. Long content must use file export. KitVerse never automatically places tool input in URLs.
Local preferences
KitVerse stores your light or dark theme choice in localStorage. This preference contains no tool content. You can clear it through your browser’s site-data controls.
Website analytics
KitVerse uses Google Analytics 4 to understand site usage. Analytics may collect page visits, approximate geography, device and browser information, and referring pages. Analytics events must never contain tool inputs, token text, JWTs, passwords, keys, file content, or user identifiers.
You can block analytics through your browser’s privacy controls or a script-blocking extension. Where prior consent is legally required, analytics must remain disabled until consent is given.
External links and data sources
Links to provider websites and source documentation open third-party sites with their own privacy practices. Model pricing and provider data are fetched at build or content-review time, not by sending your tool input to those services.
Contact
Questions or privacy concerns can be raised through the contact and corrections page.