| Quick facts | |
|---|---|
| API terms on AI training | API terms prohibit AI training[1] |
| Does Procore train on your data? | Not reviewed |
| Recommended export path | The Procore Extracts desktop application archives a project’s data by tool into a local folder.[2] |
| Connector risk | High — the API terms expressly cover AI training and bulk export. |
Section 1
What Procore holds that AI buyers value
- Projects and directories
- RFIs, submittals and change orders
- Daily logs and inspections
- Drawings, specifications and photos
- Budgets, commitments and invoices
Where the value is: Construction decision trails — RFIs, submittals and change orders tied to drawings and costs — are a rare record of professional judgment in the field.
Section 2
How to export your Procore data
The Procore Extracts desktop application archives a project’s data by tool into a local folder.[2]
- Install Procore Extracts on an administrator’s machine.
- Extract each completed project in scope.
- Confirm which project data belongs to your company versus owners, architects and subcontractors before licensing.
Keep a note of who ran each export, when, and with what filters. It is the first page of the documentation file a buyer — and later an acquirer — will ask for.
Section 3
What Procore’s API terms say about AI
API Terms and Conditions (version dated 2025-09-30): Developers may not use API Data to train, re-train, fine-tune or benchmark ML/AI, or bulk export API Data without an additional agreement.[1]
“use API Data to train, re-train, fine-tune or benchmark any machine learning or artificial intelligence algorithm, software, or system”
This is the clause that decides how a buyer may collect. A buyer that asks you to install its app or authorize a connector to Procore is collecting through the API — the route the terms restrict. Your own administrator export is governed by your customer agreement instead, which your counsel should read before anything is licensed.
Section 4
Does Procore train AI on your data?
We did not review Procore’s own AI-training practices in this research pass. Ask the vendor, and check your account’s AI or privacy settings — a buyer will ask whether the same data has already been used to train someone else’s models.
Section 5
Fields to scrub before licensing
- Project directories (names, emails, phones of many companies)
- Site photos showing workers
- Owner and client contract terms
Removing names is not de-identification; combinations of quasi-identifiers re-identify people.[3] California’s statute sets the bar for a “deidentified” consumer record.[4] Test a sample with the browser-local PII scanner before anyone else sees it.
Section 6
Check the rest of your stack
Most licensable files span several systems. The software AI data rights checker lists the API clause, vendor-training position and export path for every system we have reviewed, and the SaaS AI data ownership index publishes the same findings as a downloadable dataset.
Frequently asked questions
Can I sell my Procore data to AI companies?
How do I export all my data from Procore?
Does Procore use my data to train AI?
References
Sourced from primary industry reports, government data, SEC filings, and peer-reviewed valuation research. Retrieved at time of publication.
- 1.Procore Technologies, Inc. — API Terms and Conditions — Effective 30 September 2025; bars training or benchmarking ML/AI on API Data and bulk export without an additional agreement (2025)
- 2.Procore Technologies, Inc. — Extract Project Data Using Procore Extracts — Desktop application that archives a project’s data by tool into a local folder
- 3.U.S. National Institute of Standards and Technology — NISTIR 8053 — De-Identification of Personal Information — Reference treatment of de-identification techniques and re-identification risk (2015)
- 4.State of California — California Consumer Privacy Act, Civil Code § 1798.140 — definitions of "deidentified" and "sale" — Statutory standard a de-identified operational record must meet, and the breadth of "sale"