We ask for very little, and we say why every time.
This is a money product, so most of what we hold is either an identity check or a payment record. Nothing here is collected because it might be useful later.
Last updated 30 July 2026. This policy describes the pilot. If it changes materially we will say so on this page and tell anyone with an open project.
Four sentences, then the detail.
- We collect what is needed to verify who someone is, move money to the right account, and keep a record of a project that both sides can rely on years later.
- We do not sell personal data, we do not share it for advertising, and we have no advertising business that would give us a reason to.
- A homeowner’s address, phone and payment details do not reach a contractor because a contractor asked — there is no way for them to ask.
- Financial records attached to a project outlive the project on purpose, because a lien waiver is worth nothing if we delete it the year you might need it.
Everything we hold, by who gives it to us.
- From a homeowner
- A mobile number, and a code we text to it. Your name. The address of the property being worked on, so we know which property the project covers, and whether you occupy it — because occupancy affects which state protections apply to your project. Answers to a small number of state questions of the same kind. Your bank details, which reach our payments provider rather than us. Messages you send on a project, your approvals and disputes, and any rating you leave at the end.
- From a contractor
- A mobile number and a code. Business name, EIN, licence number where the state issues one, insurance details, and the beneficial ownership information a payments provider is required to collect before it will move money to a business. A payout account. The quotes you write and the work you submit.
- From public and official records
- We check a contractor’s licence against the state board that issued it, confirm business registration, and screen both sides against sanctions lists — a legal requirement for anyone in the payments chain, not our curiosity. We check property ownership against the county record. We do not run consumer credit checks; where you choose to pay over time, the lender does, under their own agreement with you.
- From your use of the site
- This marketing site sets no advertising or analytics cookies and embeds no third-party trackers. It loads two font files from Google Fonts, which means Google sees the request. That is the only third party this site contacts, and we are looking at self-hosting the fonts to remove it.
Nothing on that list is there for marketing.
- The phone number
- It is the account. There is no password to steal or reuse, and a code sent to a number you hold is what stops someone else approving a payment in your name.
- The property address and occupancy
- Construction law is state law, and several of its protections turn on facts about the property rather than the price. We ask the smallest number of questions that change what the product does, and the app tells you which protection each one is about.
- Bank and ownership details
- Payment diversion is the most common fraud in construction payments, and the defence is checking that the account receiving the money belongs to the business that did the work. That check is the reason we ask a contractor for ownership information, and the reason changing a payout account is treated as a security event rather than a settings change.
- The project record
- Approvals, releases, disputes and waivers form the file that proves what was agreed and what was paid. That file is the product. It is also the thing a homeowner needs if a subcontractor turns up years later claiming they were never paid.
Some of these are promises. One of them is architecture.
We do not sell your data
Not to advertisers, not to lead brokers, not to anyone building a list of people about to spend money on their house. Texas law bars the sale of sensitive personal data without consent regardless of how small a business is, and we would not do it in any case — a product whose whole claim is that it protects you cannot also be selling you.
Contractors cannot look homeowners up
This is not a policy we could quietly change; there is no homeowner directory to search. Lookup runs one direction only, because a search that finds homeowners by address is a tool for opening payment requests against strangers. A homeowner reaches a contractor. Never the reverse.
A contractor can text you a quote link, and that is not a hole in this. They have your number because you gave it to them, not because they found you here. And we don’t send that message — it opens their own phone’s messages, so it reaches you from their number. We never text anyone who hasn’t asked to hear from us, and your number isn’t stored here unless you open the quote and decide to go ahead.
We do not use your project to train anything
Your messages, documents and disputes are not training data, ours or anyone else’s.
Longer than you might expect, for a reason.
A closeout package, a signed waiver and a payment record are evidence. Deleting them promptly would feel privacy-respecting and would leave a homeowner unable to prove they paid when someone claims otherwise — and lien and contract limitation periods run for years after the work is done. So project financial records are kept for as long as they could plausibly be needed, and payment records are kept as long as financial and tax rules require.
What does not need to persist, does not. An expired invite code is gone. Verification material we were required to collect but do not need to keep is not kept. If you close an account with no project attached, there is very little left to hold.
What you can ask for, and the honest position on which law applies.
- What you can ask us to do
- Ask what we hold about you and get a copy. Correct anything wrong. Ask us to delete what we are not required to keep. Object to something we are doing. We will answer within 45 days, and tell you plainly when a legal obligation stops us doing what you asked.
- Which law gives you those rights — the honest answer
- Utah’s Consumer Privacy Act applies to businesses above $25 million in revenue handling data on 100,000 people; we are nowhere near either. Texas’s Data Privacy and Security Act exempts small businesses from most of its obligations. Neither of them currently compels the rights above from a company our size. We are offering them anyway, because the size of the company is a poor reason for you to have fewer rights, and because we would rather build the process now than retrofit it at the threshold.
- Financial privacy law does apply
- Handling money for consumers brings federal financial privacy and safeguarding obligations with it, and those do not have a small-business exemption. Where a formal financial privacy notice is required, you will receive one when your account is opened rather than being pointed at a web page.
- How to ask
- Write to privacy@projectcomplete.app. A real person reads it. During a pilot this small, that person is one of the founders.
What protects it.
Card numbers are not accepted anywhere in the product, which removes an entire category of risk rather than defending it. Bank credentials go to our payments provider rather than being stored by us. Accounts have no password to phish. A payout account locks at verification, and changing one re-runs the checks, freezes payouts briefly and notifies every open project — because that change is what payment diversion looks like.
We are building the formal written security programme that federal law requires of anyone safeguarding consumer financial information. It is not finished. Saying so is more useful to you than a paragraph implying it is.
The parts of this we have not finished.
- The formal written information security programme is in progress, not complete.
- Fonts on this site are loaded from Google, which is one third party more than we want. Self-hosting is a small job we have not done.
- A contractor has no right of reply to a rating yet. Publishing what a homeowner says about a named business without letting them answer is not a position we intend to keep.
- An independent security review has not happened. It is a requirement for the partner-bank migration, so it will.
This page describes a pilot product. It is written to be accurate about what exists today rather than about what we intend to build, and it will be reviewed by counsel before the pilot opens to people who are not already talking to us.