Skip to content
Built2Bid

Security

Last updated November 18, 2026

Built2Bid LLC

Current Published VersionLegal review pendingVersion: November 18, 2026

This document represents the current published version of Built2Bid LLC's applicable policies, terms, or disclosures and is pending review by independent legal counsel.

Built2Bid may revise this document following legal review or as business, regulatory, or operational requirements change. Updates will be published with appropriate version information, and additional notice or consent will be provided where required by applicable law.

Users are encouraged to review the current published terms and policies applicable to their use of the platform.

Legal document status

Built2Bid L.L.C. keeps a written Information Security Policy, owned by our founder and reviewed at least once a year and after any major change or incident. This page summarizes how we protect your account, your bids and customers, and any financial data you connect.

Your data is kept separate

Every record is tied to your account or company workspace, and the database enforces row-level security, so one customer's data can't be read by another. Logos, photos and generated documents are stored privately and shared only through short-lived signed links.

Sign-in and access

  • Passwordless sign-in with one-time codes sent to your email, so there is no Built2Bid password to steal or reuse.
  • Optional two-step sign-in with an authenticator app. It is required before anyone can connect a bank account.
  • Team members get only the workspaces and features their role allows, and you can remove access at any time.
  • Our own administrative access is limited to the founder, protected by multi-factor authentication, and recorded in an audit log.

Encryption

  • All traffic uses HTTPS (TLS 1.2 or newer) with HSTS.
  • Data is encrypted at rest by our database and storage provider.
  • Bank connection tokens get an extra layer of AES-256-GCM encryption before they are stored, and are never sent to your browser.
  • Keys and secrets live only in our hosting provider's encrypted environment settings, never in source code.

Connected bank accounts

If you choose to connect a bank account, we use Plaid with read-only access to balances and transactions, for cash-flow forecasting and reconciliation. Built2Bid never sees your bank sign-in details and cannot move money. You can disconnect an account at any time.

Payments

Card payments are handled by Stripe. We never store card numbers, and every Stripe event we receive is signature-verified.

Building and running the service

  • Every code change goes through a reviewed pull request and is tested before it goes live.
  • Dependencies are monitored for known vulnerabilities and patched promptly.
  • Rate limits, upload file-type checks and outbound request guards protect against common attacks.
  • Uptime and error monitoring alert us to problems, and the database is backed up daily.

Trusted providers

We rely on established providers that maintain their own security programs, including Supabase (database, sign-in and storage), Netlify (hosting), Stripe (payments) and Plaid (bank connections). We review each provider before use.

Your control

You can export all of your data or delete your account from Account settings. See our Privacy Policy for what we collect and how long we keep it.

Incidents

We have a written incident response plan. If a security incident affects your data, we will notify you without undue delay and as required by law.

Report a security issue

If you believe you've found a vulnerability, email privacy@built2bid.org. Please give us a reasonable chance to fix it before sharing it publicly, and don't access or change other customers' data. We aim to reply within 3 business days.