Sub-processors

Last updated 26 August 2026

These are the companies that process data on our behalf when you use Machinae Build. It is the whole list, not a sample. If you are a builder embedding the configurator in your own website, this is the list you are entitled to before you point your customers at it — you are the controller of their data, we process it on your instructions, and these are the people we use to do it.

The one worth reading first

What you type into the configurator is sent to a model provider. The description of a building is what the model turns into a design, so it leaves our servers by necessity rather than by choice. That text is written by a person, and people put addresses in it — “a shop behind the house on Elm Street”. We do not send your email address, phone number or password with it, and we do not send your account identifier; what goes is the description and the design being edited.

Who	What they do for us	What reaches them	When
DeepSeek	Generates a building specification from a written description, and answers design-edit requests.	The text you type and the design being edited. No name, email, phone or account identifier.	Every generation and every edit. This is the deployment's configured model provider; the current model is reported at `/health`.
Railway	Runs the application and stores its database and file volume.	Everything the service holds, because it is where the service runs.	Always.
Resend	Delivers our transactional email — sign-up confirmation, receipts, notices.	Your email address and the message we send you.	When we send you an email. A deployment configured with its own SMTP server uses that instead, and then this row is that provider.
Lemon Squeezy	Takes payment and issues receipts, as merchant of record.	What you enter at checkout, and the order it produces. Card details reach them and never us.	When you buy something.
HubSpot	Holds sales enquiries so that somebody can follow one up.	The contact details and design interest on an enquiry.	Only for enquiries made on our own site. An enquiry made inside a builder's embedded configurator is never sent here — it belongs to that builder and goes to their destination.
Google Analytics	Counts page views, so we can tell which pages are worth keeping.	Which page, when, roughly where from, and which page sent you. Your IP is truncated before storage.	Only on our own pages, and only if you said yes to the cookie notice. It is never loaded inside an embedded configurator — see below.
ipapi.co	Turns an IP address into an approximate location, so a quote can prefill the build site.	Your IP address, sent by your browser to them rather than by us.	Only if you said yes to the cookie notice. Off by default, and no answer means no.
Google, GitHub	Confirm who you are when you choose to sign in with them.	Only what you authorise at their sign-in screen.	Only if you use that sign-in button.

Inside a builder's website, two of these do not apply

Analytics never loads in the frame. A visitor of a builder's website sits under that builder's consent regime, not ours — they never saw our cookie notice and never answered it. The configurator refuses to load an analytics tag when it is embedded, and there is no setting that turns that refusal off.

Enquiries do not enter our CRM. An enquiry captured inside a builder's configurator is held against that builder, delivered where they tell us to deliver it, kept for as long as they instruct, and erased when they say so. It does not go to our sales team, because an export cannot be undone by a later deletion.

Changes to this list

The date at the top of this page changes when the list does. A builder with a data processing agreement in place is notified through the contact details on that agreement before a new sub-processor starts handling their data.

Where else to look

Data Processing Agreement is what governs the enquiries an embedded configurator captures — whose they are, how long we hold them, and what an erasure can and cannot reach. Privacy Policy covers what we collect and why. Cookies lists every cookie by name, including the partitioned one used inside an embedded configurator. Contact is where a data question goes.