Legal
Subprocessors
Every third party that touches data on our behalf, what each one handles, and how you find out before that list changes.
1. Current subprocessors
These are the third parties that may process data on our behalf when you use PulserNode. Your own n8n instance is not on this list, because you operate it and we are the ones calling it, not the other way round.
| Subprocessor | What it handles | Data involved |
|---|---|---|
| Whop | Merchant of Record. Whop is the legal seller of PulserNode subscriptions and collects and remits sales tax, VAT, and GST on our behalf. | Billing contact, subscription status, tax jurisdiction. Card details go to Whop and never reach our servers. |
| OpenCode Zen | Language model inference for drafting workflows and diagnosing failures | Redacted workflow structure and error signatures only |
| Cloud infrastructure provider | The servers running the application, PostgreSQL, Redis, the identity service, and encrypted backups | All stored data, encrypted at rest |
Authentication, the database, the queue, and backups run on infrastructure we operate rather than on third-party SaaS, so they are covered by the hosting row above instead of appearing as separate vendors.
2. Why Whop is the seller
Whop acts as Merchant of Record for PulserNode subscriptions. In practice that means Whop is the party that sells you the subscription and is responsible for charging the correct tax in your country, across more than 190 of them.
Your card statement may therefore show Whop rather than PulserNode, and your invoice is issued by Whop. The service, the support, and the obligations in our terms of service are still ours.
3. What reaches the model gateway
Prompts are built from redacted workflow structure and error signatures. Credential values and ordinary business payloads are removed before a prompt is assembled, so they cannot reach an inference provider even in principle.
Model output is not trusted on the way back either. It is parsed into an allowlisted set of patch operations, and anything outside that set is rejected before it can touch your instance.
4. How we change this list
We update this page before a new subprocessor starts handling personal data, so you have time to object. Workspace owners can subscribe to notice of changes by emailing privacy@pulsernode.com.
Each subprocessor is bound by terms at least as protective as those in our privacy policy, including on international transfers.