Messaging connectors — regulatory copy
Per-connector pre-link disclosure modal + persistent reminder line on each linked-account row. Same pattern, copy differs per platform.
Current state
Manage ConnectorsMulti-account works (Telegram ×2). No disclosure modal, no per-row regulatory state — adding both.
Post-connectSuccess modal lists connector states (Connected / Connect).
WhatsApp v1
whatsmeow bridge — unofficial. Meta can ban the linked account. Highest risk.
Heads up before you connect WhatsApp
Kimono pairs as a second device — same as WhatsApp Web — using an open-source bridge that isn't built by Meta.
- Meta may flag the device and ban your WhatsApp account. We can't prevent or reverse it.
- Rate limits and per-user isolation reduce the risk, but can't eliminate it.
- Messages stay private; we process on your behalf only.
- Unlink anytime in Settings → Linked Accounts.
I understand — continue
Cancel
Read the full terms
Settings row reminder: Connected via an unofficial WhatsApp bridge. Meta may ban accounts using this method. [Learn more]
Telegram v1
Multi-device pairing — officially supported by Telegram. Low risk; session revocable from Telegram.
Heads up before you connect Telegram
Kimono pairs as an additional device — same as Telegram Desktop. Telegram supports this officially.
- No ban risk.
- Kimono appears as an active session in Telegram. Revoke from there anytime.
- Messages stay private; we process on your behalf only.
- Unlink anytime in Settings → Linked Accounts.
I understand — continue
Cancel
Read the full terms
Settings row reminder: Kimono appears as an active session in your Telegram settings. [Learn more]
Drafts pending
- iMessage · Apple iCloud ToS · risk: Apple ID flag
- Signal · device-link protocol · risk: device limit
- Gmail · Google OAuth · risk: token revocation
- Microsoft · Microsoft OAuth · same as Gmail
Per-row state — needs Alek + Sutha
Each row needs a status indicator (paired / syncing / paused / error). Open: what states does backend emit? Recoverable in-app vs. external? Normalized model or per-connector enum? Storage on linked_accounts or separate table?