How Tellnod keeps sending in your hands

Two steps between a draft and a send

1. Prepare. The assistant asks Tellnod to prepare a send. Tellnod freezes the audience, counts recipients and exclusions, and returns a confirmation card. Nothing is scheduled yet.
2. Confirm. Only the Confirm button on the card, or the confirmation page on tellnod.com for apps that cannot show cards, can schedule the campaign. The AI app is never given a tool that sends.

Each confirmation token is random, stored only as a hash, bound to your workspace and to the person who prepared it, usable once, and expires after 10 minutes. If the audience changed since the card was shown, the confirmation is refused and the send must be prepared again.

Send permission lives on our server, not in the AI app

Signing in only proves who you are. When you confirm your first send, you explicitly allow Tellnod to send on your behalf. That consent is stored with an audit record, and you can revoke it from your account card at any time.

After you confirm

• Scheduled campaigns can be cancelled until they go out.
• New accounts ramp up gradually, and sending pauses automatically if the spam complaint rate passes 0.1%.
• Unsubscribe links, one-click unsubscribe headers, your postal address and consent records are added to every campaign.

Data isolation

• Each workspace's contacts, campaigns and results are separate, and every request is checked against the signed-in workspace.
• Each account sends through its own isolated sending configuration, so one sender's reputation does not affect another's.
• We do not receive or read your chat history. Tellnod only sees what the assistant passes to its tools.
• Content that comes from outside (contact fields, imported files, websites) is treated as untrusted data and kept apart from instructions to the assistant.

Infrastructure

• Secrets live in a managed secret store, never in the code repository; deployments use short-lived credentials.
• The database is reachable only through an encrypted connector, and services run as non-root with one service account each.
• Rate limits apply per AI client and per workspace.
• Outside production, no channel adapter can send a real message.

Reporting a vulnerability

Email security@tellnod.com with a description, steps to reproduce and the impact you observed. We aim to acknowledge reports within 2 business days.

FAQ