Local .jsonl transcripts under ~/.claude/projects/, and SKILL.md files under ~/.claude/skills/
Only trigger edits inside SKILL.md – nothing else on disk
No skill content ever leaves your machine. No account or login. Anonymous usage analytics only – feature clicks and counts, never file contents
Skill file contents never appear in any network request SkillKeeper makes. You can verify this by inspecting payloads in Little Snitch or Activity Monitor: the app only checks in for anonymous usage counts and a one-time licence activation check. With Cloud sessions on, it also asks our server for new remote sessions about once a minute
Everything SkillKeeper reads and writes about your skills stays on your Mac. We don't have an account system or any way to see your files – the only thing that reaches us is anonymous usage counts, never content
Off until you open Cloud sessions in Settings – licence only. Sessions on claude.ai/code, CI or servers then send our server what the app counts on your Mac: skill, tool and model names, token numbers, session id, Claude Code version and OS type. Prompts, code, file contents, tool inputs, email and account ids are dropped before anything is stored. Rows are kept 35 days, and only your Macs can read them. Claude Code also sends tool parameters such as Bash commands – our server drops them on arrival and never stores them
Purchases go through Gumroad's checkout, not ours. Gumroad handles your card details under its own privacy policy – we never see or store payment information, only that a licence was issued
Activating a key sends it, plus a hashed device id (not your real hardware serial), to our activation check – once, so we can enforce the 2-device limit. No further checks after that, and no skill or usage data rides along
If this page changes in a way that matters, it'll show on the Updates page too. Questions – hello@skillkeeper.app, or leave feedback directly