Privacy policy

Who we are

Blip24 is a service that watches the status of the third-party vendors a business depends on. It is operated by [to be completed], [to be completed]. Contact us about privacy at [to be completed].

For your account and billing data we decide how the data is used (we are the controller). For data your organization puts into Blip24 about other people — teammates you invite, subscribers to your status page, the destinations your alerts go to — we process it on your organization's behalf and on its instructions.

What we collect

• Account. Your name, email address, role, time zone and your organization's name. Your password is stored only as a bcrypt hash; we cannot read it.
• What you configure. Boards, the vendors you monitor, status pages you publish, and endpoints you ask us to check, with the results of those checks (kept for 90 days).
• Alert destinations. Email addresses, webhook URLs, API keys and signing secrets for the channels you connect (Slack, Teams, PagerDuty, Opsgenie and others), plus a record of each delivery. Destination URLs and channel secrets are encrypted in our database.
• Error signals. If you point your monitoring tool at your Blip24 signal URL, we store each payload as received, along with the source, service name, title, event count and time we extract from it. Configure your tool not to include personal data in those alerts.
• Team invitations. The invitee's email address, role, who invited them and when the invitation expires. The invitation link's token is stored only as a SHA-256 hash.
• Status page subscribers. Email addresses of people who subscribe to a status page one of our customers publishes. A subscription only starts after the address is confirmed from the email we send (double opt-in), and every notification carries an unsubscribe link. The customer who owns the status page decides what it is for.
• Billing. Payments are handled by Stripe. We keep the provider's customer and subscription identifiers, the plan, billing interval, subscription status and renewal date. Card details are entered on the provider's own pages and never reach our servers. When you start a Stripe checkout we give Stripe your email address and an internal organization number.
• Onboarding. To suggest which vendors to monitor, we read the public DNS records (such as SPF, MX and CNAME) of the domain in your email address.
• Visitors to the public site. Our web server logs your IP address, the page path (without its query string), the time and your browser's user agent. IP addresses are also used briefly as rate-limit counters.
• Anonymous outage reports. When you press "I'm seeing problems too" on a vendor page we store the vendor, the time, and a keyed hash (HMAC-SHA256) of your IP address and user agent, so one person cannot vote twice. We do not store the IP address or user agent themselves for this.
• Public tools. Four tools make a request from our servers on your behalf: is it down requests the site you name, the SSL checker connects to it to read its certificate, the stack scanner looks up the domain's public DNS records, and the status page detector fetches the status page URL you give it. Each result is cached briefly (from a minute to an hour) so the same check is not repeated, and none of it is linked to you. To rate-limit them, a hash of your IP address is kept as a counter that expires within a minute; it is not stored with the result.

Cookies

We set only the cookies the site needs to work:

• blip24_session keeps you signed in and holds short-lived form state. It is HTTP-only, sent only over HTTPS, and marked SameSite=Lax so other sites cannot use it to act on your behalf.
• XSRF-TOKEN protects your account against cross-site request forgery.
• A "remember me" cookie, only if you tick that box when signing in.

There are no analytics, advertising or tracking cookies and no third-party scripts, so there is no cookie banner: these cookies are strictly necessary. Fonts are served from our own servers, so loading a page contacts nobody else.

Why we use it

• To provide the service your organization signed up for: monitoring, alerts, status pages and reports (performance of our contract).
• To keep the service secure and prevent abuse, through logs, rate limits and the outage-report hash (our legitimate interest in running a safe service).
• To bill you and keep the records tax law requires (legal obligation).
• To send the email the service depends on: address verification, password resets, invitations, alerts and status page notifications. We do not send marketing email.

Who we share it with

The service providers that process data for us are listed on the subprocessors page. Alerts go wherever you tell us to send them — a Slack workspace, a PagerDuty service, a webhook — and those destinations receive the alert content because you configured them. We do not sell personal data.

International transfers and the safeguards that cover them: [to be completed].

How long we keep it

• Account and configuration data: for as long as the organization's account exists.
• Endpoint check results: 90 days, deleted nightly after that.
• Web server logs: [to be completed].
• After an account is deleted, and for error signals, outage-report hashes and billing records: [to be completed].

Your rights

You can ask us for a copy of your personal data, to correct it, to delete it, to receive it in a portable format, or to stop or restrict how we use it. Email [to be completed]. The account owner can also do two of these without asking: download an export of the organization's data, and delete the organization with everything in it, both under Settings → Danger zone. If you are a status page subscriber or a teammate invited by one of our customers, you can also ask that customer. You have the right to complain to your data protection authority.

Security

How we protect data, and how to report a vulnerability, is on the security page.

Changes

If we change this policy in a way that matters, we will update the effective date above and tell account owners by email before the change applies.