BidSight
Legal

Privacy Policy

Effective date: July 23, 2026 · Last updated: July 23, 2026
Operator: BidSight (Cauldron Labs / Justin Gardner) · Contact: justinpgardner@gmail.com

In short: We use public government contracting data to run BidSight. If you create a business profile, subscribe to alerts, or buy a service, we store the information needed to deliver that product (usually your email and business profile fields). We do not sell your personal data. Fit scores run in your browser against your profile.

1. Scope

This policy describes how BidSight (“we,” “us”) collects, uses, and shares information when you use bidsight-151.netlify.app and related services (search, map, alerts, AI drafts, business profiles, and paid features).

2. Information we collect

2.1 Information you provide

2.2 Information collected automatically

2.3 Public and third-party data we process (not “your” personal data)

BidSight indexes and displays publicly available government procurement information, including from sources such as SAM.gov, USAspending.gov, and state/local open portals. That data may include company names of awardees and other public contracting facts. We use it to provide market context and related-win insights; it is not treated as private customer data under this policy.

3. How we use information

We do not sell personal information. We do not use your business profile to cold-email other users about their competitors.

4. Legal bases (where applicable)

Where privacy laws require a legal basis (e.g. GDPR), we rely on: performance of a contract (providing the service you requested), legitimate interests (securing and improving the service, using public procurement data), and consent (where we ask for it, such as optional marketing if we ever add it).

5. How we share information

We share data only with processors that help us run BidSight, under agreements appropriate to the service:

We may disclose information if required by law, to protect rights and safety, or in connection with a merger, acquisition, or asset sale (with notice where required).

6. Cookies and local storage

BidSight is primarily a static app. We use browser local storage (not advertising cookies) to:

You can clear site data in your browser settings. That signs you out of the device-local session and removes the local profile cache; your server-side profile (if any) remains until you ask us to delete it.

7. Profiles, accounts, and fit scores

8. Payments

Paid features are processed by Stripe. Stripe’s privacy policy applies to card and payment data they collect. We store order records needed for fulfillment, support, and accounting (email, amount, product, related opportunity id, status).

9. Email communications

We do not buy email lists for BidSight marketing spam. If we introduce optional newsletters, we will ask for consent where required.

10. Retention

11. Security

We use HTTPS, access-controlled databases, service-role secrets only on the server, and least-privilege patterns for browser access (public opportunity data vs private profile/order data). No method of transmission or storage is 100% secure; please use a unique email you control for magic links.

12. Children

BidSight is directed at businesses and professionals. We do not knowingly collect personal information from children under 16.

13. International users

We and our processors may store and process data in the United States and other countries where our providers operate. If you access BidSight from outside the U.S., you understand that information may be transferred to those locations.

14. Your choices and rights

Depending on your location, you may have additional rights (access, correction, deletion, restriction, portability, objection). We will respond to verified requests within a reasonable period.

15. Third-party links

Opportunity pages may link to SAM.gov, agency portals, USAspending, and other third-party sites. Their privacy practices are their own; review those policies when you leave BidSight.

16. Changes

We may update this policy as the product evolves (for example, new paid features or processors). We will post the revised effective date on this page. Material changes that affect how we use personal data for cloud profiles or purchases will be called out on the Profile or checkout experience where practical.

17. Contact

Questions about privacy or data requests:
justinpgardner@gmail.com
Subject line: “BidSight privacy”