Privacy

Overview

Klingbar is the management surface for crews: rosters of AI agents, called personas, that watch a business and report in Slack. The personas run on a machine you control — your box — under engine logins you own. klingbar.com holds your account, each crew's configuration, and the record of what the crew did, so it can render that record and relay your decisions back to the box. We don't sell, rent, or trade any of it. Analytics are optional and load only if you accept cookies; see cookies.

This page is short on purpose. Jump to what we collect, what your box reports, Slack, processors, cookies, your rights, or contact.

What we collect

Account information. Your email address, your display name, and the WebAuthn passkey credentials you register for sign-in. Passkeys live as public-key blobs — we never see the private key your authenticator generates.
Early-access requests and contact messages. The email address, optional name, and notes you give us on the early-access form, and the name, email, and message you send through the contact form.
Crew configuration. What you enter on klingbar.com to define a crew: its personas, prompts, tasks and schedules, standing rules, learnings, members and approvers, the names and specs of the secrets it uses (never their values), and every version of each.
Setup answers. What you tell the guided setup about your business — its name, website and what it does, how it makes money, its customers and stage, your goals, and any numbers, limits or voice you add — and about you: your name, role, what you are accountable for, how you want to hear from the crew, your working hours and time zone, and your Slack member id. We keep them as a draft against your account, together with the personas, tools, code repository, channels and engine you pick, even if you never create a crew, and as each crew's business context, which is written into its standing rules. They are kept and deleted on the same terms as the rest of your account; see data retention.
Box identity. The public keys your box publishes when it pairs, its name, and the host name, Python and daemon versions, engine versions, and load it reports. Its private keys never leave the box.
Sealed secrets, briefly. A secret you enter on klingbar.com is encrypted in your browser to your box's public key before it leaves the page. We relay that ciphertext, which we cannot open, and delete it once the box reports that it applied it.
Helper links. If you hand your box's setup to someone technical, we keep the link (only a hash of it), what its page shows, any note you add, their email address if you send it by email, and the network address the box paired from. We clear the address, the note and the network address 30 days after the link expires, and delete the link 30 days after that; the email that carried it is kept like any other email we send.
Operational logs. Standard request logs (timestamp, method, path, status, duration, IP address) for debugging and abuse mitigation. Retained for thirty days.

What your box reports

The work itself happens on your box, not on our servers. Your box sends klingbar.com a record of it so you can read and act on it from the web:

Runs: each run's persona, task, verdict, timing, and the seat it used; what it spent as the engine reported it (tokens, turns, and the engine's own cost estimate); and its transcript — the prompt it was given and the output it produced, each capped in size.
Decisions and conversation: cards and how they were decided, questions and their answers, proposed and approved learnings, weekly digests, and the Slack permalinks of the posts these produced.
Health: the box's own checks — its engines and logins, its Slack connection, its channels, workspaces, and resource readings — and whether it applied or rejected each configuration version.
Focus groups and experiments, when a crew uses them: panelist transcripts and round syntheses, the source text of the creative under test, and experiment snapshots and decisions.

The prompts and data your personas send to an engine go from your box to that engine's provider under your own login and your own agreement with them. They do not pass through klingbar.com.

Slack

When you add Klingbar's Slack app to a workspace, klingbar.com connects to Slack for every crew attached there, and those crews' boxes hold no Slack token. For that workspace we keep:

The bot token Slack gives the app, encrypted at rest with a key only our servers hold. We delete it when Klingbar is removed from the workspace.
Messages and button taps meant for a crew, sealed to that crew's box's public key, so we cannot open what we store. We read each one only to work out which crew it is for, and delete it once the box collects it, or after 24 hours if the box never does.
Routing records: the workspace's name, its channels' names and ids, the ids of the messages, threads and direct messages a crew's messages are routed through, and the Slack member ids of the people involved, so that replies reach the right crew. Never the text of a Slack message. Your crews' replies pass through klingbar.com on their way to Slack, and we keep only those ids.

We also publish each person's Slack Home tab from the crew records described above.

When you link your Slack account to Klingbar — which approvers do so their decisions can be checked — we store your Slack workspace id, your user id and your Slack name against your Klingbar account. The person who adds Klingbar to a workspace is linked as they add it, from Slack's own answer. Everyone else links by a one-time code Klingbar sends in a direct message; to find you, we ask Slack which member of the workspace has your verified email address, or, if Slack finds no match, use a member id you give us. In a workspace without Klingbar, a crew on its own Slack app sends the code through that app. Either way we keep only a hash of the code, until it is used or expires.

How we use it

To operate the service you signed up for: pair boxes, render each crew's configuration and record, relay the decisions and configuration changes you make, carry Slack messages between your workspace and your boxes, and keep an append-only audit trail of every command. We use your email to send transactional messages — sign-in links, email verification, early-access invites, data-export downloads — and the crew notifications you have left on, such as a daily note about work waiting on you or a box that stopped reporting. We do not send marketing email today.

Processors

Some of the service relies on providers we send data to:

Resend delivers our email, so it receives the address and content of each message we send you.
TypeSafe processes short, structured extracts of your crew's activity — a card's title, a run's verdict, a proposed learning — and returns typed judgments: a label, a probability, a ranking. It returns no text and writes nothing back to your workspace, and where it is unavailable every page behaves exactly as it does without it. We send it only the fields a judgment needs, never a whole transcript and never a secret. A box can also ask TypeSafe directly, but only with a key you supply for that crew.
Slack carries messages between your workspace and klingbar.com when you add Klingbar's Slack app, so it receives what your crews post there, each person's Home tab, and, when you link your account, the email address we look you up by.
Google Analytics, only if it is configured for the site and only after you accept cookies — see below.

Klingbar sets three first-party cookies:

klingbar_session — required. Holds your signed-in session on authenticated pages. Without it you can't sign in. HttpOnly, SameSite=Lax. Cleared when you sign out.
klingbar-theme — preference. Records your light, dark, or match-system theme choice. Set when you click the theme toggle in the footer or topbar; lasts one year. Removing it just resets the page to follow your operating system.
klingbar-cookie-consent — preference. Records whether you've accepted or rejected the consent banner. Set when you click Accept or Reject; lasts one year. Reopen the banner from the "Cookie preferences" link in the footer.

Analytics are optional and off until you accept. If Google Analytics 4 is configured for the site, it loads only after you click Accept on the consent banner. It then sets Google's own cookies (such as _ga) and sends page-view data to Google. If you reject the banner, or never answer it, it does not load at all.

Your rights

Delete your account. Visit your account's danger zone. Deleting it closes the account at once and signs you out on every device. We keep its data for 30 days in case you change your mind — write to support@klingbar.com to undo it. After that, ask us and we erase it.
Export your data. Visit your account's danger zone to request an archive of your profile and your focus-group sessions, with their participants and messages. You'll receive an email with a download link when it is ready. Your crews' records — configuration, runs, cards, questions, learnings and digests — are not in the archive; you read them on each crew's pages.
Change your email. Visit your profile to start an email change; we'll send a confirmation link to the new address.
Other requests. Write to support@klingbar.com with anything else — DPA paperwork, GDPR access requests, deletion requests on a colleague's behalf, and so on.

Data retention

Account and crew data are kept while your account is open. When you delete your account, its data stays for 30 days in case you change your mind, and we erase it when you ask after that. Operational logs are pruned at thirty days. Outbound email metadata (delivery receipts) is retained for one year for debugging.

Contact

Questions about this page or how we handle your data? Send a note via the contact form or write directly to support@klingbar.com. A person reads every message.

What we collect,and what we don't.