Flows
Subprocessors and network flows: no external calls by default
Where do your photos and data go? Nowhere other than your servers and your inventory tool. Here is the list of flows, and how to check it yourself.

Contents
In a security questionnaire, two questions always come up: where does the data go, and which third parties process it? For the platform, the answer fits in a few lines. This page details it and shows you how to check it on your own installation.
No external calls by default
The platform is installed as containers on your servers, and the analysis engine runs on site. No online service is required to analyze a photo: not to locate the equipment, not to compare it with the inventory, not to check the license.
By default, the platform therefore makes no calls to the Internet. It can run on a network with no outbound access, which is common in sensitive operational environments.
The list of flows
Exchanges are limited to these:
| Source | Destination | Purpose |
|---|---|---|
| User’s computer or phone | Platform interface | Sign-in, sending photos, viewing |
| Interface | Analysis engine (internal) | Photo analysis |
| Comparison (internal) | Inventory connector | Reading the rack’s inventory |
| Inventory connector | Your inventory tool | Reading, then writing after approval |
The only flow leaving the installation is the one from the connector to your inventory tool, which is also on your infrastructure. It uses the token of a dedicated, non-administrator account in your inventory tool, created at installation with limited rights: reading the inventory, writing restricted to the objects the platform updates. In the standalone version, without an inventory, this flow does not exist.
Check it yourself: the System page
The platform’s System page shows the services actually reached and their status: analysis engine, label reading, inventory connector. Your teams can compare it with the list above, and check it against what your own network filtering and monitoring tools observe.
We also recommend blocking, at your firewall, any outbound flow from the installation other than the one to your inventory tool. The platform does not need it to work.
Subprocessors: what this changes
The platform does not pass your photos to a third party. Photos, surveys, comparisons and logs stay on your servers; no outside service is involved in processing them.
This simplifies your record of processing activities and your impact assessments: because of the platform, there is no data flow to an outside hosting or computing provider. Aspects related to personal data that may be visible in photos are covered on the page GDPR and personal data.
Frequent questions from security teams
Does the platform need Internet access to work? No. Neither photo analysis, nor comparison, nor license checking requires outbound access.
Do updates download on their own? No. Each release is handed over to you, and your team installs it; the signature is checked at that point.
Can the connector’s token be read-only? The installation needs to write to your inventory tool (fields and tags specific to the platform). After that, if you do not want to write from the platform, the dedicated account’s write rights can be removed: the comparison still works, and the inventory tool refuses writes. Writes, for their part, always wait for human approval.
Can the platform be installed on an isolated network? Yes. It is even the easiest configuration to justify: the only exchange needed, to your inventory tool, stays internal to your infrastructure, and the standalone version needs none. The way releases are handed over adapts to this case.
What about a demo?
For a demo on your own photos, before any purchase, we analyze a few images on an isolated instance dedicated to this purpose. The conditions (number of photos, retention period, deletion) are agreed with you beforehand. Request a demo.