Sub-processors

This page names the companies that process data on our behalf. It is referenced by the Privacy Policy and by the Mutual Confidentiality Agreement, and it describes the software build running in production on the date at the top of this page. We re-verify it against the deployed build when we release.

One limitation, stated because it is true and because you would find it anyway. A screening run reads public sources chosen while the run is happening — grid operator publications, planning and environmental registers, map and terrain services, meteorological datasets. Which hosts are contacted depends on the site and the questions asked. The table below names every company under contract that receives data on our behalf. It cannot name every public website the system reads during a run, and we describe those as a category rather than pretend to a closed list.

These receive project material: site geometry and coordinates, project type, requested capacity, and the questions and notes you wrote. They do not receive your name, your email address or your company name: those are not fields we put in the request. What you type is another matter, and we would rather say it than let you assume otherwise — a site name, a note, a question you ask, or the text of a document you upload is sent as you wrote it, and any of those can contain a person's or a company's name.

Report generation runs through a single routing provider, which passes each request to a model operator. The routing provider selects the upstream that serves a request, so the operator named below is the one it serves through today rather than a fixed guarantee. We list the routing provider and the operator that serves those requests. We check this against the production database rather than against our own documentation, and we re-check it when we release.

Training and retention. Our agreement with the routing provider prohibits retention of request content and prohibits training on it, and the same prohibition is passed to the model operator. The instruction is also applied technically on every request and re-applied on every retry. We can show you both the configuration and the signed agreement.

These receive site coordinates or the bounding box around them, in order to render maps and retrieve public datasets.

These receive personal data.

We give at least 15 days' notice before a new sub-processor begins processing customer data. Notice is given by email to account holders and by updating this page. If you object on reasonable data protection grounds within that period, write to [email protected]. If we cannot offer an alternative, you may terminate the affected part of the Service without penalty for the remainder of the term.

Our data processing agreement with you, which names these companies as authorised sub-processors and carries your right to object to a new one, is available from [email protected]. A company appears on this list when it is live in the deployed build, and we re-verify the list against that build at each release.