Privacy Policy

Trench holds your unit prices and cost build-ups — the most commercially sensitive numbers in your business. We do not sell them, we do not pool them with other contractors’ numbers, and we do not use them to train anyone’s AI models, and we never use them to bid, price work, or compete with you. Nobody outside your company sees them except, in the narrow case section 3 describes, the engineers who keep the service running.

Your account: name, email address, password (stored hashed, never in readable form), and company details you enter.

Your work: bids, line items, cost build-ups, your catalog and crew rates, jobs, logged hours, equipment inspections, load tickets, and documents you upload such as bid schedules, supplier quotes and receipt photos.

Your employees: if you use the field app, the names, roles and pay rates you enter for the people on your roster, and the hours they log.

Where a punch happened: when an employee clocks in, switches jobs, or clocks out on the field app, Trench records their phone’s location at that moment, once, along with how precise the phone says it is. Nothing is recorded between punches — Trench never tracks a phone in the background. The phone asks the employee before sharing its location, and a punch still saves if they say no. Only people in the employer’s company account see it.

How Trench gets used: which screens are opened and which actions are taken, so we can see what is slow or confusing. It is tied to your account, not sold, and never includes the content of a bid.

People you invite into your company account, and field logins you create — which see only the jobs assigned to them, never pricing. Isolation between companies is enforced by the database itself, on every read, not by application code that could forget.

Being on the Trench team does not open your pricing. Trench was built alongside a working contractor, so we built the wall into the database: the Trench staff console shows a company’s name, which features it has switched on, and counts of activity — never a bid, a price, a cost build-up or a catalog. That applies to everyone on the Trench team, including anyone who also estimates for a construction company.

The only way past that wall is direct administration of the database. One person holds it: a Trench founder who does not bid work or work for any construction company. It is used only to keep Trench running, to fix a problem, or to answer a support question you asked — never to look at, copy or act on your bids or prices. The contractor Trench was built with has a customer account like yours, behind the same wall, and no way past it.

We disclose data to anyone else only if the law requires it. If we are asked for your data and we are allowed to tell you, we will.

These are the outside companies your data can reach, and why:

• Supabase — the database, logins and file storage. All of your work lives here.
• Vercel — hosting. Serves the app and keeps request logs.
• Google (Gemini) — reads a supplier quote or a receipt photo you upload, and proposes values from it. Only documents you choose to upload to those two features are sent, and they are not used to train Google’s models. Turn the feature off and nothing is sent at all.
• Resend — sends account email: invites, password resets and job reports you ask for.
• OpenStreetMap — draws the map on a job’s Jobsite Area, and looks up an address you type there to place the pin. Only that typed address is sent — never an employee’s location, which is compared against the jobsite inside Trench.
• Intuit (QuickBooks) — only if you connect it, and only to sync the employee roster you asked to sync.

For as long as your account is open. Delete something in the app and it is removed from the live database; a deleted bid sits in Trash until you empty it. Close your account and we delete your data within 30 days, except anything we are legally required to keep. Backups roll off on their own schedule, within 90 days.

Data is encrypted in transit and at rest. Access between companies is blocked at the database level and tested. Files you upload sit in private storage that cannot be read by a public link. No system is perfectly secure; if a breach affects your data we will tell you promptly and say what we know.

A copy of your data, a correction, or deletion — email us and we will do it. You do not need a legal reason and we will not ask for one.

Trench is a business tool and is not for anyone under 18. We do not knowingly collect data from children.

If this policy changes in a way that matters, we will post the new version with a new effective date and tell account owners by email. The Terms of Service cover the rest of your relationship with Trench.

Privacy questions, or a request under section 7: support@trenchbid.com.