Trust & security

By design, Xpanion uses the network for three things, and none of them carries meeting content — no audio, no transcript, no minutes, no board, no ledger.

1. License validation. The app periodically confirms that your subscription is active. The call carries your license key, an identifier derived from your machine, and the IP address our service sees. It carries nothing about your meetings. Details: Privacy Policy, section 4.1.
2. Updates. The app checks for a newer version and downloads it from our distribution endpoint. The update is signed; the check carries no meeting data.
3. Models. On first run — and only then — the app downloads the speech and language models it runs from our distribution endpoint. Details: Privacy Policy, section 4.4.

There is no analytics, no telemetry, no crash reporting and no session recording inside the application.

You do not have to take our word for it. Put an outbound firewall on the app — Little Snitch or LuLu — or watch it with nettop in Terminal, and record a meeting. You should see the license check and, on first run, the model download. If you see anything else, write to hello@xpanion.com with the subject "Network" and tell us what you saw. We will answer, and we will publish what we find on this page.

Account, subscription and license records — who bought which plan, which machine it is bound to, and whether the license is active. That is all. The database runs on Supabase in the United States. No meeting content ever reaches it, because the application has no code path that sends any.

The service providers involved, what each one receives, and where each one processes it are listed on the Sub-processors page.

Xpanion is signed with Valinorsk's Apple Developer ID and notarized by Apple. The only system entitlement the app carries is the microphone. Third-party components and their licenses are listed in LICENSE-3RD-PARTY.txt inside the application bundle.

xpanion.com sets no cookies, runs no analytics and no tracking, and loads nothing from a third party — no fonts, no scripts, no images. Every page is served with a Content Security Policy that forbids outside origins, and with the usual hardening headers. You can inspect them in your browser's developer tools, or with curl -I https://xpanion.com/.

If you believe you have found a security issue in Xpanion or on this site, write to hello@xpanion.com with the subject "Security". We read every report ourselves, we will acknowledge it, and we will not take action against anyone who reports in good faith.