1. Information we collect
Account and contact information
Names, company names, email addresses, telephone numbers, account roles, login credentials, referral information, state, and account preferences.
Company verification information
Business addresses, license numbers and documents, insurance information and documents, trade specialties, verification status, reviewer notes, and related submissions.
Project, bid, and marketplace information
Project descriptions, locations, trades, schedules, plans, specifications, addenda, proposal files, bid amounts, notes, award status, messages, attachments, project access records, and user-to-user workflow activity.
Payment and transaction information
Product, amount, currency, transaction status, Stripe Checkout Session and Payment Intent references, receipts, access activation, refunds, disputes, chargebacks, and fraud-prevention records. Card numbers and CVCs are entered into Stripe’s secure payment interface and are not stored by BuildersBids.
Sales application and compliance information
Legal address, work authorization statements, experience, résumé, introductory video, references, taxpayer classification, taxpayer name, encrypted SSN or EIN information, last four digits, Form W-9, front and back of government identification, electronic acknowledgments, signatures, review decisions, commission records, and payout information.
Technical and security information
IP address, browser and device information, user agent, session identifiers, timestamps, login and password-reset activity, email-verification activity, audit records, security events, and error logs.
Communications
Contact requests, support messages, account and project messages, notification preferences, email delivery status, testimonials and consent references, and other communications with BuildersBids or marketplace users.
2. Sources of information
Information may come directly from users, their authorized company representatives, another user involved in a project or referral, Stripe, email and hosting providers, security and technical systems, public licensing or business records used for verification, and lawful authorities.
3. How information is used
- Create, verify, secure, administer, and support accounts.
- Review company and Independent Sales Representative applications.
- Publish authorized project previews and provide restricted project access.
- Match trades, process bids, record awards, and enable authorized communications.
- Process and verify payments, activate access, issue receipts, and address disputes.
- Calculate, hold, approve, reverse, and document commissions and bonuses.
- Send verification, security, project, bid, payment, support, and operational messages.
- Prevent fraud, abuse, duplicate transactions, unauthorized disclosure, and security incidents.
- Maintain records, enforce agreements, comply with law, and protect legal rights.
- Analyze and improve reliability, accessibility, usability, and marketplace operations.
4. How information may be shared
| Recipient category | Purpose |
|---|---|
| Authorized marketplace users | Project, bid, proposal, company, and contact information is shared only as permitted by the applicable role, trade purchase, bid acceptance, and project workflow. |
| Stripe | Payment processing, authentication, receipts, fraud prevention, refunds, disputes, and chargebacks. |
| Hosting, email, storage, security, and technical providers | Operate, secure, back up, monitor, and deliver the service under appropriate service arrangements. |
| Professional advisers and insurers | Legal, tax, accounting, insurance, compliance, or dispute assistance when reasonably necessary. |
| Authorities or affected parties | Comply with law, court orders, lawful requests, protect rights and safety, investigate fraud, or respond to a security incident. |
| Business transfer participants | Evaluate or complete a merger, financing, acquisition, reorganization, or sale, subject to appropriate confidentiality protections. |
5. Sale of personal information and cross-site tracking
BuildersBids does not sell personal information for money and does not operate as a data broker. As of this policy’s effective date, BuildersBids has not intentionally installed third-party advertising pixels or cross-site behavioral advertising analytics on the website. Essential service providers may process technical information to provide their services.
A person may submit a verified request directing BuildersBids not to sell covered information, even though BuildersBids’ current practice is not to sell it.
6. Cookies and similar technology
BuildersBids uses essential session, authentication, security, CSRF, checkout, and preference technology. Stripe may use necessary payment and fraud-prevention technology during checkout. Review the Cookie Notice for details.
7. Data security
BuildersBids uses administrative, technical, and physical safeguards appropriate to the sensitivity of the information, including private file storage, role-based access, encryption for specified taxpayer and compliance information, password hashing, session controls, audit records, and restricted document downloads. No system can guarantee absolute security.
8. Retention
Information is retained for as long as reasonably necessary to provide the service, maintain transaction and project history, administer accounts, comply with tax, accounting, licensing, fraud-prevention, security, and legal obligations, resolve disputes, enforce agreements, and preserve records subject to a legal hold. Retention periods differ by record type.
BuildersBids may retain archived project, bid, payment, commission, audit, and consent records after an account becomes inactive when needed for these purposes. Information that is no longer reasonably needed will be deleted, deidentified, or securely disposed of when practicable and legally permitted.
9. Privacy choices and requests
Users may update certain account and company information through the applicable portal. To request access, correction, deletion, restriction, a copy of information, or to direct BuildersBids not to sell covered information, use either designated request address:
- Email support@buildersbids.com with the subject “Privacy Request.”
- Use the Contact & Support Center, select “General question,” and begin the message with “Privacy Request.”
BuildersBids may verify identity and authority before completing a request. Some information may be retained or a request may be limited when permitted or required by law, including records needed for security, fraud prevention, contracts, tax, transactions, disputes, or legal claims. Rights vary by location and apply only when the relevant law applies.
10. California disclosures
California residents may request information and exercise rights available under applicable California law. BuildersBids identifies the categories of personal information collected and the categories of recipients in this policy. BuildersBids does not currently respond differently to browser “Do Not Track” signals because no uniform technical standard requires a particular response. BuildersBids does not knowingly allow third parties to collect personally identifiable information over time and across unrelated websites for targeted advertising through BuildersBids.
11. Nevada disclosures
Nevada residents may submit a verified request through the designated request addresses above directing BuildersBids not to make a sale of covered information. BuildersBids will respond within the period required by applicable Nevada law and may use a lawful extension when reasonably necessary.
12. Children
BuildersBids is a business marketplace and is not directed to children under 18. BuildersBids does not knowingly create marketplace accounts for children. Contact us if you believe a child submitted personal information.
13. Material changes
BuildersBids may update this policy. Material changes will be identified by a revised effective date and may also be communicated through the website, account, or email when appropriate.
BuildersBids LLC
support@buildersbids.com
BuildersBids Contact & Support Center
No public street address is published through this policy.