You send us your errors. Here's how we look after them.
Monitoring sees the inside of your apps, so we built Fidiba to hold as little as it can, and nothing it doesn't need.
We never hold your app's keys
Fidiba never asks for your Stripe, mail or AI keys. Your app checks them itself and sends a heartbeat: "works" or "fails".
Scrubbed before it is stored
Passwords, tokens, card numbers, emails and phone numbers are removed from errors and logs before they are written. You can add your own patterns.
Read-only connections
Connections to DigitalOcean, Cloudflare and GitHub use read-only tokens, stored encrypted. Settings shows when each was last used.
Write keys can't read
The key in your app can only send data in. A leaked key can add noise to one project, nothing more, and you can roll it in one click.
Each customer kept apart
Every stored row and file carries its account. The server adds the account to every query, never the browser.
The agent can't act
The agent reads errors, figures and logs and can open a draft pull request. It can't merge, deploy, restart or page anyone.
The details
- Where data is stored
- DigitalOcean, Frankfurt (EU). Backups in the same region.
- Encryption
- HTTPS for everything sent to Fidiba. Stored data and backups encrypted at rest.
- How long data is kept
- Set by your plan: errors 7 to 90 days, logs 3 to 14 days. Deleting a project removes its data within 7 days.
- Who at Fidiba can see your data
- Our staff, only to help with a problem or keep Fidiba running. Each look is read-only, at most 30 minutes, needs a reason and is recorded in our staff log.
- Services we use
- DigitalOcean (hosting), Cloudflare (network and this website), Anthropic (the agent), Twilio (SMS and calls), Stripe (billing), Resend (email)
- Reporting a problem
- [email protected]. We reply within one working day.
Read the full privacy notice and terms.