Card data stays with Stripe.
Checkout takes place on Stripe’s hosted payment page. Sysana’s server creates the session, but does not receive or store your full card number or CVC.
TRUST SHOULD BE
VERIFIABLE.
Clear boundaries for what Sysana can access, how payments are handled, and how the Mac app should be distributed.
Your files are not the product.
Core system diagnostics are designed to run locally. Ask Sysana should use compact system summaries—not the contents of documents, photos, messages, or files.
One official download path.
Use only the installer linked from sysana.app. Production releases should be Developer ID signed, Apple-notarized, and served over HTTPS before publication.
Permission is contextual.
macOS permissions should be requested only when needed and explained before use. Meaningful system actions should always show their target, impact, and risk first.
WHAT SYSANA SHOULD NEVER REQUIRENo password collection.
No password collection.
No disabled Gatekeeper.
No silent cleanup.
REPORT A SECURITY CONCERN
If something looks wrong, stop and contact us. Include the page or app version, but never send passwords, payment details, or private documents.
SECURITY@SYSANA.APP ↗