Channels / Signal
Signal with an audit record
Keep end-to-end encryption and still hold an audit record. Groups, attachments and disappearing chats archive inside your own tenant.
Signal
liveConnected accounts are running in production today.
The connection
How Signal connects
A signald daemon links to your Signal number as a secondary device. Decryption happens on your own instance, and the keys sit in a tenant database that no other workspace queries.
Signal is where the sensitive part of a negotiation happens. We link as a device, so encryption is never broken, and the plaintext index stays inside your tenant with your own keys.
Transport
Linked device via signald, keys held in your tenant
Counted as
One connected account. Conversations are never metered and teammates are never billed, on any plan.
See what an account costssignal.adapter • live • 5 capabilities
Capabilities
What the Signal adapter carries
Linked device, end-to-end intact, local key custody.
End-to-end encryption preserved
Bring your own index keys
Disappearing messages archived before they go
Group indexing
Attachment vault
The AI layer
Tuned for Signal, not for everything
The same models run on every network, with the parts that only matter on Signal turned on here.
01
Disappearing capture
Chats set to expire land in your audit vault before Signal erases them.
02
Commitment tracking
Promises and deadlines made in a Signal thread get flagged and dated.
03
Attachment scanning
Images and files become searchable text the moment they are decrypted.
Spam shield, thread summaries and search run on every plan. Commitment tracking, reply debt, relationship health and live translation in 42 languages start on Team, and they cover every connected account, including this one.
The AI layerHistory and export
Signal keeps message history on the devices themselves, so a linked device receives a short recent window rather than the back catalogue. Indexing starts at linking and older Signal threads stay on the handsets. What arrives after linking stays in your tenant and exports on request.
Your archive
Signal history you can take
Indexed for the life of the account on all four plans, from 1 GB on Starter to 1 TB on Scale. A single export runs to 1 GB on Starter and Team, 25 GB on Scale and uncapped on Enterprise, and the archive stays readable after you close the account.
Questions
Signal, specifically
What buyers ask before they connect this one. Anything else and a person who worked on the adapter will reply.
Ask us directlyDoes linking break Signal end-to-end encryption?
No. The signald worker registers as an official secondary linked device, the same way Signal Desktop does. Decryption happens inside your own workspace instance.
Can we retrieve messages that vanished on the phone?
Yes. Once the linked device takes a message in, it is committed to your archive before the client-side timer clears it from the handsets.
Can we import our older Signal threads?
No. Signal hands a new linked device a limited recent window, so anything older than that stays on the phones. If you need those threads on the record, keep the handset export from Signal itself.
Where are the Signal decryption keys stored?
In your isolated tenant container. On Enterprise you hold them in your own KMS or Vault, and the material stays out of our reach.
Next
Read these next
Ten live networks, one workspace
Connect your first accounts in ten minutes. Unlimited teammates and permanent history indexing on every plan.