Privacy policy

The status history of the services it monitors — counts of how many checks of each provider succeeded on each day, and recent response times. Those records describe GitHub and Cloudflare, not visitors, and they are identical no matter who is looking.

The one other thing kept here is the community report counter described below, which is a tally and not a record of people.

There is no account system, no login, no profile, and no mailing list.

Each service page asks whether that service is down for you. Answering it stores one number: a running count, per service and per hour, of how many people said down and how many said working. There is no message box, so nothing you write is published, because there is nothing to write. You can change your answer until the hour is out; after that it is only part of a total.

Those counts are kept for 24 hours and then expire. What is published is a total, never a list of who said what.

To keep one browser to one report per service per hour — and to let you change that report if you clicked the wrong button — isuptime stores your answer for the rest of that hour against a one-way hash of your IP address and browser user-agent, salted with a value that changes every hour. The hash cannot be turned back into an IP address, it is different for you next hour, and it is deleted at the end of the hour it was made for, before the counts it belongs to. Your own browser also remembers which services you reported this hour, under sv-reports, so the buttons show what you said.

Community reports never change the status isuptime publishes. The status on every page comes from the provider's own feed, and votes are shown beside it, clearly labelled, so that a green feed and a room full of people who cannot log in are both visible for what they are.

Your preferences stay on your device, in your browser's local storage. They are never transmitted to isuptime:

• sv-theme — whether you chose light or dark mode.
• sv-levels — the last status seen for each service, used to detect when something has just changed.
• sv-notify — your alert settings, including any Discord, Slack or Telegram webhook you enter. Because these stay in your browser, clearing site data deletes them, and they do not follow you to another device.

If you enable browser notifications, that permission is granted to your browser directly and can be revoked there at any time.

If you send a message through the contact form, the message and any reply address you choose to include are sent on as an email so they can be read and answered. Delivery is handled by Resend, an email provider who processes the message in order to deliver it. Nothing is written to a database here, and what you send is not used for anything other than replying to you. Please do not send sensitive information through it.

Like any website, the hosting platform records standard request logs, and isuptime briefly holds request counts in memory to rate-limit the alert and contact endpoints so they cannot be abused to flood someone else's channel. IP addresses used for that purpose are held only for the length of the rate-limit window, are not written to disk by this site, and are not linked to anything else.

isuptime links out to each provider's own status page and incident reports. Once you follow one of those links you are on that company's site, under their privacy policy, not this one.

isuptime does not currently display advertising. If that changes, this page will be updated before any ads appear, and it will name the advertising provider and explain the cookies it uses.

This is a technical tool aimed at developers and other professionals. It is not directed at children, and it does not knowingly collect information from them.

Because isuptime holds no personal data of its own, there is no account to delete and no export to request from it. To remove everything this site has put on your device, clear its site data in your browser.

If this policy changes, the date at the top of the page changes with it. Material changes — new categories of data, or a new third party receiving it — will be described here rather than made quietly.

Questions about this policy can be sent through the contact page. The rules for using the site itself are in the terms of service.