Data Handling

Last updated: March 2026

Transit-only architecture

Signal Path is built on a transit-only data model. We do not store your operational data. Information enters a workflow, is processed, delivers an output, and is then discarded. There is no persistent database holding your business data on our infrastructure.

How data flows

Every automated workflow follows the same four-stage pattern:

  1. Input — data arrives via a trigger (webhook, email, form, or API call)
  2. Process — the workflow applies logic, formatting, or AI analysis
  3. Deliver — the output is sent to your designated destination (Slack, email, Notion, etc.)
  4. Discard — no copy is retained on Signal Path infrastructure after delivery

Isolated Private Cloud infrastructure

Each client runs on their own Private Cloud instance. Your workflows run in a dedicated environment that is not shared with any other client. There are no shared databases, no shared queues, and no shared processing nodes. Your data cannot cross into another client's environment.

Security measures

The following controls are in place across all client environments:

  • All data in transit is encrypted (TLS 1.2 or higher)
  • Credentials and API keys are stored in isolated, environment-specific secret stores — never in workflow code
  • No shared databases between clients
  • Access to each Private Cloud instance is restricted to that client's workflows only

Setup timeline

Your Private Cloud environment is provisioned and configured within 72 hours of install confirmation. This includes credential setup, workflow deployment, and a verification run before handover.

Questions

If you have questions about how your data is handled within your specific workflows, raise them during your Workflow Audit or contact us via the details provided at booking.