Privacy Policy

Effective date: 2026-03-07

This policy explains how WhyDidItClose handles information.

Summary

  • WhyDidItClose is local-first.
  • Core diagnosis runs on your device.
  • No account is required for the core macOS app or iPhone companion.
  • We do not automatically upload your diagnostic history to our servers.

Information Processed On Device

WhyDidItClose may process the following information locally on your device:

  • app identifiers, such as app name, bundle ID, PID, and app path
  • launch and termination timestamps
  • termination metadata, including quit attribution and OS-observed termination details when available
  • diagnosis output, including likely cause, confidence, explanation, and recommended next action
  • optional user feedback inside the app, such as helpful or unhelpful ratings
  • optional purchase and entitlement status required to unlock paid features

Local Data Sources

To diagnose why an app closed, WhyDidItClose may read local operating-system evidence around the event window, including:

  • app lifecycle notifications from macOS
  • local unified log data
  • local crash reports
  • local spindump or related system evidence when available

Local Storage

WhyDidItClose stores its working data locally in your user Library, including files such as:

  • ~/Library/Application Support/WhyDidItClose/events.json
  • ~/Library/Application Support/WhyDidItClose/feedback.jsonl
  • ~/Library/Application Support/WhyDidItClose/telemetry.json

These files remain on your device unless you delete them.

Sharing and Exports

  • WhyDidItClose does not automatically send diagnostic history to us.
  • Data leaves your device only when you explicitly export or share it.
  • You are responsible for reviewing exported files before sending them to a third party.

Purchases

If you purchase or restore an unlock, Apple processes the transaction. We do not receive your full payment credentials.

WhyDidItClose may locally cache entitlement state so the app can determine whether paid features are available.

Website Analytics

Our website may use privacy-respecting analytics to measure visits and conversion events, such as download clicks. Website analytics are separate from the app’s local diagnosis workflow.

Permissions

WhyDidItClose may request permissions relevant to product behavior, such as notifications. Denying optional permissions may limit related features but does not change this privacy policy.

Children

WhyDidItClose is not directed to children under 13.

Changes

We may update this policy from time to time. The current version is the version published at:

  • https://whydiditclose.com/privacy/

Contact

For privacy questions, contact:

  • support@whydiditclose.com

Signed + notarized macOS build. SHA256 published.