Your work stays
your work.

AgentPerch privacy policy

Updated 5 November 2026 · Describes the current private beta

No AgentPerch account is required. Activity monitoring uses local normalized metadata. Optional crash reporting is a separate, opt-in feature.

Local activity metadata

User-installed observation hooks send normalized updates into the AgentRelay support folder on your Mac: ~/Library/Application Support/AgentRelay. AgentPerch reads that inbox. It does not read provider chat histories or request provider account credentials.

Metadata may include session and turn identifiers, project labels or fingerprints, timestamps, provider and model identity, generic action categories, child-agent identifiers, and supported numeric token counts. Prompts, replies, raw commands, tool arguments and results, and credential values are excluded from retained activity events.

Integration setup preserves unrelated provider settings and creates private backups. Changes are scoped to the selected provider or project. Hooks do not approve requests, start model work or change trust decisions. Installed hooks can receive events while AgentPerch is closed. Removing an integration stops its new updates; hiding a provider only changes the visible sessions and counts.

Retention and removal

The displayed session ledger covers the previous 24 hours. The disk inbox retains up to 10,000 events; this is a count limit, not a guaranteed 24-hour deletion deadline. Preferences, local acknowledgement and review timestamps, and setup backup files are stored separately.

Before deleting shared support data or backups, check whether other configured hooks still use them. Closing or uninstalling the app does not by itself establish that installed hooks and retained data have been removed. Contact support if you need help identifying them.

Notifications

Notifications require explicit enablement and macOS permission. Notification Center receives generic provider/status text and random notice identifiers, without project names, prompts, paths or session identifiers. Notice-to-session routing stays in memory and expires when the app relaunches. Delivery can depend on the provider and operating system.

Optional local counters

Usefulness counters default off. If enabled, they remain on your Mac and contain fixed aggregate panel/link counts and up to 366 distinct received-event days, without agent or session identifiers or conversation content.

The explicit export contains counts and limitations, without the recorded dates or agent/session identifiers. Turning the feature off stops new recording. Clear local counts removes stored counters. AgentPerch does not automatically upload these counters.

Optional crash diagnostics

Crash reporting defaults off on fresh installations. When enabled, AgentPerch sends sanitized native crash information to its Sentry project. Allowed information includes the app version, operating system and symbolication metadata.

The app’s diagnostics facade excludes agent messages, prompts, tool output, project paths, session identifiers, screenshots, recordings, supplemental attachments and user identity. The configured Sentry project also scrubs IP, user and location fields. Network requests still reach Sentry infrastructure, which processes network metadata to receive them.

No activity event, usefulness counter or provider credential is sent to Sentry as analytics. Crash consent does not authorize sharing provider conversations or raw activity files. Learn about Sentry’s privacy practices.

This website and support

This website does not use analytics scripts, advertising trackers, cookies or a signup form. The interactive illustration uses sample data in your browser and does not connect to your coding tools. The website host processes the network information needed to deliver these pages.

If you email support, your email address and the information you choose to share are processed to respond to your request. Review attachments and screenshots for private labels, identifiers and content before sending them. Never send credentials.

Questions

For privacy questions or requests concerning information you have shared with support, email contact@whodevelop.com. This policy will be updated if the app’s data practices change.