Legal
Privacy policy
What we collect from your n8n instance, what we deliberately never store, how long each category survives, and how to make it all go away.
1. The short version
PulserNode connects to an n8n instance you own and operate. To do that we hold your account details, your instance URL, and an encrypted copy of your n8n API key. We read workflow structure and execution outcomes so we can version, monitor, and repair them.
We do not want your business data and we designed the system not to keep it. Execution payloads are redacted before anything is written down, and the encrypted diagnostic samples that survive redaction expire after 30 days.
2. Who is responsible for your data
PulserNode is the controller for the account and billing data described below, and a processor for the workflow and execution data we handle on your behalf. You remain the controller of the data inside your own n8n instance; we never become its owner.
For any question about this policy, or to exercise a right described in section 8, email privacy@pulsernode.com.
3. What we collect
Account data
Your email address, name if you provide one, workspace name, and authentication identifiers issued by our identity provider. We use these to sign you in and to attribute actions in the audit trail.
Connection data
The HTTPS base URL of each n8n instance you connect and its API key. The key is envelope-encrypted with contextual authenticated data, decrypted only at the moment of an outbound call to your instance, and never returned to a browser or written to a log.
Workflow data
Workflow structure, node configuration, version snapshots, deployment records, validation findings, and proposed patches. This is what makes version history and rollback possible.
Execution data
Sanitized execution summaries: which workflow ran, when, how long it took, whether it succeeded, and which node failed. Where a diagnosis needs the shape of the data a node received, that sample is redacted, then encrypted, then expired on the schedule in section 6.
Billing data
Subscription status, plan, and billing period. Card details are handled by Whop, our Merchant of Record, and never reach PulserNode's servers.
Operational logs
Request metadata, correlation IDs, error traces, and audit events. Credentials, workflow payloads, and decrypted diagnostics are excluded from logs by design.
4. What we deliberately do not collect
- Ordinary business payloads flowing through your workflows are not retained.
- Credential values stored inside n8n are never read into our model. Workflows reference credentials by identifier, and that is all we keep.
- No advertising identifiers, no cross-site tracking, no data broker enrichment.
- We do not sell personal data, and we do not share it for behavioural advertising.
5. How we use it
- To run the service: connect to your instance, version changes, watch executions.
- To diagnose failures and, where you have enrolled a workflow in Guard, to propose and verify a repair inside the limits published on the Guard page.
- To generate workflow drafts when you ask for them. Redacted workflow context is sent to the model provider named in our subprocessor list; model output is parsed into an allowlisted set of operations before it can touch anything.
- To bill you, to answer support requests, and to secure the platform against abuse.
- To keep an audit trail of who changed what, which is a security control as much as a product feature.
Our legal bases are performance of a contract for the service itself, legitimate interests for security and abuse prevention, and legal obligation for financial records.
6. How long we keep it
| Category | Retention |
|---|---|
| Ordinary business payloads | Not retained at all |
| Encrypted raw diagnostic samples | 30 days, then deleted |
| Sanitized execution summaries and metadata | Your plan's history limit |
| Workflow versions and deployment records | For the life of the workspace |
| Audit events | One year |
| Account and billing records | As required by financial law after closure |
Deleting a workspace removes its connections, drafts, versions, and stored diagnostics. Encrypted backups roll off on their own schedule and are not used to resurrect deleted data.
8. Your rights
Depending on where you live, you may have the right to access, correct, export, delete, restrict, or object to our processing of your personal data, and to withdraw consent where consent is the basis.
- Access and export: most of it is already in your workspace. Ask us and we will send the rest.
- Deletion: delete a connection to revoke our access immediately, or email us to remove the workspace entirely.
- Complaint: you may lodge one with your local supervisory authority.
Email privacy@pulsernode.com and we will respond within 30 days.
9. How we protect it
- n8n API keys are envelope-encrypted at rest with contextual authenticated data, so a ciphertext moved out of its row does not decrypt.
- Every request, row, queue job, lock, and audit record carries a workspace identifier, with PostgreSQL row-level security as a second boundary underneath the application checks.
- Outbound calls to your instance require HTTPS, approved ports, and public addresses for every DNS answer, re-resolved per request, which is what stops a rebinding attack from turning our fetcher into a probe of internal networks.
- Platform database backups are encrypted with Restic.
To report a vulnerability, email security@pulsernode.com and please do not include live keys or customer data in the report. More detail lives on our security page.
10. International transfers and subprocessors
We use a small set of subprocessors to run the service, listed with their purpose and location on the subprocessors page. Where data moves outside your region, it moves under standard contractual clauses or an equivalent mechanism.
We will update that page before adding a subprocessor that handles personal data, so you can object before the change takes effect.
11. Children
PulserNode is a tool for operating production software and is not directed at anyone under 16. We do not knowingly collect data from children. If you believe a child has given us data, email us and we will delete it.
12. Changes to this policy
When this policy changes materially we will update the date at the top of this page and notify workspace owners by email before the change takes effect. Continuing to use PulserNode after that date means the updated policy applies.
Contact
Privacy questions: privacy@pulsernode.com. Security reports: security@pulsernode.com. Anything else: hello@pulsernode.com.