The four documents, what is in them, and what is still missing.
Everything that governs your use of FoundrySuite ships inside the download as files you can read, rather than as a page you have to keep asking us for. This page is the index to them, and it does not paper over the gaps.
Who is behind the product
The vendor
Project Foundry LLC, which is the party to the licence agreement, the controller named in the privacy notice, and the name in the footer of every page on this site.
How to reach us
One address serves support, licensing and data protection: info@project-foundry.net. Put “data protection” in the subject line for a data request and it reaches the right person rather than support.
Two facts we have not been given
Our registered postal address and the state we are formed in are still marked as gaps in the documents themselves. They are shown further down this page exactly as they appear in the documents, rather than filled in with something plausible.
The four documents
Each is a file in the download, written to be read rather than survived.
End User Licence Agreement
The contract. What the licence grants and restricts, that it is per workstation and not per user, that it is perpetual, and that replacing a machine does not require a new purchase. It also sets out what happens to your data, what we may and may not do with AI output, the warranty disclaimers, the limitation of liability, and the governing law.
File in the download: EULA.md. Sections a buyer usually wants: 1.1 the licence and the thirty-day trial, 1.2 the instalment plans, 1.3 moving to another machine, 4 your data, 5 AI features and model use.
Privacy Notice
What the software processes, what we process, and why there is no processor relationship for your business data. Section 1 names every outbound connection the software can make; section 3 names the controller for the data about you, the lawful basis for each item, how long it is kept, and your rights — including the right to complain to a supervisory authority and the one-month deadline we hold ourselves to.
File in the download: PRIVACY-NOTICE.md.
AI Facts Sheet
Written for a compliance officer rather than a lawyer. What the four AI features do, what is sent to a model and what is never sent, what the research feature puts on the wire, and the fact that we supply no model and host no weights — so the provider obligations for a general-purpose model do not sit with us.
File in the download: AI-FACTS-SHEET.md.
Compliance Notes
The engineering-side position: transport, session storage, tenant isolation, retention windows, and the AI disclosure record written for every model call. It also contains an honest list of what is still missing, which is the part worth reading first if you are doing a procurement review.
File in the download: COMPLIANCE.md, alongside a deployment guide for the network-access case, which is the one deployment where decisions are yours rather than defaults.
Where to read the behaviour rather than the paperwork
The security page describes what the software refuses to do, and the AI page describes what the model is permitted to touch. Both are written to be checked against the running product.
Who you are contracting with
Both documents open with the same contact block, and a procurement reviewer will read it before anything else. Here it is in full, so you do not have to take a PDF's word for it.
Project Foundry LLC
701 South St., Ste 100
Mountain Home, AR 72653
United States
This is the registered address in the EULA and the Privacy Notice — where formal notice and a data-subject request are served. The EULA is governed by the laws of the State of Arkansas.
Both of these facts used to be marked «FILL: …» in the documents themselves rather than guessed at. They are filled in now, and a test in the source checks that no unrecognised placeholder has appeared since — so a third gap cannot slip in unnoticed, and a filled one cannot be quietly left on the list as if it were still outstanding.
What that means for you
Nothing in these documents is provisional. The licence grant, the data terms, the AI terms, the governing law and the refusal list are complete as written.
If your procurement process needs something these documents do not say — a tax identifier, a signed W-9, a data-processing agreement, a security questionnaire — ask us and you will get a real answer from a person.
We kept those two facts marked rather than filling them with a plausible guess, because a wrong registered address in a contract is the kind of error nobody checks until it matters.
Questions these documents raise
Who is the data controller for my business data?
You are, not us. The privacy notice is explicit that we do not act as a processor on your behalf, because your data never reaches us — there is no server for it to arrive at. We are a controller only for the business data described in section 3: information about you and other people who contact us.
What happens to my data if I stop paying?
It stays where it is, in a format you can read without us. The EULA says a licence is not a subscription and does not need to be returned; uninstalling ends your right to use the software and creates no debt, and your right to use the data you produced does not terminate with it.
Do you host the AI model weights?
No, and saying so is not a hedge. The EULA states that you choose the model and we do not provide one; the AI facts sheet says the same; and the manifest shipped in the installer names the files the software looks for without, at present, publishing an address for any of them. Where no address is published nothing is fetched and the software reports the weights as absent.
Can I read these before I buy?
Ask and we will send them. They are also reproduced in full inside the download, which is the version you should hold on to — it is the one that shipped with the software you are running.