How do I receive messages?

Two options: poll our REST API (GET /api/v1/messages/poll) on your schedule, or configure webhook delivery and we POST messages to your endpoint with automatic retries and circuit breaker.

What integrations are available?

Four: n8n trigger and send nodes, MCP server for any compatible AI agent (Claude, Cursor), Agent Zero plugin for bi-directional AI chat, and a REST API with 4 endpoints for everything else.

Do you store my messages?

No. Messages are relayed, not stored. In poll mode, messages sit in a Redis queue until you poll them. In webhook mode, payloads are temporarily held in S3 during delivery. Nothing persists after successful delivery.

How do I authenticate?

Bearer token via API key. The dashboard also supports webhook bearer tokens, custom header auth, and HMAC signing. Read and write credentials are isolated — a compromised poll key cannot send messages, and vice versa.

How quickly can I get started?

Most users connect their first messenger in under five minutes. Add PrivacyFlow as a contact, send /signin, get your API key, and start polling or configure your webhook.

3 E2E messengers · 1 API

Encrypted messages, delivered to your automation.

Relay Signal, SimpleX, and Session messages to n8n, AI agents, or any webhook. No message content stored after delivery.

Signal, SimpleX, and Session — one API
n8n nodes, MCP server, Agent Zero plugin
Poll our API or receive via webhook

Connect a messenger See how it works

Poll incoming messages

PrivacyFlow

Signal

Session

SimpleX

n8n

AI agents

Webhooks

GET/api/v1/messages/poll?limit=10

"messages": [
  {
    "messenger": "signal",
    "content": "Hello!",
    "isGroupMessage": false
  }
]

POST/api/v1/messages/send

"messages": [{
"messenger": 'signal',
"message": 'Reply received!'
}]

Messages are relayed, not stored. Nothing persists after delivery.

3 encrypted messengersn8n · MCP · Agent ZeroPoll or webhook deliveryCrypto payments

Trusted signals: relay uptime 99.99%, messenger parity verified monthly.

Three steps

From encrypted chat to your automation stack.

Connect a messenger, choose your delivery method, and start automating. No burner phones, no device pairing, no data retention.

🔗01
Connect a messenger
Add PrivacyFlow as a contact on Signal, SimpleX, or Session. Send a DM command to get your API key. No email or signup forms.
More detail
🛰️02
Choose delivery
Poll our REST API for incoming messages, receive them via webhook, or connect n8n, MCP, or Agent Zero directly.
More detail
⚡03
Automate
Messages flow into your workflows. Send replies back through the same API. Batch up to 50 messages per call.
More detail

View API reference

The problem

Encrypted messengers weren't built for automation.

Signal, SimpleX, and Session are excellent for private communication — but they have no webhooks, no API, no way to trigger your workflows. You shouldn't have to choose between privacy and automation.

Without PrivacyFlow

Burner phones and mirrored devices just to receive messages.
Manual copy-paste between chat and your tools.
Brittle self-hosted bridges that break on every update.

With PrivacyFlow

One relay for Signal, SimpleX, and Session — no devices to maintain.
Messages flow directly into n8n, AI agents, or your webhook.
Send replies back through the same API. Bi-directional, no lock-in.

What you get

Built for privacy-first automation.

Four things that make PrivacyFlow different from a generic webhook service.

Three messengers, one API

Signal, SimpleX, and Session — normalized into a single REST contract. Group messages included, with automatic groupId routing.

View messenger setup →

Four integration paths

n8n trigger and send nodes. MCP server for any compatible AI agent. Agent Zero plugin for bi-directional chat. REST API for everything else.

Explore integrations →

Poll or webhook — your choice

Poll our API when you're behind a firewall. Use webhook delivery when you want push notifications — with automatic retries and circuit breaker.

Delivery options →

Relayed, not stored

No message content persists after delivery. Separate read/write Redis credentials. Crypto payments (Monero (XMR), native coins (ETH, Base, Polygon, BSC, TRON), and stablecoins (USDC, USDT)).

Privacy details →

Use cases

What you can build.

Real workflows powered by encrypted messages — no custom bridge code required.

n8n automation

Trigger n8n workflows when encrypted messages arrive. Send replies back through the same node. Batch up to 50 messages per call.

PrivacyFlow Trigger node polls for incoming
PrivacyFlow Send node for outgoing
Works with any n8n workflow

Install n8n node →

AI agent chat

Connect MCP or Agent Zero for bi-directional AI conversations through encrypted messengers. Your agent responds to Signal, SimpleX, or Session messages.

MCP server for Claude, Cursor, and others
Agent Zero plugin for full bi-directional chat
One context per contact, persisted across restarts

Set up AI agent →

Webhook delivery

Receive messages at your endpoint with automatic retries, circuit breaker, and dead letter queue for undeliverable payloads. The system handles retries and cleanup automatically — no manual intervention required.

Push delivery to your webhook URL
Circuit breaker with automatic recovery
Automatic dead-letter handling (no user action needed)

Webhook setup →

Integrations

Four ways to connect PrivacyFlow to your stack.

Whether you use n8n, AI agents, or plain webhooks — PrivacyFlow has a native integration path. No custom bridge code required.

Sample request

# REST API — poll for messages
GET /api/v1/messages/poll?limit=10
Authorization: Bearer pf_live_xxxxxx

# REST API — send messages
POST /api/v1/messages/send
Authorization: Bearer pf_live_xxxxxx
Content-Type: application/json

{
  "messages": [
    {
      "appId": "app_123",
      "contactId": "+1-555-0100",
      "messenger": "signal",
      "message": "Reply received!"
    }
  ]
}

# n8n: Install PrivacyFlow Trigger + Send nodes
# MCP:  Add PrivacyFlow MCP server to any compatible agent
# A0:   Enable PrivacyFlow channel plugin in Agent Zero

How messages flow

1

Message arrives

A contact sends a message on Signal, SimpleX, or Session.

2

PrivacyFlow relays

Our chat handler normalizes the payload and routes it to your poll queue or webhook.

3

Your stack receives

You poll the API, n8n triggers, your AI agent responds, or your webhook processes the message.

Prefer CLI deployment? View CLI recipe.

If clipboard access is blocked, highlight the snippet and copy it manually — we never capture what you copy.

Pricing

Start free. Upgrade when you need more.

Simple, transparent pricing. Crypto payments accepted — Monero (XMR), native coins (ETH, Base, Polygon, BSC, TRON), and stablecoins (USDC, USDT). No billing address required.

Free

Get started

Everything you need to try PrivacyFlow.

$0forever

One app, one messenger
Poll delivery (REST API)
n8n trigger + send nodes
Community support

Connect

Pay in XMR, BTC Lightning, or approved stablecoins. We never collect billing addresses.

Pro

Best value

Full relay for teams and power users.

$5per month

Unlimited apps
All three messengers
Webhook delivery with DLQ
MCP server + Agent Zero plugin
Batch sending (up to 50/call)
Priority support

Connect

Pay in XMR, BTC Lightning, or approved stablecoins. We never collect billing addresses.

Enterprise or crypto treasury billing? Talk with sales.

FAQ

Questions, answered.

Everything you need to know before connecting your first messenger.

Signal, SimpleX, and Session. All three are fully supported with bi-directional messaging — receive and reply through the same API. Group messages are supported with automatic groupId routing.

Need a deeper dive? Contact privacy team.