HeronSignal privacy overview

HeronSignal collects the information needed to provide product experience insights, account access, workspace setup, alerts, and support. This may include account details, workspace configuration, configured domains, product signals, logs, health check results, and integration settings.

We use data to operate HeronSignal, surface issues, generate insights, send alerts, secure accounts, improve reliability, and support users. We do not use customer data to sell advertising.

HeronSignal is designed not to record passwords, payment card details, form field values, private keys, or intentionally submitted secrets. The tracker redacts sensitive URL parameters such as tokens, passwords, emails, sessions, and API keys before storage.

Teams can mark sensitive page areas with data-heronsignal-mask to hide captured element text, or data-heronsignal-ignore to skip click capture inside that area. Custom logs and business event payloads should use non-sensitive values only; HeronSignal also redacts common secret-like keys as a safety net.

HeronSignal may use workspace data to produce AI-assisted summaries, recommendations, and explanations. These insights are intended to help teams decide what deserves attention first. HeronSignal does not write code directly into your repository; it provides context to the coding agent and workflow you choose.

Access is scoped to authenticated users and their workspaces. Tokens and integrations should be kept private. We use reasonable safeguards to protect data, but no system can be guaranteed perfectly secure.

Raw telemetry is retained for a limited analytics window. Durable aggregated analytics and saved AI reports may be retained longer so teams can understand trends without keeping every raw event forever.

For privacy questions, data requests, or account concerns, contact the HeronSignal team through the support channel provided during onboarding.