---
title: "Privacy policy"
url: https://badgerbell.com/privacy
mcp: https://badgerbell.com/mcp
---

# Privacy policy

Last updated: 25 October 2026

This policy explains what URLERT LLC ("BadgerBell", "we", "us"), a Texas limited liability company at 5900 Balcones Drive, Suite 100, Austin, Texas 78731, United States, collects when you use BadgerBell: the website at badgerbell.com, the app, the status pages, the API and the AI-assistant connector (together, "the Service"). It also covers why we collect it, who handles it for us and what you can do about it. The rules for using BadgerBell are in the [Terms of service](https://badgerbell.com/terms.md).

**The short version:**
- We collect what we need to check your sites, alert the people you choose and show your status pages.
- We never sell data, and we use no advertising or tracking cookies.
- Phone numbers are used only to send the alerts and the confirmation code you asked for. Mobile information is not shared with third parties or affiliates for marketing or promotional purposes.
- Your data is kept in the European Union.

[Text alerts](https://badgerbell.com/text-alerts.md): how people opt in to BadgerBell's alert texts, and how to stop them.

## \1. Who we are

URLERT LLC runs BadgerBell. We decide why and how the personal data described here is used. For your own customers' data, such as the email addresses of people who subscribe to your status page, you decide and we handle it for you. Contact: support@badgerbell.com.

## \2. What we collect

### If you have an account

- **Account:** your name and email address, and how you sign in (Google, or an email address with a password, and any passkey or authenticator app you add). Passwords and authenticator keys are stored in a form we can't read back.
- **Teams:** the teams you are in and your role, and the invitations you send, including the invited email address.
- **Your monitors:** what you ask us to check (addresses, servers, schedules, how often and from where), their settings and notes, and the results: up or down, response times, certificate and domain details, and the reason a check failed. For an incident we also keep a snapshot of what the site answered: the response body and headers, the certificate, DNS answers and timings.
- **Monitor credentials:** headers, tokens, passwords and request bodies you give a monitor. They are stored encrypted, and they are sent to our probes sealed, so that only the probes can read them.
- **Alert contacts:** the email addresses, phone numbers and chat channels you add to be told about a monitor, and your alert rules. A phone number is texted a confirmation code before it is used.
- **Status pages and subscribers:** the words and design of your status pages, and the email addresses of people who subscribe to them. A subscriber confirms their address before we send anything. Subscribers' addresses are seen by the team that owns the page, and never by an AI assistant or agent.
- **Slack, if you connect it:** the workspace and channel you pick, and the access token Slack gives us, so we can post alerts there. We do not read your messages.
- **Google sign-in, if you use it:** your Google account ID, your email address and your name, as Google shares them when you sign in. We ask Google for nothing else.
- **Billing, when paid plans exist:** your plan and its history. Card details are taken by Stripe, our payment processor, and never reach our servers. No card is taken today.
- **Activity:** what people and AI assistants in your team changed, and each sign-in, with its method, country and IP address. A sign-in from a new device or country is marked as unusual.
- **Access:** API tokens (stored in a form we can't read back) and connected AI assistants, with when they were last used.
- **Help and abuse:** what you write to us, and reports about the pages or monitors we are told about.

### When someone visits a status page or subscribes

A status page is public. To show it, our servers and Cloudflare, which sits in front of them, receive the visitor's request, including their IP address and browser. We use that to serve the page and keep it secure, and we do not build profiles of visitors. A person who subscribes gives their email address and confirms it.

### Security and cost logs

Our servers keep logs of requests (the IP address, the page asked for and the browser) and of errors. We use them to keep the Service secure, to stop abuse and to find faults. We also count emails, texts, calls and AI use for each team, to keep costs in check and to catch abuse.

### Cookies

We use cookies only to keep the Service working, and none is for analytics or advertising:
- to keep you signed in, and to tell this browser apart from another;
- to protect sign-in, such as short-lived ones while you sign in with Google or with a second factor (up to ten minutes), and one that makes sure a stranger's wrong guesses can't lock you out of your own account;
- to remember a language or colour theme you choose.

Cloudflare, in front of BadgerBell, may set a strictly necessary cookie to protect the Service from bots.

## \3. How we use it

- **To run BadgerBell for you:** to check what you asked us to check, send the alerts you chose, show your status pages, run your account and team, and answer your questions. This is the contract between you and us.
- **To keep it secure:** to sign people in safely, to spot unusual sign-ins, to stop abuse and attacks, to enforce limits and to hold costs, such as a team that suddenly sends far more than usual. This is our legitimate interest in keeping the Service secure.
- **To tell you things about your account:** invitations, confirmations, sign-in links, alerts, notices about your plan, and changes to our terms or this policy. We send no marketing.
- **To explain failures (not on yet):** BadgerBell has no built-in AI feature today. When it adds one, such as an explanation of why a check failed or a drafted status update, and you use it, the facts about that check or incident are sent to our AI provider to write the text. AI explains and drafts only. It never decides whether an alert is sent, and nothing it writes reaches a status page without a person.
- **To meet the law,** if it requires us.

**What we don't do:** sell personal data; use it for advertising; use it to build profiles of the people who visit status pages; or use it to train AI models.

**Google user data.** What we receive from Google when you sign in (your account ID, email address and name) is used only to sign you in and to run your account. We do not sell it, share it for advertising, or use it for anything else. BadgerBell's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

## \4. Who handles it for us

We use a small number of providers to run BadgerBell. They process data only for us and on our instructions.
- **DigitalOcean:** hosting. Our servers, and our checking locations, run on it. Our main server is in Amsterdam.
- **Cloudflare:** DNS, the network in front of the Service, bot protection, and storage of our encrypted backups (R2, in its EU jurisdiction).
- **Resend:** sends our emails, including sign-in links, confirmations and alert emails. It receives the recipient's address and the email's content.
- **Twilio:** sends alert texts, and the confirmation code. It receives the phone number and the text.
- **Slack:** when you connect it, receives the alerts we post to your channel.
- **Google:** sign-in, if you choose it.
- **Stripe:** payments, when paid plans start.
- **Anthropic (not in use today):** the AI model behind built-in AI features, once BadgerBell adds them and you use one. It receives the facts of that check or incident, and nothing else about you.
- **Healthchecks.io:** receives BadgerBell's own uptime signals. These hold no customer data.

A data processing agreement and the current list of these providers are available on request at support@badgerbell.com. We post a new provider on the list 30 days before it starts handling customer data, where reasonably possible.

We may also disclose data if the law requires it, to protect people from harm, or as part of a sale or merger of BadgerBell, in which case this policy and the promise in the Terms continue to apply.

## \5. Text messages and phone numbers

- A phone number is used only to send the alerts about monitors the person chose, and the one text with the confirmation code that they asked for. We send no marketing texts.
- Texts go only to numbers confirmed with a code. Nobody can add your number for you.
- Reply **STOP** to opt out at any time, and **HELP** for help. Message and data rates may apply.
- **No mobile information is shared with third parties or affiliates for marketing or promotional purposes.** Information sharing to subcontractors in support of the service, such as Twilio, which delivers the texts, does not include mobile opt-in data and consent. This information will not be shared with any third parties for their own purposes.

The words of the texts, and how a person opts in, are on [the opt-in page](https://badgerbell.com/text-alerts.md).

## \6. Where it is kept

Your data is kept in the European Union: on DigitalOcean in Amsterdam, with backups in Cloudflare R2's EU jurisdiction. Some providers named in section 4, such as Google, Twilio, Slack, Stripe and Anthropic, are based in or run services in the United States and receive data in the course of their work. When data goes from the UK or the European Economic Area to a country without an adequacy decision, we rely on the safeguards our providers offer, such as the EU-US Data Privacy Framework where a provider is certified under it, and Standard Contractual Clauses.

## \7. How long we keep it

- **Single checks:** 48 hours.
- **Hourly totals:** 90 days.
- **Daily totals:** as long as your plan keeps history (3 months on the free plan, up to 24 months on paid plans). If you move to a smaller plan, older daily totals are deleted after the 60-day price lock ends.
- **Incidents and their snapshots:** with the incident, as long as your plan keeps history.
- **Activity and sign-in records (with the IP address and country):** at least 12 months.
- **Account and team data:** until you delete your account or team. Monitors and status pages you delete go to a bin for 30 days and can be restored, then they are deleted.
- **Status page subscribers:** until they unsubscribe or the page is deleted. A subscriber who never confirms is deleted after 7 days.
- **Backups:** kept 30 days, so deleted data leaves our backups within 30 days after it is deleted.
- **Security logs:** kept only as long as we need them for security and to find faults.

## \8. Your choices and rights

- **Export** every monitor, alert rule and status page, and your check history, from the app at any time.
- **Delete** your account from the app, or ask us to. If you are the only owner of a team that has other people in it, make someone else an owner first.
- **Correct** your name and contact details in the app.
- **Stop texts** by replying STOP, or by removing the number in the app.
- **Unsubscribe** from a status page with the link in any of its emails.

Depending on where you live, you may also have the right to access, correct, delete or move your data, to object to or restrict how we use it, to withdraw consent you gave, and to complain to your data protection authority. To use any right, or to ask what we hold about you, email support@badgerbell.com. We answer within 30 days. We do not treat anyone worse for using their rights.

If you are a subscriber to someone's status page, the team that runs the page decides what is sent to you. You can ask us to delete your address too.

## \9. Organizations and clients

If you use BadgerBell for an organization or for a client, your organization controls what is in its team, and we handle it on its behalf. A data processing agreement is available on request at support@badgerbell.com.

## \10. Security

We protect data with encryption in transit (HTTPS), encrypted backups, credentials for monitors that are stored encrypted and sent sealed to the probes, passwords and tokens that we can't read back, two-factor sign-in with passkeys and authenticator codes, and access limited to the people who run BadgerBell. No service is perfectly secure. If a breach affects your data, we tell you within 72 hours of learning of it, or as the law requires. To report a security problem, write to support@badgerbell.com.

## \11. Children

BadgerBell is not for anyone under 16, and we don't knowingly collect their data. If you think a child has given us data, contact us and we will delete it.

## \12. Changes to this policy

For changes that matter, we tell you by email at least 30 days before they take effect, unless we must change something sooner for security or the law. The date at the top shows the last update.

## \13. Contact

- Post: URLERT LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78731, United States

Questions, requests about your data and security problems: [support@badgerbell.com](mailto:support@badgerbell.com)