Why BugsRadar stores nothing

Updated 1 October 2026 · BugsRadar team

BugsRadar is forward-only. An event from your application stays in memory until it is delivered to the channels of its project, and then it is gone. Nothing is written to disk or to a database. This is the one design decision most of the product follows from.

What happens to an event

The package or the HTTP endpoint hands the event to BugsRadar. BugsRadar works out whether it is a new error or a repeat of one it is already counting, and either sends a full message to your channels or updates the count. While an error keeps repeating, it keeps in memory a counter, the latest sample and the id of the message it sent to your chat, so that it can write the count into that message. When the error stops, that is dropped too. There is no table of events anywhere.

Your users' data doesn't pile up on our disks

Stack traces and log properties carry personal data more often than anyone intends: an email address in an exception message, a user id in a property, an order number. In a product that stores events, that data accumulates on a third party's servers, month after month, and becomes something you have to think about. In BugsRadar it passes through memory and lands in a chat you control, through a bot or webhook you own. The only copy is yours.

Simpler compliance

For the data inside your events you are the controller and BugsRadar processes it on your behalf, only to deliver it. There is nothing to export when a user asks for their data and nothing to erase when they ask to be forgotten, because nothing was kept. The Privacy Policy says this in the language auditors expect, and the Security and data page lists the few things that are stored: your email, your projects, your channels with their credentials encrypted, your plan.

No storage, no quotas

Products that store events have to meter them, because storage is what they pay for. That is where event quotas come from, and the bill that arrives after a crash loop. BugsRadar has no storage to meter, so plans differ by features, not by volume: no event quotas on any plan, Free included. A bad night is a bad night for you, not an invoice from us.

What you give up

History. There is no page of past errors, no trend over a month, no search. The message in your chat is the record, and the chat is where it stays. If you need to look back, keep your logs, which you have anyway, or run an error tracker next to BugsRadar for the investigation. BugsRadar is for the moment an error first appears; see Alerts in chat instead of a dashboard.

Where the message lives

After delivery the message is in Telegram, Discord or Pushover, under that service's terms, in a chat you decide the membership of. Delete the channel in BugsRadar and the only thing that disappears on our side is the encrypted credential. The messages stay in your chat for as long as you keep them.

Where to go next

Security and data lists what is stored and how. Keep the API key secret explains the one thing you do have to protect. Or get started.