Diagnostics and privacy
A record of how Argus runs. Health values and meal text do not belong in it.
What diagnostics contain
Argus uses Sentry for redacted crash and error reports, app hangs, and performance timings. These reports help the developer find failures and slow requests across the app, web, and API.
Reports exclude health values, meal text, email addresses, credentials, and request bodies. Network details contain paths and status codes, with query strings removed. Where a report identifies an account, it uses the account id only. Session replay is off; screenshots and view hierarchies are not attached.
Your choice in the app
In Debug and TestFlight builds, Account → Diagnostics has a “Share diagnostics with the developer” toggle. It starts on in Debug and off in TestFlight. You can change that choice at any time. App Store builds do not share diagnostics.
When sharing is on, the app can also send Argus a redacted sync report and up to 200 events covering recent sync activity and selected performance timings. “Send diagnostics now” sends one immediately. Turning sharing off stops Sentry reporting and new Argus diagnostics uploads. Web and API error reporting runs separately from this app setting.
Who can read reports
The developer reviews Sentry reports and the Argus admin diagnostics service. Uploaded reports are protected by account ownership and an admin allowlist. They are not available to agent model tools.
Diagnostic data is used to maintain Argus, not for advertising or tracking.
Retention
Our retention policy is 90 days for Sentry reports and 30 days for reports uploaded to Argus. Argus removes expired uploads nightly.