BuildMetrx · last updated October 19, 2026
BuildMetrx is a cost-intelligence system for construction companies. A company signs up, its people upload or connect the sources of its vendor bills, and BuildMetrx turns them into cost data the company uses to run its jobs.
This policy covers the data BuildMetrx handles for a company that uses it. It is written for the company and the people it authorizes.
Account data: names, email addresses and roles of the people a company adds.
Business records the company brings in: vendor invoices and receipts (files and the data read from them), vendors, customers and projects, jobs, budgets, schedules, timesheets, purchase orders, payments and contracts.
Accounting data, when a company connects an accounting system such as QuickBooks Online: vendors, customers and projects, bills, expenses, bill payments and the files attached to them. BuildMetrx reads this data; it never writes to the accounting system.
Time clock data, when a company uses the time clock: each worker's name and contact details, clock-in and clock-out times, the location of the device at each punch, and a photo taken at each punch. When the company turns face matching on and the worker agrees in writing, a numeric face template is also made from the worker's approved photo. The company's own photo and face policy, shown to every worker before they enroll, says how long these are kept and how they are destroyed.
Mailbox data, when a person connects a mailbox so vendor invoices arrive by email: BuildMetrx has read-only access. It looks at the sender, subject and attachments of incoming messages to find vendor invoices and imports the attachments of the messages that match. It does not send, change or delete mail, and it does not use mailbox data for anything else.
Email sent to a company's own invoice address (an address ending in in.buildmetrx.com that the company creates and gives to its vendors): the email is received by Resend, which keeps it for up to 30 days. BuildMetrx keeps the sender, the subject and the attached files and never the body. A file from a sender the company trusts becomes an invoice like any upload; a file from a sender nobody at the company has accepted is held for up to 30 days until a person accepts or ignores it, then removed.
Usage data: sign-ins, pages opened and errors, kept to run and support the service.
If the in-app helper is turned on for your login, what you write to it and its replies are stored and may be read by BuildMetrx staff to improve the product and to answer your feedback. The helper only knows how BuildMetrx works; it does not read your company's records, and it never changes anything.
Helper conversations are kept for 180 days, then deleted.
To provide the service to the company that owns the data: reading invoices, building cost reports, comparing prices, forecasting cash and everything else the product does.
Documents are read by automated systems (including third-party AI services) to extract their line items. Those services process the document to answer the request and are not permitted to use it to train their models.
We do not sell data. We do not share a company's data with other companies. Aggregated, de-identified statistics may be used to improve the product.
Our own staff open a company's account only to set it up or to support it, and each such session is recorded.
We use a small number of providers to run BuildMetrx. Each one handles data only to provide its part of the service.
Hosting and database: Supabase, on Amazon Web Services, in the United States. Network and application delivery: Cloudflare. Reading documents: Anthropic. Sending sign-in codes and notices by email, and receiving email sent to a company's invoice address: Resend.
Face matching, only for a company that has turned it on: Amazon Web Services (Amazon Rekognition).
Connections a company or a person chooses to make: Microsoft or Google for a connected mailbox, and Intuit for QuickBooks Online. When a person asks BuildMetrx to find a job-site address on the map, that address is sent to OpenStreetMap.
A company's owner or administrator connects an accounting system through that system's own sign-in and consent screen. BuildMetrx stores the resulting access credentials encrypted and uses them only to read the data listed above.
The company can disconnect at any time from its Settings page. Disconnecting revokes BuildMetrx's access at the accounting system and deletes the stored credentials. Data already imported stays in BuildMetrx as the company's own records unless the company deletes it.
Data is stored with our hosting providers in the United States, encrypted in transit and at rest. Access inside BuildMetrx is limited to the company that owns the data, enforced at the database level, and to the people that company authorizes.
Secrets such as accounting credentials and third-party keys are encrypted with keys that are never stored beside the data.
Sign-in takes a second step — a code sent by email — on any browser we have not seen before. The database is backed up every day.
If we learn that a company's data was reached by someone who should not have had it, we tell the company's owner promptly — and in any case within the time the law requires — with what we know and what we are doing about it.
BuildMetrx uses only the cookies the product needs to work: one that keeps you signed in, one that remembers a browser you have already verified, and ones that remember display choices such as light or dark mode. We do not use advertising or third-party tracking cookies.
A company's data is kept while it uses BuildMetrx. A company can delete its records from inside the product, and can ask us to delete its account and everything in it; we complete such requests within 30 days, except where a record must be kept to meet a legal obligation. Copies held in our backups are overwritten on the backup schedule.
Questions, access requests and deletion requests go to the company's owner in BuildMetrx or to us at the address on the sign-in page. We answer within 30 days.
A worker with a question about the time clock should ask their employer first: the employer decides how the time clock is used, and can correct or delete a worker's records.
We will post changes to this policy here, with the date above updated.