Updated October 9, 2026. This policy describes Redfish Console versions that include optional app diagnostics.
Information we collect
Redfish Console has no developer-operated account service, hosted relay, behavioral analytics, advertising, or session replay. Optional app diagnostics go to PostHog by default; you can turn them off in Settings. It connects directly to the BMC you configure.
Data on your iPhone
Your server address, certificate trust, and connection settings are saved locally. Credentials use Keychain/SecureStore, and session tokens remain in process memory. Successful read data, including hardware inventory, sensor readings, and event content, is cached in an age- and size-bounded local SQLite database across app launches. Cached data may be included in device backups. It does not replace live authentication or authorize commands.
Removing a connection or clearing app data removes its local metadata, trust, credentials, and cached reads. It does not change the BMC or erase earlier device backups.
Purchases
Apple and RevenueCat process purchases and entitlement checks using an anonymous app purchase identifier. Redfish Console disables RevenueCat’s automatic device-identifier collection and diagnostics. BMC addresses, credentials, certificates, readings, and events are not sent to RevenueCat.
Optional app diagnostics
App diagnostics are on by default for new installations and upgrades without a saved choice. No consent prompt is shown. You can turn Share App Diagnostics off or on in public or signed-in Settings. A saved opt-out is preserved. The choice applies to this installed app and survives sign-out and relaunch. Clearing app data resets the choice to on. Reporting stays off if the saved settings cannot be restored.
When enabled, PostHog receives sanitized JavaScript errors and standard native crash reports. JavaScript reports include error stacks, unexpected local-cleanup and settings-storage failure categories, app version/build, operating system, device class, and technical symbol identifiers. Our JavaScript filter excludes raw messages, full source paths, server addresses, credentials, server records, and search text.
Native reports bypass that filter and can include crash reasons, stack traces and file paths, app/device/operating-system metadata, and pseudonymous identifiers. Crash reasons can contain data referenced by the app at crash time. We do not supply your server account or purchase identity to PostHog. We do not capture activity histories, screen/touch events, screenshots, console/network breadcrumbs, or session recordings. Custom performance measurements are not enabled. SDK-generated identifiers and request IP addresses mean reports are not anonymous. PostHog also receives error-tracking configuration requests while the SDK is initialized, including while saved settings are loading with reporting off.
Turning sharing off blocks new JavaScript reports and calls PostHog's opt-out API, which applies to native reporting asynchronously. Previously captured reports may arrive afterward. JavaScript reports are queued in memory; the native SDK stores crash reports locally for delivery after relaunch. Its installed crash handler may retain local crash files while sharing is off, and re-enabling can send retained reports. Disabling does not erase reports already held by PostHog. Diagnostic retention and requests to remove provider-held data can be discussed through support. The website itself collects no app diagnostics.
Website and support
This website uses no cookies, analytics, browser scripts, or remote fonts. Cloudflare processes requests to serve the site. If you email support, we receive the information you choose to send.