Wiresheet.ai station link

The extension has one purpose: to let the Wiresheet.ai web app read and change a Tridium Niagara station on your own network, from the computer that can reach it, without that station being exposed to the internet.

For each station you add, the extension keeps the address, the username and the password you enter. They are kept in this Chrome profile's extension storage on your computer. The extension does not encrypt them itself; they are protected the way other data your extensions keep is protected, by your computer account and your Chrome profile.

They are removed when you choose Forget for a station in the extension — which also withdraws the extension's permission to reach that address — or when you remove the extension from Chrome.

Only to the station addresses you enter. Chrome asks you to allow each address at the moment you add it; the extension is given no access to any site when it is installed.

At a station, it calls only the Wiresheet.ai module's own endpoints (/wiresheet/…) and two of Niagara's own: its file download, for a graphic you open and the pictures on it, and its palette, when you open the palette. Your username and password are sent to that station and to nothing else, over whichever of http or https the address you entered uses — prefer https:// where the station supports it.

The extension works only on app.wiresheet.ai. It does not run on, read or change any other site. On that page it passes messages between the page and the station, and marks the page so the page can tell whether the extension is present.

It gives the page the list of stations you have added — each one's identifier, address and username, never the password — and the station's answers to what you open: its components, values, graphics and their pictures, so that the page can show them to you.

Your station password never does. Nor, as a rule, does what the station sends back: the components, values, graphics and pictures you open are shown in your browser and are not sent on to us. There are three exceptions, and we would rather name them:

• A graphic's file, when you open it. The file and the station's Niagara version are sent to Wiresheet.ai so the page can show the default values of the widgets on it. They are used to answer that request and are not stored.
• The station's address, in the page address. A station opened through the extension has an identifier made from its network address — a station at 192.168.1.50 opens at /workspace/ext.192-168-1-50. Like any page address, it reaches our server when the page is opened, and may appear in routine web server request logs. It is not stored with your account.
• What the agent reads, when you ask it about the station. The Wiresheet.ai agent runs on our servers. When you ask it something about a station opened through the extension, each station call it makes during that turn is passed to your page, made through the extension, and its answer — the components, values, slots, tags, histories and palette entries it reads — is sent back to Wiresheet.ai, and from there to the AI model provider that runs the agent, which reads it to answer you. During a turn the extension is only asked to read and to check proposals without making them: nothing on the station changes until you apply a proposal yourself. The conversation, with what was read, is kept in our server's memory for up to an hour after its last turn so that a follow-up can carry on, and is not written to disk. What the station refuses when the agent checks a proposal is kept, as a short sentence, so that the agent does not repeat the mistake on that station — and so is what it learns of the station's component types, their inputs and outputs. Nothing is sent this way unless you ask the agent something.

• It contains no analytics, advertising or tracking code.
• It does not sell or rent the information it handles, passes it on only as described above, and does not use it for anything but the purpose above.
• It does not load or run code from outside the extension.

Wiresheet.ai's use of the information the extension handles complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

If what the extension keeps or sends changes, this page changes with it, and the date above moves. Questions go through our contact page.