Privacy, plainly.
What we collect, why, how long we keep it, and what you can make us do with it.
Last changed 8 October 2026. If this page ever changes in a way that matters, the date changes with it and the change is written down on our status page.
We do not use cookies
Not one, anywhere on this site.
No cookies, no tracking pixels, no advertising network, no analytics that follows you, no fingerprinting. That is why you are not reading this through a consent banner: there is nothing to consent to. We would rather earn the trust than ask for it in a popup.
If we ever add something that needs your permission, you will be asked before it runs, and the change will be logged publicly like every other change we make.
What we collect, and only this
Nothing about you if you are only reading. Two things do happen when one of these pages opens, and this is all of them:
- A page-view counter. Cloudflare, which serves these pages, adds a small script that counts page views for us. We see only totals: which pages were opened, which sites sent people here, how fast the pages loaded, and the countries, browsers, operating systems and kinds of device they were opened on. It sets no cookie, stores nothing in your browser and does not follow you to other sites, and Cloudflare throws your internet address away instead of keeping it. Visits that reach Cloudflare in the EU, the UK, Switzerland, Norway, Iceland or Liechtenstein are left out of the count.
- Slack's button picture. The Add to Slack button on the front page is Slack's own picture, so your browser fetches it from Slack's servers. Like any download, that shows Slack your internet address, your browser and its language setting, and that the page was on statuspost.org; Slack's own privacy policy, not ours, covers what Slack does with that.
The list below begins when you connect StatusPost or ask us to watch a site.
| What | Why we need it | How long |
|---|---|---|
| Your email address | It is where we write when something on your site needs your attention. If you added StatusPost to Slack, it is the address Slack holds for you. If your organization uses StatusPost from an AI assistant, it is also how you sign in there, with a code we email you. There is no password, so there is nothing else to remember or leak. | Until you ask us to delete it |
| The web addresses you ask us to watch | We cannot watch a page without knowing where it is. | Until you delete the organization. If you only stop watching a page, its address stays on record with the readings already taken |
| What we saw when we looked | The answer each address gave, how long it took, and whether it matched. This is the product: without it there is no status page and no alert. | Every reading for 30 days. After that the individual readings are deleted and one line a day survives: how many times we looked and how many were clean. That daily line is kept so your history does not vanish. |
| Your organization's name | So your status page says who it belongs to. | Until you ask us to delete it |
| Your Slack workspace and channel, if you install the Slack app | The workspace and channel you chose at install, the address Slack gave us for posting into that channel, and the email address of the person who installed it, who becomes the organization's first member. That is how alerts reach the channel and how we know who looks after the organization. Slack sends the app every message posted in that channel. The app acts only on commands, on mentions, on replies in threads, and on two reactions on its own alerts. To tell whether a thread is one of its own it asks Slack for that thread's messages and looks only at who sent them; every other message is dropped at once and never stored. What you ask the app and what it answers, including a question typed in plain words, is kept for ninety days, so we can see where it fails people and fix it; then it is deleted, whether or not anyone has used the app since. An idea you send through the app is kept with your organization's name; your email address and Slack user id on it are removed after ninety days. When a member claims an interruption with a reaction, a button or a word, that member's Slack user id is kept on the interruption and removed ninety days after it closes. Nothing else from the channel is kept. | Until you remove the app from Slack, or delete the organization. Slack tells us when the app is removed and we forget the channel the same minute. |
What we never do
- We never sell anything about you, or share it with an advertiser. There is no advertiser.
- We never ask for a password to your website, your donation platform, or anything else. The checks work from the outside, the way a visitor sees you.
- We never change anything on your site. StatusPost reports what it finds and hands you the fix; it does not reach in and touch your systems.
- We never publish a check you have hidden. Hiding a check hides it from your public page; it keeps running, one that alerts still alerts you, and any advice still comes in the Sunday note.
Who else touches it
Only the companies that make the service run, and only for that purpose:
- Cloudflare serves these pages, counts their page views, and runs the checks.
- Supabase stores the readings and handles the sign-in codes.
- Google Workspace carries our email.
- OpenAI and Anthropic, reached through Cloudflare's AI Gateway, write the one paragraph in an alert that says what is likely causing an outage. They are sent only the facts of the outage: the address we watch, what it answered, its recent record, and the state of the organization's other watched addresses. When a member asks the Slack app a question in plain words, that question is sent to them too, as typed, together with those facts, so the answer can address it; do not put personal details in a question. Nothing else about you as a person, not even your email address, is sent to them.
Each of them is a processor acting on our instructions, not a party we sell to.
What you can ask us for
Whether or not the law where you live requires it, you can ask us to:
- tell you everything we hold about you,
- correct anything wrong,
- delete it all and close the account,
- send you a copy in a file you can take elsewhere. For the copy, write to us and we send you a one-time link to it by email. If your organization uses StatusPost from an AI assistant, asking there (the export_organization tool) sends the same link by email within a minute.
Write to contact@statuspost.org and a person will answer. We do not require a particular form of words, and we do not charge for it.
Where we are
StatusPost is run by V2C, a 501(c)(3) nonprofit in the United States, and the data lives on servers in the United States. If you are in the UK or the European Union and you are unhappy with how we have handled something, you can complain to your national data protection authority, and you can write to us first at the address above.
If something goes wrong
If your information is ever exposed, we will tell you what happened, when, and what we did about it, on the status page and by email. That is the same promise we make about our own outages, and it is written down for the same reason: a service that hides its mistakes is not worth trusting with yours.