Privacy

What we collect

Three separate things, kept separate. The public marketing site collects the least; the product collects what it needs to do the job you hired it for.

• On the public site — Aggregate page-view counts, and nothing else. No cookies are set, no profile is built, and nothing you do here follows you to another site. The full detail — including exactly what the request contains — is on the analytics page.
• When you have an account — Your email address, and a session cookie that keeps you signed in. That cookie is strictly necessary: without it there is no way to know the browser asking for your project data is you.
• Your project data — Whatever you connect or upload: Procore records your Procore account can already see, and documents you upload directly. This is the substance of the product and it is the part we treat most carefully.

Connecting Procore

Connecting Procore is something you do deliberately, through Procore's own authorisation screen. We never ask for your Procore password and never receive it.

What we receive is an access token, which we store encrypted. It grants us the same view your own Procore account has — no more. Disconnecting from the settings screen revokes it. We do not write to Procore.

Documents you upload

An uploaded document is quarantined on arrival and read in an isolated process that has no network access at all. That is a deliberate structural decision, not a policy one: the stage that opens an untrusted file physically cannot send it anywhere.

When a document needs to be interpreted, only the narrow, located portion of it is sent to the language model — not the file, not the whole document. That excerpt is sent as data to be read, never as instructions to be followed.

Extracted figures are never treated as authoritative until a human on your side reviews them. That is a product decision about trust, and it is also a privacy one: nothing derived from your documents is acted on automatically.

Who else touches your data

We use a small number of infrastructure providers. Each one is listed here because it can, in the course of doing its job, hold or transit your data. This list is a commitment: adding to it is a change we tell clients about, not a configuration detail.

• Vercel — Hosts the site and the application, and provides the aggregate page-view counting described on the analytics page.
• Supabase — Runs the database and authentication. Your project records live here, encrypted at rest, isolated per tenant at the database level rather than only in application code.
• Amazon Web Services (Bedrock) — Runs the language and embedding models. Inference is pinned to United States regions and to specific named models; we do not enable the multi-region inference profiles that would allow a request to be served outside that footprint. Today these calls reach AWS over its public endpoint rather than a private network connection — the controls are credential scoping and region pinning, and we would rather say so plainly than imply an isolation we have not yet built.
• Resend — Delivers email — sign-in links, invitations, and the weekly brief if you have opted into it. A brief contains summaries of your project conditions, so email is a real boundary; it is off by default and you can turn it off permanently from any message.
• Procore — Your own construction management system, connected at your instruction. Procore's handling of your data is governed by your agreement with Procore, not by this page.

What we do not do

This section is short on purpose. These are commitments, not aspirations.

• We do not sell personal information, and we do not share it with advertisers or data brokers.
• We do not run advertising or third-party marketing trackers on this site.
• We do not use your project data to train models for anyone else's benefit.
• We do not send your data to your general contractor, or to anyone else on the project, ever. The product exists to sit on one side of the table.

Your data, and getting rid of it

You can disconnect Procore, delete an uploaded document and its extracted records together, and turn off email at any time from within the product.

To ask what we hold about you, to correct it, or to have it deleted, write to hlaos@ownerrepai.com. We keep project data for as long as your account is active; when you ask us to delete it, we delete it rather than deactivating it.

Changes to this page

If we add an infrastructure provider that can hold your data, or change where inference runs, we will say so here and tell account holders — that is a change to a promise, not a change to a setting.