kellerai companion
Last updated: April 2026
kellerai companion is a local-first, privacy-by-default coding companion. Your data belongs to you. We believe developer tools should earn trust through transparency, not terms of service.
Data collection is organized into four tiers. You control which tiers are active.
Tier 1 — Hook Signals (Always On)
Basic signals from Claude Code hooks: tool call names and duration, test pass/fail counts, commit frequency, lint results, file paths edited, session start/end times. Collected by virtue of installing the companion plugin.
Tier 2 — Git History (Opt-In)
Analysis of your local git commit history for deeper personality insights: commit patterns, branch behavior, merge frequency. No file content is read. Requires explicit opt-in.
Tier 3 — Extended Signals (Per-Signal Opt-In)
Optional detailed signals: time-of-day patterns, tool preference rankings, error recovery patterns. Each signal can be individually enabled or disabled.
Tier NEVER — Prohibited Signals
The following are NEVER collected, not configurable, and architecturally impossible to capture: keystroke timing, raw file content, clipboard contents, idle/away detection, window focus tracking. No code path exists for these signals.
~/.kellerai-companion/events/. Never uploaded, never synced.~/.kellerai-companion/state.db. Derived from events, deterministic.companion share, a curated personality snapshot is uploaded to kellerai.fun (Vercel KV). Contains ONLY: companion identity, five personality axis values, session count, and starred observations.companion purge.None. Ever. Your data is never shared with third parties, never sold, never used for advertising, and never used for model training. The only data that leaves your machine is what you explicitly choose to share via companion share.
companion purge. Delete shared data from Settings.Questions about privacy? Contact privacy@kellerai.io.