Alerts only you can read.
End-to-end encrypted alerts from your servers, scripts and AI agents. Each one is sealed on your server before it’s sent and opened on your iPhone. Unlike Telegram bots, we can’t read your private alerts.
Included on every plan. Turn it on in the app: Account → Private alerts.
{
"channel": "Payments",
"level": "critical",
"encrypted": {
"v": 1,
"epk": "Xq3oW0f9n6Vh8dKp…",
"ct": "9Jt2KcV0uQ4nL1mYb7sE…",
"keys": [{ "kid": "Zmh6rfhivXdsj8GL", "key": "…" }]
}
}
Your iPhone opens it with your key. Nobody in between has that key, including us.
Sealed before it leaves, opened on your phone.
The key that opens your alerts is made on your iPhone and never leaves your devices.
- Turn it on in the app
Your iPhone makes your key. iCloud Keychain syncs it to your other Apple devices, and you save a recovery code in case you ever need it.
- Your server seals each alert
Our CLI or library fetches your public key, encrypts the alert on your server, and sends only the sealed version. Same messages as before: emoji, lines, fields and links.
- Your iPhone opens it
It arrives like any alert, with the full message on your Lock Screen and in the app. Alarms and critical alerts work the same.
No readable copy to leak.
If our database were ever stolen, all anyone would find is the sealed version.
- We can’t see the alert
Titles, messages, fields, links and photos are sealed. So are the names, emails and amounts inside them.
- We can see when
Which channel an alert arrived in, the time, roughly how big it was and whether it’s been read.
- We can see your account
Your email, your plan, and your phone number if you use texts. Name channels plainly (“Ops”, not the client’s name): channel names aren’t encrypted.
- Deleted on your schedule
Set a private channel to delete its alerts after 1, 7 or 30 days. After that there’s nothing left, sealed or not.
Bots never get secret chats.
Telegram’s end-to-end encryption is only for secret chats between two people. Bot messages are ordinary cloud chats that Telegram can read.
| Telegram bot | I Need Alerts private alerts | |
|---|---|---|
| End-to-end encrypted | No | Yes |
| Can the service read your alerts? | Yes, they’re stored readable on Telegram’s servers | No, we only store the sealed version |
| Rings like an alarm, breaks through Focus | No | Yes |
| AI agents can read them | Through the bot, in plain text | Only agents you pair, with their own key |
One flag on the command you already run.
Turn on private alerts in the app first: Account → Private alerts. Then send with your API key.
From a terminal or script
export INEEDALERTS_API_KEY=ina_…
npx ineedalerts send --private --channel Payments \
--title "Payout failed · \$1,240.00" --body "Acme Supply LLC · Stripe: account_closed" \
--link "Open in Stripe=https://dashboard.stripe.com/payouts"
From Node
import { IneedAlerts } from 'ineedalerts';
const alerts = new IneedAlerts({ apiKey: process.env.INEEDALERTS_API_KEY });
await alerts.sendPrivate({
channel: 'Payments',
level: 'critical',
title: 'Payout failed · $1,240.00',
body: 'Acme Supply LLC · Chase ••4417\nStripe: account_closed',
links: [{ label: 'Open in Stripe', url: 'https://dashboard.stripe.com/payouts' }],
});
Other languages: the format is open and uses standard encryption (X25519, HKDF-SHA256 and ChaCha20-Poly1305). See the developer docs.
Let an AI agent read them
In the app, tap Account → Private alerts → Add an agent, choose its channels, and run the code it shows on the agent’s computer. The agent gets its own key, and senders seal alerts for it too. Then add it to Claude Code:
npx ineedalerts pair ABCD-EFGH-JKLM
claude mcp add ineedalerts-private -- npx -y ineedalerts mcp
The agent opens alerts on that computer, so we still can’t read them. Whatever the agent reads goes to its AI provider as part of your conversation, so only give it the channels it needs.
Private alerts, plainly.
Do I have to use private alerts?
No. Normal alerts keep working exactly as they do now, and many are fine as they are. Private alerts are for channels with details you’d rather nobody else could read. You choose per channel.
What can’t I do with a private channel?
We can’t search it, show it on the website dashboard, or let AI apps connected through our hosted connector read it, because we can’t read it ourselves. The app and agents you pair can. Plain alerts to a private channel are refused, so nothing slips through unencrypted.
What if I get a new iPhone?
With iCloud Keychain on, your key comes with it. Otherwise open Account → Private alerts and enter your recovery code. Without the key or the code, private alerts can’t be opened by anyone, including us. You can start over with a new key, but older private alerts stay locked.
Can someone with my phone read them?
Yes, like any message on an unlocked phone. If you’d rather they didn’t show on the Lock Screen, set I Need Alerts previews to “When unlocked” in iOS Settings → Notifications.
Is it really end-to-end?
Yes. The key is made on your iPhone, alerts are sealed on the sender’s machine, and our server only ever passes the sealed version along. The sender’s own server has the alert before sealing it, so keep that server secure.
Can I read them on the website?
Not yet. Private alerts open in the iPhone and iPad app and on agents you pair. The website dashboard shows them as “Private alert”.