LeadPulse

Privacy

LeadPulse is a hosted monitor for automation agencies. This page describes what the product stores so you can decide whether to connect an n8n instance. It is not a substitute for advice from your own counsel.

Account data

When you sign up we store your name, email address, a password hash if you use a password, and a session. Magic-link tokens are short-lived and deleted when they expire. The workspace name, brand name, and optional logo URL are stored so reports can be white-labeled.

Automation data

Connecting an n8n instance stores the base URL and the API key encrypted with AES-256-GCM. The key is decrypted only on the server when we call n8n. We store workflow names, active flags, rule settings, and a recent window of executions: status, start time, and item count. We do not need the lead payloads themselves, and we do not keep them when n8n returns them inside execution data.

The free audit and the automation health check send the API key to our server for that single request. We use it to read workflows and executions, then discard it. It is not written to the database. The health check stores the instance host, a score, and the issues it found, behind an unguessable link. That results page is not indexed.

Heartbeat URLs are unguessable. A call records the time and an optional count. Do not put personal data in the count.

Alerts and reports

Email alerts go out through the address you configure, using Resend when that provider is set. Slack webhooks and Telegram bot tokens are stored so we can post alerts. Weekly reports contain workflow names, counts, and incident text. Share links are unguessable. Anyone with the link can view that report.

Billing

Paid plans are processed by Stripe. We store the Stripe customer id, subscription id, price id, and status. Card numbers stay at Stripe. See Stripe’s privacy policy for how they handle payment data.

How long

Workspace data stays until you delete the account or a resource. Execution rows are replaced on each sync with the latest window from n8n. You can disconnect an instance at any time, which deletes its workflows, cached executions, and related incidents.

Contact

This deployment is operated as a self-serve product. Use the email on your account if you need a copy or deletion of workspace data, and include the workspace name.