Legal
PreGov holds two very different kinds of information: a small amount about the people who use it, and a large amount about how public agencies spend money. This describes both, and is specific about which is which.
Draft — not yet in force
This document describes how PreGov actually works today, but it has not been reviewed by a lawyer and is not a binding agreement. Do not rely on it. It takes effect only when it carries an effective date here.
Creating an account requires a work email address and a password. A display name is optional. Passwords are stored only as a bcrypt hash — we cannot read yours, and nobody at PreGov can recover it for you.
If you join a workspace, we store your membership, your role in it, and any market or category restrictions the workspace owner sets for you.
Each sign-in creates a session record so you can be signed out from another device. That record holds a coarse device class derived from your browser's User-Agent — "Windows desktop browser", not the full header, because a full User-Agent string is a fingerprinting surface with no operational use here — and a keyed hash of the IP address the session was created from. The raw IP is not stored.
Rate limiting works the same way. To stop someone guessing passwords or spraying registrations, we count attempts against a keyed hash of the email address or network the attempt came from. Raw email addresses and raw IPs never land in those counters.
Inside the application we record which screens you open, which screen you came from, how long you spent, and a small set of named actions such as running an export. Each event is tied to your user and your workspace.
We do not do this to visitors. If you are not signed in, nothing is recorded — there is no anonymous identifier, no advertising cookie, and no third-party analytics script on any page of this site.
This telemetry exists so we can see which parts of the product are unused or broken. It is not sold, and it is not shared with anyone outside the subprocessors listed below.
The substance of the product is public record: solicitations, bid tabulations, award decisions and the amounts attached to them, published by government agencies as part of their procurement process. That data names businesses — who bid, what they bid, who won.
Where a source publishes an individual's contact details alongside a business — a named contact, an email address, a phone number, a mailing address — we discard those fields at the point of import and verify afterwards that none survived. The product reads a firm's name, the city it is associated with, and the solicitation it appeared on. It has no use for the rest, so it does not keep the rest.
If a record about your business is wrong, or you believe it should not appear, write to us at the address at the end of this document. Tell us the record and why, and we will tell you what we found and what we did.
Retention is enforced by the software, not by intention:
PreGov runs on infrastructure operated by other companies. Each of these can technically access data in the course of providing its service:
We do not sell personal information. We do not share it with advertisers. There is no third-party tracker, tag manager or advertising pixel on this site — you can verify that by reading the network requests any page makes.
We do not use your data to train a general-purpose model. Where the product uses AI to summarise a document, that runs against the specific document you asked about.
You can change or remove your name and email from your account settings, sign out any session from any device, and turn on two-factor authentication at any time.
For a copy of what we hold about you, or for deletion of your account and its data, write to us. Depending on where you live you may have a statutory right to those things; we will handle the request the same way regardless of whether you do.
Every workspace's data is isolated at the database level, not only in application code, so a bug in a query cannot return another customer's rows. Two-factor secrets are encrypted at rest with a rotatable key. Administrative access to customer data is logged with the reason it was used.
None of that makes a system unbreakable. If you find a vulnerability, please tell us at the address below rather than demonstrating it against another customer's data.
We will post any change here and update the effective date. Material changes will also be sent to the email address on your account. Write to hello@pregov.com with any question about this policy, to make a privacy request, or to ask about a record concerning your business.
Engineering wrote the text above from the system's observable behaviour. These are the points it could not decide, listed here so the review has a starting agenda rather than a blank page.