Data & Security

ButterKit runs on your Mac. No servers, no accounts, and no data leaves your machine unless you tell it to. This means security is straightforward; but it also means you’re responsible for your own backups. (tip: consider version control like Git)

If I choose to publish to App Store Connect, where is the API key stored on my machine?

You can optionally have ButterKit publish your screenshots and App Store metadata to App Store Connect for you. It connects directly to the App Store Connect API from your Mac; there’s no middleman server, and your data never passes through us. API keys are stored in your macOS Keychain.

Is it safe to use ButterKit with AI agents (MCP)?

ButterKit’s MCP tools are scoped intentionally to what you can already do in the app: manage documents, edit designs, translate text, and upload to App Store Connect, not access arbitrary files or run commands.

That said, AI agents act on your behalf. If you give an agent a vague instruction, it may make changes you didn’t expect, like overwriting text or uploading screenshots to the wrong locale. This isn’t unique to ButterKit; it’s an inherent property of agentic tools.

A few practical tips:

• Use document.snapshot and design.export_preview to review changes before saving or uploading.
• Save your document before running multi-step workflows so you can revert if needed.
• Review any asc.upload_* calls carefully — uploads go directly to App Store Connect.
• Use version control like Git to easily revert if needed
• Always review your information in App Store Connect before submitting to Apple for review