FAQ

Is WhyDidItClose local-first?

Yes. The beta workflow is designed to process diagnosis data on-device, with exports only when you explicitly share files.

Which closure types can it classify?

WhyDidItClose is designed for practical termination coverage including normal quit, force quit, kill paths, and crash/policy signals when available.

Is diagnosis always 100% accurate?

No. It is a best-effort diagnostic tool. Every result includes confidence so teams can decide when to escalate.

What is included in Pro unlock?

Pro is focused on advanced workflow value, especially exports and faster handoff for support/QA/engineering collaboration.

How do I restore purchases?

Use the in-app restore action while signed into the same App Store account used for purchase. Restore can take a moment while the storefront sync completes.

Restore did not unlock immediately. What should I do?

1. Confirm you are signed into the correct App Store account.
2. Trigger restore again from within the app.
3. Restart the app and retry restore.
4. If still locked, contact support@whydiditclose.com with app version and macOS version.

Is this a subscription?

Current launch strategy is a one-time unlock model.

How do I report a diagnosis issue?

Send support@whydiditclose.com:

• app version/build
• macOS version
• expected vs actual behavior
• exported event evidence when safe to share

Can teams roll this out internally?

Yes. Teams commonly use WhyDidItClose for support triage and QA release validation workflows.