🪶 Conversation collection

Effective: rolling. This page describes exactly what we record when you chat with the assistant at lil.black-magic-lab.com, what we strip out, and how to opt out.

What this is

The assistant runs on a small CPU-only language model. To make it actually useful for DevOps, observability, and SRE topics, we save the prompts and responses people send so we can fine-tune it on real questions over time. Without that, it stays generic.

What we collect (per chat call)

Field	Purpose	Notes
`id`	so the 👍/👎 feedback can attach to the right message	random UUID
`ts`	when the call happened	UTC seconds
`model`, `tier`	which model + whether you were guest / user / admin
`prompt_redacted`, `response_redacted`	the actual conversation, after redaction	see below
`prompt_tokens`, `completion_tokens`, `latency_ms`	quality + perf signals
`ip_hash`	abuse triage only	HMAC-SHA256 with a daily-rotating salt — not reversible across days
`user_id`	per-user quota + session-level signal	null for guests
`feedback`	your 👍 or 👎	only set if you click

What gets stripped before storage

Before anything is written to disk, both the prompt and the response are passed through a redactor that replaces these patterns with placeholders like [redacted-token]:

JWTs, GitHub / Slack / OpenAI / Anthropic / AWS / GCP API tokens
Long hex / base64 strings that look like keys (≥24 chars)
PEM private-key blocks
Email addresses, phone numbers, IPv4/IPv6 addresses
US-format SSN and credit-card numbers

The redactor is regex-based and best-effort. It is not a substitute for not pasting real secrets in. If you do paste a real secret, treat it as leaked and rotate it. We CI-test that known-secret strings don't survive the redactor (tests/test_redact.py).

What we don't collect

Your raw IP address (only the daily-rotating hash above)
Your browser fingerprint
Cookies beyond the opt-out flag and the session token
Anything from the offline / local engine — that runs entirely in your browser

Retention

90 days hot on the API server (rotated daily, gzipped)
Archived to GCS after that for fine-tuning corpus building
Old archives can be deleted on request — email the contact below with your user_id or ip_hash from a recent response header

How to opt out

The chat footer has a “disable collection” link. Clicking it sets the cookie bos_no_collect=1 on this site. Any chat call that arrives with that cookie (or with the header X-No-Collect: 1) is not logged. You can also clear your browser's cookies for this domain to reset the flag.

How to disable for a single message

Send the request with the X-No-Collect: 1 header from the API directly. The cookie is just a convenience for the in-browser UI.

Why this exists

Real DevOps questions in production environments contain context that no public dataset has — internal tool names, weird Terraform state edge cases, on-call patterns. We want the small assistant to actually be useful for those, not just regurgitate generic answers. The 👍/👎 buttons help us pick which responses to keep as gold examples.

Contact

Questions or deletion requests: akujin@black-magic-lab.com.

← Back to Black Magic Lab