What we keep, and what we do not

A drill is a Microsoft Teams call in which we deliberately observe everything that arrives — speech, video, the text chat, a shared screen. That makes it worth being exact about what is measured, what is stored afterwards, and what becomes public.

What happens during a call

Sergeant Sammie receives whatever the call carries and measures it as it arrives: timings, accuracy against a value he generated, whether a stream started and stopped when asked. The measuring happens in the moment.

What is recorded

Every call is recorded. Sergeant Sammie keeps both sides' audio, both sides' video, the text chat, and any screen the agent shares, which is recorded during the Show Me drill. He also starts Microsoft Teams' own recording and transcript of the meeting, under his Microsoft 365 account.

These recordings are kept on Sergeant Sammie's own server and, for the review of each run, in KnowAll AI's Microsoft 365 tenant. They are seen only by KnowAll AI staff reviewing runs.

Raw recordings are deleted after 30 days: the audio, each side's video, the frames, the logs and the timelines. What is kept after that is the report, its PDF, and a single composite video of the call. Teams' own recording and transcript are kept under the meeting organiser's Microsoft 365 retention settings.

A published result on the leaderboard is the score and its measurements. It contains no audio, video or screen capture.

The call itself runs on Microsoft Teams, so Microsoft processes the media in transit under their own terms, exactly as they would for any other Teams call.

What is stored

• The report. Per drill: pass or fail, the measured numbers, and the calibration baseline for that session.
• A composite video of the call, kept with the report after the raw recordings are deleted.
• An email address, so the report can be sent. Used for that, and not added to any list.
• A declared stack, if one is given — the model and media plane the operator says they are running. Published as declared, because it cannot be verified.

There are no accounts. Nothing is stored that would let anyone log in, because there is nothing to log in to.

Payment

Batteries are paid over the Lightning Network. We see an invoice and whether it settled. There is no card number and no billing address, because Lightning does not carry them.

If you sign in, your invoice carries your Nostr public key. The key is written into the invoice's description, so it is visible to anyone who can see that payment. It is a public key and nothing else — not a name, a company or an address — and it is the same key your score is published under. If you do not sign in, no key is recorded.

We also keep a record of which settled payments have been used, so that one payment cannot buy two batteries. It holds the payment hash, the amount and the time, plus your public key if you signed in.

Credits bought on invoice are different: a company buying them gives us the ordinary details a purchase order requires, and those are handled as normal business records.

What becomes public, and what cannot be undone

A result is published only if you sign in with a Nostr key before you reach the payment step. Signed out, the report is emailed to you and nothing is published.

If a result is published, understand what that means: it is a signed event on the Nostr network, copied across relays that we do not own and cannot instruct. A published result cannot be recalled. That permanence is what makes a score worth something to people who have never met you, so sign in only if you are happy for it to be public.

Messages

Messages sent from this site, or to Sergeant Sammie in Teams, are read by a person at KnowAll AI. He is a scripted instrument and answers nothing himself.

Asking us

Questions about any of this, or a request to see or delete what we hold, go to support@knowall.ai. KnowAll AI is the data controller for the records described above.