Privacy Policy of the Chrome extension “StatusEye Pulse”

1. In short

• The Extension works inside your browser. Without an action from you it sends nothing to StatusEye.
• Only a site name (for example, example.ru) is sent to StatusEye, and only when you press the “Check SSL and domain” button yourself.
• The Extension has no analytics, no ads and no trackers. Your data is not sold or passed to third parties.
• No sign-up or account is needed.

2. Who is responsible

2.1. The Extension and the StatusEye service are run by the same owner. The owner’s details are given in the service privacy policy (in Russian).

2.2. Contact: info@statuseye.ru, Telegram @StatusEyeSupport_bot.

3. What stays in your browser

3.1. For every page you open, the Extension sees the technical loading data that Chrome shows to extensions:

• the page address and the chain of redirects;
• the response code and the server response time;
• the IP address Chrome connected to (when you use a proxy, this is the proxy address);
• load errors of images, scripts and other files of the page;
• details of the site certificate, if Chrome provides them.

3.2. The Extension does not read page text, form fields, passwords, cookies or request headers.

3.3. This data is used to draw the badge and the card. It is kept in the temporary memory of the browser (chrome.storage.session) and is erased when you close the tab or the browser. It is not sent anywhere.

4. Domain expiry: public registries

4.1. When you open a site card, the Extension asks the public RDAP service of the domain registry for the domain registration date. The request goes straight from your browser and contains only the domain name of the site, without path or parameters.

4.2. The Extension gets the list of RDAP services from IANA (data.iana.org). Registries and IANA are independent organisations: they see your IP address and this domain name and handle it under their own rules.

4.3. The registry answer is saved in your browser (chrome.storage.local) and refreshed after 24 hours. It does not leave your computer.

5. “My sites”

5.1. You build the “My sites” list yourself with the “Watch this site” button. It is stored only in your browser (chrome.storage.local) and is not sent to StatusEye.

5.2. While the browser is open, the Extension itself regularly visits these sites from your computer and your IP address (without cookies) and stores the result on your device. The owner of such a site will see these requests in their logs.

5.3. Problem notifications are optional: Chrome asks for permission separately. Without it the Extension shows a red dot on the icon.

5.4. The Extension works only while the browser is open. If the browser is closed, there are no checks and you will not learn about an outage. For round-the-clock checks there is the separate StatusEye service, which you may connect if you wish.

6. The StatusEye request on a button

6.1. If Chrome did not show the certificate expiry date, or the domain is in the .ru, .su or .рф zone (they have no public RDAP service), the card shows the “Check SSL and domain” button. Until you press it, nothing is sent to StatusEye.

6.2. After you press it, one request with one value goes to the StatusEye server: the site name (for example, example.ru). No path, parameters, cookies, account data or browsing history.

6.3. The server connects to this site itself, reads the certificate expiry date and, for the .ru, .su and .рф zones, asks the public whois service for the domain expiry date. Then it returns the dates to you.

6.4. The site name is not written to the database or to application logs. It sits briefly in the server memory so that a repeated request does not load other servers: up to 6 hours for the certificate and up to a day for the domain, and it disappears on restart. As with any website, the web server technical logs keep the IP address, the time and the address of the request itself, but not the name of your site, because it travels inside the request. The number of requests per IP address is counted in memory to protect the service from overload.

6.5. The request is answered by the StatusEye server at statuseye.ru. It passes the site name nowhere else, except to the site you are checking and, for the .ru, .su and .рф zones, the public whois service.

7. What we never do

• We do not collect analytics, usage statistics or information about your visits.
• We do not show ads and do not embed third-party scripts or counters.
• We do not sell or pass data to third parties and do not use it for anything except the functions described here.
• We do not download or run code from the internet: all the code of the Extension is inside it.

The use of information received through Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

8. Why the permissions are needed

• Access to all sites: to show the response code and loading data on any page you open, and to check the sites you have added.
• webRequest, webNavigation: to learn the response code, the redirect chain, the timing and the load errors.
• storage: to keep the temporary tab data and your “My sites” list.
• alarms: to wake the Extension for regular checks of “My sites”.
• notifications (optional): to tell you about a problem with a site. It is requested only when you turn notifications on.

9. How to delete your data

9.1. Everything the Extension stores is in your browser. You can remove a site from the “My sites” list itself, and all the data of the Extension disappears when you remove it from Chrome.

9.2. StatusEye stores nothing about this Extension: the site name from the button request is not saved anywhere (see 6.4), so there is nothing to delete. Send questions about your data to info@statuseye.ru.

10. Changes and contact

10.1. If this policy changes, we will update the effective date at the top of this page and publish the new version at the same address. By continuing to use the Extension after an update, you accept the current version of the document.

10.2. Questions and requests: info@statuseye.ru or Telegram @StatusEyeSupport_bot.