Privacy
Effective date: 2026-11-03
Who is responsible
BidPro is operated by Delegate Labs. You can reach us at james@delegatelabs.ai.
What we hold
To run the service we hold:
- names and email addresses of account users
- company details, such as the company name, address, phone number and logo
- the names, email addresses, phone numbers and property addresses of your customers
- photos you add to a proposal, and the work items, hazard notes, prices and totals in your proposals
- the times a proposal is viewed
- the IP address and user agent recorded when a proposal is accepted
What we use it for
We use this data only to run the service: to sign you in, build and send your proposals, show them to your customers, record their response and let you export your own records. We do not sell your data or your customers' data, and it is not used for advertising.
Who else handles it
We use outside services to run BidPro. Amazon Web Services stores and serves everything we hold. Postmark delivers the emails you send. Clerk handles sign-in. We also rely on a few infrastructure services that receive far less. Each one is listed below with what it receives.
- Amazon Web Services (processor). Hosts the application server, the database, photo storage, DNS, container images and configuration secrets, and sends billing and cost alerts to the operator. Receives: Everything held in the service: account, customer, property, proposal and photo data, and the network details of every request.
- Postmark (processor). Delivers the proposal emails an owner sends to a customer and reports whether each was delivered or bounced. Receives: The recipient's email address and name, the owner's company name and reply-to address, and the proposal link inside each email.
- Clerk (processor). Signs owners in and verifies sign-in tokens. Its script runs on signed-in owner pages only, never on the public pages. Receives: The email address, name and sign-in details of account users, plus the IP address and browser details of every sign-in request.
- Let's Encrypt (infrastructure). Issues the TLS certificates that secure this site's web addresses. Receives: The public domain names of the service, and the server's IP address when a certificate is requested.
- ZeroSSL (infrastructure). Issues TLS certificates when Let's Encrypt cannot (Caddy's default fallback certificate authority). Receives: The public domain names of the service, and the server's IP address when a certificate is requested.
- Docker Hub (infrastructure). Supplies the Caddy web server image the host runs. Receives: The server's IP address when the image is pulled. No visitor or customer data.
- Ubuntu package repositories (infrastructure). Supply the Docker packages installed when the server is first set up. Receives: The server's IP address at setup time. No visitor or customer data.
- Google Fonts (infrastructure). Serves the IBM Plex Sans typeface that every page loads. Receives: The IP address and browser details of every visitor's browser, and of the server's own browser when it prints a PDF.
Cookies
The landing page, the Terms and this Privacy page set no tracking cookies. Signed-in owner pages use cookies from Clerk to keep you signed in. We run no analytics or advertising on any page.
How to request export or deletion
You can export your proposals as PDF and CSV from inside BidPro at any time. To request export or deletion of your account and its data, email james@delegatelabs.ai from the email address on your account. Database backups are kept for 7 days, so deleted data can remain in a backup for up to that long.
Changes to this policy
If we change this policy we will publish the new text on this page with a new effective date.