PLCGateway Monitor – Privacy Policy
In short: PLCGateway Monitor does not collect, sell or share any personal data. It has no analytics, no advertising and no tracking. It communicates only with the PLCGateway servers that you add yourself, and everything it stores stays in your browser.
1. What the extension does
PLCGateway Monitor shows the alarms, production figures (OEE) and live values of your own PLCGateway Connect, SCADA or Embedded servers in the Chrome toolbar, notifies you about new alarms and opens the screens of those servers. It is published by PLCGateway (plcgateway.com).
2. Information the extension handles
| Information | Why | Where it is kept |
|---|---|---|
| Name and address of each server you add | To connect to your PLCGateway servers | In your browser (Chrome local extension storage) |
| Session token after you sign in, or the API token you enter | To authenticate requests to your server | In your browser (Chrome local extension storage) |
| Your user name and password | Sent once to your own server to sign in | Not stored |
| Pinned tags, notification and check-interval settings | To show the values you chose and to remember your settings | In your browser (Chrome local extension storage) |
| The latest alarm status of your servers | To update the badge and detect new alarms | In your browser (session storage, cleared when Chrome closes) |
Alarms, values, OEE figures and screen lists are read from your servers when needed and are not stored beyond the latest alarm status listed above.
3. Where data is sent
- The extension sends requests only to the PLCGateway servers you add, at the addresses you enter, to read alarms, values, production figures and screens, and to acknowledge alarms when you choose to.
- No data is sent to the developer of the extension, to PLCGateway or to any third party.
- The extension does not use cookies of your PLCGateway session in the browser, does not read your browsing history and does not access any other website.
- We recommend using HTTPS addresses or a protected network (for example a VPN) for servers reached over the internet.
4. Permissions
- storage – keeps your server list, tokens and settings in your browser.
- alarms – checks your servers for new alarms at the interval you choose (30 seconds to 5 minutes).
- notifications – shows desktop notifications for new alarms, filtered by the priority you select.
- Access to a server address – requested only when you add a server, only for that address, and removed when you remove the server.
The extension contains all of its code in the package; it does not download or run remote code.
5. Keeping and deleting data
Data stays in your browser until you remove it. Removing a server in the extension's settings deletes its address, token and pinned tags and gives back the access permission for that address. Uninstalling the extension deletes all of its data. A session token also stops working when your server ends the session (after 12 hours); an API token stops working when it is regenerated on the server.
6. Your PLCGateway servers
Your PLCGateway servers are operated by you or your organisation. What they record (for example which user acknowledged an alarm) is governed by your organisation's own policies, not by this extension.
7. Chrome Web Store User Data Policy
The use of information by this extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the extension's single purpose described above; it is not sold, not used for advertising and not transferred to anyone.
8. Children
The extension is a tool for industrial users and is not directed at children.
9. Changes
If this policy changes, the new version will be published on this page with a new date. Changes that would collect or share data would only be made with your consent.
10. Contact
PLCGateway – [email protected] – plcgateway.com