Security and privacy¶
What we keep about the sites you watch, who in your team can see it, and what our checks send to your websites and servers.
Your account's data¶
Every monitor, group, window and alert belongs to one account. Nobody in another account can see it, and two accounts that watch the same website each have their own monitor, with nothing shared between them. Inside your account, what a person can see and change depends on their role (who can do what).
Saved passwords¶
A website's Basic Auth user name and password, saved under Basic Auth in a monitor's Settings, are kept encrypted. The password is never shown in a page as it loads:
- Owners and Admins see it as dots, with an eye beside it. Clicking the eye shows it, and each time the account's history records who looked, never the password itself (Basic Auth).
- Members and Viewers see the user name and Password saved, never the password.
- During a support visit, when one of our team opens your account to help you, the password stays hidden: the page shows the dots and Hidden during a support visit. in place of the eye.
When a monitor's address moves to another domain name, its saved password is removed, so it is never sent to a site it was not given for (address).
What our checks send to a website¶
Each check of a website is one ordinary request, as a browser would make, with no cookies and nothing typed in:
- The method you chose under More settings:
GET(the default), which reads the page, orHEAD, which only asks for its headers (more settings). - The user agent
Mozilla/5.0 (compatible; UptimeGorilla/0.1; +https://uptimegorilla.com), so your logs and your firewall can tell our checks from visitors (allow our checks). - The Basic Auth password, only when one is saved, only over
https://, only once the website's certificate is accepted, and only to the same host and port. It is never sent overhttp://, nor to another host a redirect leads to. With the Basic Auth warning on, each check first asks without it.
We read at most the first megabyte of a page and follow at most 5 redirects. We never run the page's scripts, never submit a form and never sign in.
What our checks send to a port¶
A port monitor only connects to the port and, where the service speaks first, reads its first line. We send it nothing: we do not log in, send mail or type a command. On a database port we only connect: we never log in or send a query.
Where the checks come from¶
From our own checking servers, whose names and addresses are listed on allow our checks. Each check comes from one of them at a time, so your website gets one visit per check interval (read the last result). Private and internal addresses are never checked: a monitor whose address leads to one shows Private or internal address.
Alert emails¶
Each alert email goes to one address at a time: nobody sees who else got it. No alert email goes to an address nobody has confirmed: not your account's alert email while it is a sign-in email not confirmed yet, and not an address added to a group until its owner confirms it, and its owner can stop the emails with one click (confirm an address, stop the emails). A group's emails never name your servers or your other addresses.