Data Retention
What stays, and for how long.
Pre-release draft — provider and hosting review pending
Most Dreadcast settings live on your Mac. Kevin Fleming publishes Dreadcast. This page explains what is saved, for how long, and how to clear it.
Retention at a glance
| Data | Where and for how long | How to remove it |
|---|---|---|
| ZIP, location mode, last rounded coordinate and city/state label, and app preferences | Local app preferences until changed or the app container is removed. | Change the setting or remove the app’s preferences/container. |
| Notification delivery IDs and dates | Local history used to suppress duplicates. Entries older than 90 days are pruned when the app processes its history; this is not a guaranteed background deletion deadline. | Remove the app’s preferences/container. |
| Previously supplied Xweather client ID and secret | Login Keychain in production builds until deleted. Keychain entries can survive app uninstall. Development builds may store them in local preferences. | Delete the Dreadcast/Xweather entry for service com.radarbar.RadarBar.providerCredentials in Keychain Access. Remove development preferences separately. |
| Weather, radar, map, and air-quality responses | Temporary in-memory caches and system-managed network caches. Their lifetime depends on macOS and provider cache headers; no single fixed deletion period is promised. | macOS manages these caches; clearing the app container may remove app cache files. |
| Website visits | The site host may keep request and security logs, including IP address and timestamps. Host settings and retention are pending verification. | Email kevin@dreadcast.app to ask about data we control. Deletion depends on what the host can identify and its obligations. |
| Support messages or GitHub issues | Only if you submit them. GitHub handles issues under its policy. Messages to kevin@dreadcast.app include your address and what you send. Our support-mail retention schedule is pending verification and will be published before release. | Remove or edit public GitHub content where available; ask the publisher privately about material it controls. |
| Provider and Apple request records | Controlled by each service under its own policy. Dreadcast has no central copy of these logs and cannot promise their retention period. | Contact the relevant provider or Apple for their available controls. |
Stop future location requests
Switch Dreadcast to ZIP mode to stop device-location requests, or revoke its Location Services permission in macOS System Settings. Disabling weather layers and quitting the app stops their new requests while the app is not running. These choices do not erase request records already held by an outside service.
Clear local data
Uninstalling the app alone may leave its preferences, container, or Keychain entries. Remove the Dreadcast app container and preferences using macOS tools if you want its local settings and history cleared; then check Keychain Access for the service named above. Take care if you use more than one development or signed build: they may have separate containers or credential storage. macOS may retain backups or caches under its own settings.
Questions and deletion requests
Dreadcast has no user account or app-data server from which to retrieve a profile. Email kevin@dreadcast.app for access or deletion requests about information we control. Do not post personal details in a public issue. Verified host and support retention schedules are still pending. We cannot identify every third-party request or remove records held by Apple, GitHub, or weather providers.
Changes
This pre-release draft is dated October 2, 2026. We will update it when app storage, hosting, support, or provider practices change. See the Privacy Policy for the full data-flow description.