Security
Security policy
Effective November 3, 2026
Reporting a vulnerability
Email [email protected] with the subject line “Motion Glass security”. Please report privately rather than in public. Include steps to reproduce, the app version, your macOS version and any proof of concept. We aim to acknowledge reports within three business days and to agree on a disclosure timeline with you. We will credit reporters who want to be named.
Key handling
Motion Glass is a bring-your-own-key app. Anthropic and OpenAI API keys are:
- entered only by you in Settings → Providers;
- stored in the macOS Keychain as app-local, non-synchronizable generic passwords;
- never written to UserDefaults, project files, logs, crash reports or analytics;
- sent only to the provider endpoint or custom base URL you configured;
- removable at any time in Settings or with Keychain Access.
App hardening
- App Sandbox with minimal entitlements (network client, user-selected files, downloads) and Hardened Runtime enabled; no JIT and no unsigned executable memory.
- No third-party runtime SDKs. Native Apple frameworks only.
- The AI returns declarative JSON that is validated against a versioned schema. Downloaded content is never executed (App Store Guideline 2.5.2).
- No telemetry, no accounts and no server-side components, so there is no Motion Glass service to breach.
- Release builds are distributed through the Mac App Store, which notarizes and signs the binary.
Scope
In scope: the Motion Glass macOS app, the Mac App Store release, this website and the public model catalog endpoint. Out of scope: the Anthropic and OpenAI APIs themselves and social engineering against maintainers.
Safe harbor
Good-faith research that respects this policy, avoids privacy violations, does not degrade service and does not access other users' data is welcome. We will not pursue legal action against researchers who follow these rules.