1. Scope and Privacy Commitment
This Privacy Policy explains how BidBreak collects, uses, stores, shares, and protects personal information in connection with its websites, applications, AI-assisted construction estimating tools, preconstruction workflows, and related services. It applies to account holders, website visitors, company administrators, proposal recipients, and people whose information users submit to the Services. Organizations using BidBreak are responsible for determining that they have authority to provide project and contact information.
2. Information We Collect
We collect information you provide, information created through use of the Services, technical information collected automatically, and information received from authorized service providers or integrations. The categories and examples below describe data that may be collected depending on the features you use.
3. Account and Company Information
Account information may include name, email address, authentication identifiers, company name, trade specialties, role, subscription status, company branding, address, phone number, website, team membership, preferences, and communications. We record legal-policy versions, acceptance timestamps, user identifiers, and the server-observed IP address associated with acceptance for compliance and audit purposes.
4. Uploaded Documents and Construction Data
Users may upload PDFs, construction drawings, specifications, addenda, images, photographs, spreadsheets, schedules, bid forms, ZIP archives, and other project files. We store the original file or a service-generated reference and may create extracted text, page images, thumbnails, chunks, classifications, sheet references, or other technical derivatives needed to analyze and display the material.
5. RFIs, Estimates, and Generated Work Product
We process project names, client and contact details, RFIs and responses, scope items, quantities, generated estimates, material and labor breakdowns, exclusions, clarifications, risks, proposal content, revisions, approvals, status history, email and proposal tracking events, and user edits. These records enable collaboration, history, auditability, proposal delivery, and improvement of user-directed outputs.
6. Payment Information
Subscription and credit payments are processed through Stripe. BidBreak may receive transaction identifiers, customer and subscription IDs, payment status, billing contact details, card brand and last four digits, invoices, refund status, and related records. BidBreak does not receive or store full payment-card numbers or security codes. Stripe processes payment information under its own privacy policy and security obligations.
7. Usage Analytics and Communications
We collect feature interactions, generation and regeneration activity, file counts and sizes, page counts, model and processing metrics, credit usage, exports, errors, support requests, email delivery status, proposal views, and related operational events. We use this data to provide account history, measure performance and costs, detect abuse, troubleshoot, support customers, and improve product design. Analytics should not include unnecessary sensitive content.
9. Device and Network Information
We may collect IP address, browser type, operating system, device and session identifiers, language, approximate region derived from IP, timestamps, referring pages, requested URLs, and diagnostic or security logs. This information supports authentication, fraud prevention, rate limiting, incident investigation, compatibility, and legal compliance.
10. How We Use Information
We use information to operate and secure accounts; upload, store, convert, extract, and analyze documents; generate estimates and other requested work product; provide project, proposal, email, and RFI workflows; process billing and credits; deliver customer support; detect fraud and abuse; diagnose failures; communicate service and policy updates; comply with law; and improve platform performance, reliability, usability, and product capabilities. Where required, we rely on contract performance, legitimate interests, consent, or legal obligations as the applicable processing basis.
12. Document Storage and File Deletion
Uploaded files and technical derivatives are stored using managed cloud infrastructure and may be replicated for availability and backup. Authorized account users can delete uploaded files through available project controls or request deletion through the website contact form. Deletion removes active access, but residual copies may remain temporarily in backups, logs, cached derivatives, legal holds, proposal history, or records needed for security, billing, dispute resolution, or compliance. Deleting a source file may not automatically delete estimates or proposals previously generated from it; those records must be deleted separately where controls permit.
13. Data Retention
We retain account and project information while an account is active and for a reasonable period afterward to provide exports, restore service, resolve disputes, enforce agreements, prevent fraud, and meet legal, tax, accounting, and payment obligations. Retention varies by data type, account instructions, backup cycle, contractual requirements, and legal holds. When information is no longer reasonably needed, we delete, aggregate, or de-identify it. Users may request account or file deletion, subject to lawful exceptions and organizational authority.
14. Security Measures
BidBreak uses administrative, technical, and organizational safeguards appropriate to the nature of the information, including access controls, authentication, role-based permissions, encrypted transport, managed infrastructure, service monitoring, backups, provider review, and incident response practices. No internet transmission, AI system, or storage service is completely secure. Users must protect credentials, assign least-privilege access, review sharing and proposal recipients, and notify BidBreak promptly of suspected compromise.
15. Privacy Rights and Requests
Depending on location, individuals may have rights to access, correct, delete, restrict, or receive a copy of personal information; object to certain processing; withdraw consent; or appeal a request decision. Requests may be submitted through the BidBreak website contact form and may require identity, account, and authority verification. Company-managed information may be referred to the organization controlling the account. We will not discriminate for exercising applicable privacy rights.
16. GDPR Readiness
For individuals in the European Economic Area, United Kingdom, or Switzerland, BidBreak is prepared to support applicable rights and controller-processor obligations. BidBreak generally acts as a processor or service provider for project content submitted by business customers and as a controller for account, billing, security, and direct service information. Cross-border transfers may rely on adequacy decisions, contractual safeguards, or other lawful mechanisms. Individuals may complain to their local supervisory authority after contacting BidBreak.
17. California Privacy Readiness
California residents may have rights to know, access, correct, delete, and obtain information about categories, sources, purposes, and recipients of personal information, and to opt out of sale or sharing as defined by California law. BidBreak does not sell personal information for money and does not knowingly share personal information for cross-context behavioral advertising. Authorized agents may submit verified requests. Certain business-to-business, employment, security, legal, and other exceptions may apply.
18. Children’s Privacy
BidBreak is a business service not intended for children under 13, and users must be at least 18 to create an account. We do not knowingly collect personal information from children. If you believe a child provided information, contact BidBreak through the website contact form so the information can be investigated and deleted where appropriate.
19. International Users
BidBreak and its service providers may process information in the United States and other countries where laws differ from those in your location. By using the Services, you understand that information may be transferred and processed across borders subject to contractual, technical, and legal safeguards appropriate to the transfer. You remain responsible for project-specific restrictions, including export controls and contractual data-location requirements.
20. Changes to This Policy
We may update this Privacy Policy as the Services, providers, laws, or practices change. The version, effective date, and last-updated date appear on this page. Material changes will be communicated through the Services, email, or another reasonable channel and may require renewed acknowledgment where required.
21. Contact Information
Privacy questions and requests may be submitted through the contact form on the BidBreak website. Include the account email, company, request type, applicable jurisdiction, and enough information to verify and locate the relevant records. For security, BidBreak may request additional verification before disclosing, correcting, exporting, or deleting information.
