Under active development — prototyping only
This platform is still under development. We may recycle environments and purge stored data from time to time, without notice. Do not rely on KBworker for anything more than prototyping — otherwise you will have data loss. Keep your own copies of anything you can't afford to lose.
Scope
Covers KBworker — the web app at www.kbworker.com and the backend at api.kbworker.com. Read this before signing in or uploading data.
Sign-in
Authentication runs through Auth0 with Google as the identity provider. We receive only your name, email, and profile picture URL — never your password.
Your data
Files go to S3 under a per-user path. Workflows, models, credentials, and run traces sit in MongoDB filtered by your user ID. Nothing is visible to another user unless you share it — a workflow or a published page, with people, a team, or publicly.
Where it lives
All data lives in infrastructure operated by the project maintainer. Provider credentials are encrypted at rest with AES-GCM; the master key never touches disk.
What we don't do
No ad tracking, no analytics SDKs, no reselling data, no training models on your prompts or files. Auth0 is the only third party at sign-in.
Third parties
Prompts and completions you send to an LLM provider traverse that vendor under their privacy policy. KBworker only forwards the request — review each vendor's terms.
Cookies
One session cookie from Auth0 keeps you signed in. No analytics or marketing cookies. Clearing it or signing out ends the session.
Deletion
Delete a workflow, run, or file from the UI and the rows + S3 objects go with it. Email contact@kbworker.com to wipe your full account.