Security

Last updated: August 9, 2026

Qampanion is a fully local macOS application. Everything you create in it — projects, test cases, screenshots, test results, app bundles — is stored only on your Mac. Qampanion has no cloud backend and no servers that receive or store your data. Nothing you create in the app is ever sent to our servers or to third-party services.

Signed and notarized by Apple

Every Qampanion release goes through the standard Apple distribution pipeline:

Developer ID signing — the app is signed with an Apple Developer ID Application certificate issued to our developer account.
Notarized by Apple — both the .app bundle and the .dmg installer are submitted to Apple's notary service and stapled, so Gatekeeper verifies them on first launch.
Hardened Runtime — enabled for the app, the CLI, and the MCP server.
Verified on every release — our release pipeline runs codesign --verify --deep --strict and a Gatekeeper assessment (spctl) on every build, and it pins the expected signing certificate fingerprint. If the app were ever signed with a different certificate, the release would fail automatically.

Your data stays on your Mac

Projects are saved as .qpn files wherever you choose.
Test cases, steps, actions, screenshots, and results are stored locally in your project file and in standard macOS directories (~/Library/Caches/Qampanion and ~/Library/Application Support/Qampanion).
App bundles (.ipa / .apk) are kept in a local cache and never uploaded.
Screenshots and snapshot diffs are compared and saved on your machine.

Qampanion requires no accounts and no logins. There is no cloud database, no remote data lake, and no way for anyone at Qampanion to access your project data, source code, screenshots, or test results.

What does leave your Mac

For full transparency, these are the only network communications the app makes:

Usage analytics — basic Firebase Analytics events, such as "test case created" or "test run started". These events contain only feature-level information and do not include any personal information or any data you enter into the app.
Update checks — an anonymous HTTPS request to qampanion.com for the update feed. No personal or testing data is sent.
Optional helper downloads — public tools used for iOS/Android development (such as axe, Android command-line tools, and OpenJDK) are downloaded from qampanion.com/releases/tools/, only when you choose to install them.
Content you explicitly provide — app bundles are downloaded only from URLs you give us, and network request test steps send requests only to endpoints you define yourself.

How updates work

Qampanion uses Sparkle, the standard update framework for macOS apps:

The app periodically fetches the update feed from https://qampanion.com/releases/appcast.xml over HTTPS.
Every update package is cryptographically signed, and the app verifies this signature before installing — an unsigned or tampered update is rejected.
Every update ships as a notarized DMG signed with our Developer ID certificate, exactly like the initial download.

CLI and MCP server

QampanionCLI is a local command-line tool that reads and writes the same project files as the main app. It performs no network calls on its own and runs only the tools you already have installed (xcrun, adb, etc.).
QampanionMCP is a local MCP server that exposes Qampanion actions to AI agents. By default it uses stdio transport, which means the client launches the binary directly and no network port is opened. Optional HTTP mode binds to 127.0.0.1:8080 by default and can be exposed on your LAN only if you explicitly choose to do so.

Both tools are signed with the same Developer ID certificate and run with Hardened Runtime. In all cases, project and test data stays on the Mac where Qampanion is running.

Certifications

We do not currently hold certifications such as SOC 2 or ISO 27001. Qampanion's security model is architectural rather than procedural: because there is no cloud infrastructure that stores your data, most of what those audits evaluate — servers, databases, access management, data retention — simply does not exist in our product. Your data never leaves a device you control, and the binary you run is signed and notarized by Apple.

If your organization requires a vendor security assessment, we are happy to answer it directly — contact us at support@qampanion.com.

Your responsibilities

Because Qampanion is a local tool that can run scripts and interact with simulators/emulators, you remain responsible for:

Keeping your Mac, user account, and project files secure.
Only adding app bundles, scripts, and network request endpoints that you trust.
Deciding whether to expose the MCP HTTP server beyond localhost.