No analytics by default
The launch posture should remain no account, no analytics, and no crash reporting unless records say otherwise.
The privacy view keeps the local-first data posture visible before install.
Data collection, local storage, analytics, crash reporting, and third-party network use are visible before install.
The privacy surface must stay concrete enough for a user to decide whether installing a direct Mac app is safe.
The launch posture should remain no account, no analytics, and no crash reporting unless records say otherwise.
Name local preferences and library state that may live on the user's Mac.
Call out Homebrew, Sparkle/appcast, and browser requests as the relevant network surfaces.
Make every product, procurement, proof, legal, support, status, and release surface visible before launch.
Make Privacy visible from the public site and the native app before a reviewer has to ask.
Back the view with org privacy policy plus app privacy receipts, then project the same record into site and app.
Data collection, local storage, analytics, crash reporting, and third-party network use are visible before install.
Vapor Wares launch views are shared records projected into the public site and native app. The site is not allowed to know more than the app, and the app is not allowed to hide launch trust state.