Privacy notice
Last changed 19 November 2026 · What changed
In short
- We keep the errors, figures and logs your apps send, scrubbed, for as long as your plan says.
- We never sell data or use it to train AI models.
- You can download or delete everything from your account page.
1. Who we are
Fidiba is a monitoring service. It takes the errors, figures, logs and traces your apps send, checks your sites from outside, works out what needs you, and pages the people on call. It is run by Fidiba, LLC, a Delaware limited liability company, 131 Continental Dr, Suite 305, Newark, DE 19713, United States ("Fidiba", "we", "us").
This notice covers:
- this website, fidiba.dev, and the status pages we host on it;
- the Fidiba app at app.fidiba.dev, and the address your apps send data to;
- the emails, push notifications, text messages and phone calls Fidiba sends.
For your own account details, and for how we run Fidiba, we decide how data is used: we are the controller. For the data your apps send us, and for the people who subscribe to your status page, you decide what is sent and why: you are the controller and we are your processor. We use that data only to run Fidiba for you, as these terms and your settings say. If you need a data processing agreement, write to us at [email protected].
2. What we collect
About you, when you use Fidiba
- Your account: your email address, your name, your time zone, the teams you are in and your role in each (Owner, Member or Viewer).
- How you sign in: if you use Google or GitHub, the few details listed in Signing in with Google or GitHub. For a passkey, its public key (your device keeps the private part). For an email link, a fingerprint of the link (not the link itself) for 15 minutes.
- Signing in safely: the IP address of each sign-in request, for an hour, to stop people guessing; the city Cloudflare reports for that address, put in the sign-in email so you can spot one you didn't ask for; and when each of your sessions started and was last used.
- How to reach you: the phone number you verify for text messages and calls, your quiet hours, and each browser you turn alerts on in (its push address and the device name you see in Settings).
- What you do in Fidiba: an audit log of changes made in your team, such as rules changed, keys rolled, people invited and pages taken or passed, with who made each one.
- Billing, for Owners of paid teams: your plan, invoices and the card's brand and last four digits. The card itself is held by Stripe, never by us.
- People you invite: their email address and the role you chose, until they join or the invitation ends.
- When you write to us: what you send and our replies.
What your apps send, and what Fidiba checks
- Errors, figures, logs and traces your apps send through the Sentry SDK, OpenTelemetry, Prometheus or Vector, after scrubbing (below). Request bodies are off unless you turn them on.
- Releases: the version, and the commit, author and notes if your deploy sends them.
- Heartbeats and checks: when your jobs check in, and what our checkers see when they visit your sites, certificates and domains.
- Connected accounts: if you connect DigitalOcean, Cloudflare or GitHub, a read-only token, stored encrypted, and what it reads (backups, servers, firewalls, release changes).
- Status pages: the updates you post, and the email addresses of people who subscribe to your page.
Your apps' data can hold details about your own users, such as an IP address or a user id in an error. You decide what your apps send. Please don't send health, financial or other sensitive details about people.
On this website
The website and hosted status pages are plain pages. They set no cookies and run no analytics or advertising code. Cloudflare, which serves them, sees your IP address and browser details to deliver the page and block attacks.
3. Signing in with Google or GitHub
You can sign in to Fidiba with Google or GitHub instead of an email link. Both are optional. We use them only to know it is you, and we ask for the smallest access each offers.
Fidiba asks Google for the openid, email and profile permissions, which let us read:
- your Google account id, which Google calls the subject;
- your email address, and whether Google has verified it;
- your name.
We don't ask for, and can't see, your Gmail, contacts, calendar, files or anything else in your Google account, and we don't use your profile picture.
- How we use it: the first time, we match Google's verified email address to your Fidiba account, or make a new account with that address and name if you are signing up. After that, Google's account id alone signs you in. We use your name and email address only to show who you are in your team and to send you Fidiba's own emails.
- What we store: your Google account id and the email address it signed in with, joined to your Fidiba account, plus your name and email address on the account itself. We check the token Google sends at sign-in and then throw it away. We keep no Google access or refresh token, so Fidiba can't reach your Google account after you are signed in.
- Who we share it with: only the people in your Fidiba teams see your name and email address, and our email service (Resend) uses your address to deliver Fidiba's emails to you. Nobody else gets it. We never sell it, never use it for advertising, and never use it to train AI models.
- Deleting it: Delete my account on your account page removes your Google link along with your account straight away. Database backups are overwritten within 7 days. You can also remove Fidiba's access at any time in your Google account under Third-party apps and services.
Fidiba's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
GitHub
Fidiba asks GitHub for the read:user and user:email permissions, which let us read your public profile and your email addresses. We read only:
- your GitHub user number and username;
- your name, if you have set one;
- the email addresses GitHub has verified.
Signing in can't read or change your repositories, organisations or anything else on GitHub.
- How we use it: the first time, we match one of your verified email addresses (your primary one first) to your Fidiba account, or make a new account with it if you are signing up, named after your GitHub name or username. After that, your GitHub user number alone signs you in.
- What we store: your GitHub user number and username, joined to your Fidiba account, plus the name and email address on the account itself. We throw GitHub's token away as soon as we have read these details. We keep no GitHub token from sign-in.
- Who we share it with: the same as for Google above: your teams see your name and email address, Resend delivers Fidiba's emails, and nobody else gets it.
- Deleting it: Delete my account removes your GitHub link along with your account. You can also revoke Fidiba in GitHub under Settings › Applications.
Connecting GitHub so the agent can read release changes is separate from signing in. It uses its own GitHub App, which a team Owner installs on the repositories they choose.
4. What we never collect
- Passwords. Fidiba has none. You sign in with Google, GitHub, an email link or a passkey.
- Your app's own keys, such as Stripe, mail or AI keys. Your app checks them itself and sends a heartbeat saying whether they work.
- Secrets and personal details in your data. Before anything is stored, the processor removes passwords, tokens, card numbers, email addresses and phone numbers from errors and logs, using the same rules as Sentry's SDK plus any patterns you add.
- Card numbers. Payments go through Stripe's own pages.
We never sell data, never use it for advertising, and never use it to train AI models.
5. Cookies and storage
The app uses only what it needs to sign you in and remember your settings:
| Name | What it does | How long |
|---|---|---|
plumb_session | Keeps you signed in. Only the app can read it. | 30 days, or until you sign out |
plumb_google, plumb_github | Ties the end of a Google or GitHub sign-in to its start, so nobody else can finish it. | 10 minutes |
| Appearance, in your browser's storage | Remembers System, Light or Dark on this device. | Until you clear it |
These are all needed for Fidiba to work, so there is nothing to switch off. Cloudflare may add its own security cookie to tell people from bots. We use no tracking, analytics or advertising cookies.
6. Why we use it
| What for | Legal basis |
|---|---|
| Running Fidiba: storing your apps' data, finding problems, showing your outline, status pages and checks | Our contract with you |
| Paging the people you put on call, by push, text message, phone call and email, and the morning summary | Our contract with you |
| Billing and keeping invoices | Our contract with you, and the law on keeping accounts |
| The agent investigating a problem, when your plan includes it | Our contract with you |
| Keeping Fidiba and your account secure: sign-in limits, sign-in emails, the audit log | Our legitimate interest in a safe service |
| Helping you when you ask, and telling you about changes to Fidiba or these terms | Our contract with you, and our legitimate interest |
| Meeting legal requests | Legal obligation |
We don't send marketing email. If we ever do, we will ask first and every email will have a way to stop.
7. Who we share it with
We use these services, each only for the part it does:
| Service | What it does for Fidiba | What it gets |
|---|---|---|
| DigitalOcean | Servers, the database and file storage | Everything Fidiba stores, encrypted at rest |
| Cloudflare | DNS, the secure tunnel to the app, and serving this website | Traffic to and from Fidiba, including IP addresses |
| Anthropic | The agent that investigates problems (Claude) | The evidence for one problem: scrubbed errors, figures, logs and release changes |
| Twilio | Text messages and phone calls | Your phone number and the alert's words |
| Resend | Email addresses and the email's words | |
| Stripe | Payments and invoices | Owners' billing details and card |
| Google, GitHub | Sign-in, only if you choose them | That you are signing in to Fidiba |
| GitHub | The agent reading release changes and opening draft pull requests, only if you connect it | What the agent writes in a draft pull request |
| Your browser's push service (Google, Apple or Mozilla) | Delivering push alerts | An encrypted alert it can't read |
| Hetzner, Fly.io | Checkers that visit your sites from other networks | The addresses you ask us to check |
| Better Stack | Watching that Fidiba itself is up, and keeping our own servers' logs | Our servers' logs, which never hold secrets or scrubbed fields |
Under Anthropic's commercial terms, what we send through its API is not used to train its models. Each service is bound by a contract to use the data only to do its part for us.
Apps and agents you connect to Fidiba (for example over MCP) see what you allow them to, for the projects you choose. Your status page and its updates are public, because that is what they are for.
We share data with anyone else only if the law makes us, and then only what it requires. We will tell you first unless the law forbids it. If Fidiba is sold or merged, your data moves with it under this notice, and we will tell you before that happens.
8. Where it is kept
Fidiba's servers, database, files and backups are with DigitalOcean in Frankfurt, Germany (EU). Some of the services above work from other countries, including the United States. When data goes outside the EU or the UK, we rely on the safeguards each service offers, such as the European Commission's standard contractual clauses.
9. How long we keep it
| What | How long |
|---|---|
| Raw errors and figures | Your plan's history: Free 7 days, Team 30, Business 90 |
| Logs | Free 3 days, Team 7, Business 14 |
| Traces | Free 3 days, Team and Business 7 |
| Issues, their counts and the agent's write-ups | As long as the project exists |
| A deleted project | Restorable for 7 days, then its data and files are removed |
| A project paused because the plan went down | 30 days, with a warning a week before and on the day, then its data is removed |
| Your account | Until you delete it. Audit log rows stay, without your name on them |
| A sign-up never finished | 7 days |
| Sessions | 30 days, or until you sign out |
| Sign-in links and passkey challenges | 15 minutes and 5 minutes |
| IP addresses of sign-in requests | 1 hour |
| Invitations | 7 days, or until taken |
| Your download of your data | 7 days after it is made |
| Database backups | 7 days |
| Our staff's log of support work | 2 years |
| Invoices and payment records | As long as tax and accounting law requires |
As a backstop, any raw data file older than 100 days is deleted whatever happens. Removed data can stay in backups for up to 7 more days.
10. Keeping it safe
- Everything sent to Fidiba goes over HTTPS. Stored data and backups are encrypted at rest.
- Every team's data is kept apart by the database itself, not only by our code. The browser never decides which team it sees.
- A project's write key can only send data in. It can't read anything.
- Tokens for connected accounts are read-only and encrypted. Settings shows when each was last used.
- Our servers have no open login port. Our staff reach them only over a private network, and our staff console can't be reached from the internet at all.
- Our staff look at a team's data only to help with a problem or to keep Fidiba running. A look is read-only, lasts at most 30 minutes, needs a reason, hides restricted values, and is recorded in our own staff log. We don't send you a notice each time.
If a breach puts your data at risk, we will tell you without undue delay, and the authorities where the law requires. More on the security page.
11. Your rights
Depending on where you live, you can ask us to:
- show you what we hold about you, and give you a copy;
- correct it;
- delete it;
- stop or limit using it, or object to how we use it;
- give it to you in a form another service can read.
Most of this you can do yourself on your account page: change your name and time zone, Request export for a zip of everything you and your teams hold, and Delete my account. If you are the only Owner of a team that has other people or projects, pass the team on or delete it first.
For anything else, write to [email protected]. We reply within 30 days. If your details came to us in a customer's data, for example an error from their app, ask that customer first: they decide what is kept, and we help them answer.
You can also complain to the data protection authority where you live or work.
12. Children
Fidiba is a tool for work. It is not for anyone under 16, and we don't knowingly hold their details.
13. Changes to this notice
When this notice changes, the date at the top changes and the change is listed below. If a change matters to how your data is used, we email the Owners of every team at least 30 days before it applies.
14. Contact
Fidiba, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States.
Email [email protected]. To report a security problem, write to [email protected].
What changed
- 19 November 2026: Added exactly what Google and GitHub sign-in read, store and share, and how to delete it, with Google's Limited Use statement.
- 19 November 2026: First full notice, written from how Fidiba works today.