Effective Date: February 2, 2026 | Last Updated: April 23, 2026
BuilderBlock is primarily designed for and marketed to United States residents. Individuals outside the United States who choose to use the Services do so at their own risk and are responsible for compliance with local laws, including the EU General Data Protection Regulation (GDPR), UK Data Protection Act, and other applicable non-U.S. privacy regimes. BuilderBlock does not tailor the Services for, nor claim compliance with, non-U.S. privacy frameworks.
Welcome to BuilderBlock. This Privacy Policy explains how BuilderBlock LLC ("BuilderBlock," "Company," "we," "us," or "our") collects, uses, discloses, and otherwise processes personal information in connection with our websites, mobile applications, platform, services, products, and other functionality we offer (collectively, the "Services").
BuilderBlock is a construction management platform that serves three types of users:
This Privacy Policy applies to all users of our Services, regardless of user type. By accessing or using our Services, you acknowledge that you have read, understood, and agree to the practices described in this Privacy Policy.
Where we have a direct relationship with you and you have created an account with us, BuilderBlock is the controller of the personal information we hold about you. Where we process personal information on behalf of a Contractor customer (for example, information about their subcontractors or customers that they enter into the platform), we act as a processor on behalf of that Contractor. In such cases, the Contractor is the controller of your personal information, and our processing is governed by our agreement with them.
If you have questions or concerns about this Privacy Policy, please contact us at [email protected].
We collect information in the following ways:
When you create an account, use our Services, or communicate with us, you may provide us with the following types of personal information:
Account and Profile Information
Business and Licensing Information
Location Information
Financial and Billing Information
Project and Business Data
Communications and Messaging
Reviews and Ratings
Electronic Signature Information
When you access or use our Services, we automatically collect certain information, including:
Device and Technical Information
Usage and Log Information
Visitor Analytics on Public Contractor Profiles
When you visit a contractor's public profile page on BuilderBlock, we collect anonymized analytics data to help contractors understand how visitors interact with their profiles. This data is collected only if you have accepted the cookie consent banner on the page. We collect:
If you submit the contact form on a contractor's profile, your anonymous analytics session may be linked to the lead record created from your form submission. This allows the contractor to understand how you found their profile. Once linked, future visits you make to the same contractor's profile from the same browser may be recognized as returning visits and attributed to your lead record, enabling the contractor to see when a known prospect revisits their profile. You can opt out of visitor analytics by declining the cookie consent banner or by enabling Do Not Track (DNT) or Global Privacy Control (GPC) in your browser settings.
Referral Attribution
If you arrive on a contractor's profile via a referral short link of the form /r/<code> shared with you by a past customer of that contractor, we set a first-party HttpOnly cookie named bb_ref (containing only the referral code, not the referrer's identity) so the contractor can credit the referring customer if you later submit the contact form. The cookie has a 30-day expiration and is restricted to same-site requests (SameSite=Lax). Anonymous analytics sessions you create on that contractor's profile while the bb_ref cookie is present may be tagged with the same referral identifier so the contractor can measure how their referral program drives traffic from past customers — independently of whether you ever submit the contact form. The referring customer's identity is never shown to you while you browse (we redact it to first name + last initial only, e.g., "Jane D."), and the referring customer's contact details (email, phone) are never shared with you. We do not sell, share with marketing partners, or feed referral attribution data to AI providers; the attribution is used solely to populate the contractor's internal referral dashboard and to credit the referring customer at the contractor's discretion.
Estimate View Tracking
When you open a secure estimate link shared with you by a contractor (for example, an HTML estimate at /quotes/public/<token>), we record an "estimate view" engagement event so the contractor knows you have viewed their proposal. The estimate view event includes the time of your view, an anonymized visitor identifier (the same SHA-256 hash described above — your raw IP address is never stored), and a reference to the specific estimate you viewed. Multiple views of the same estimate from the same browser within a two-hour window are recorded as a single view to avoid over-counting. Estimate view tracking is suppressed when:
Estimate view events are used for lead scoring (contractors can see which leads are engaging with their proposals) and, for contractors on qualifying subscription tiers, may also trigger real-time engagement alerts. Estimate view events are retained for 24 months from the date of the view, after which they are permanently deleted.
Security and Authentication Information
If you choose to connect third-party services to your BuilderBlock account, we may receive information from those services, including:
We only access third-party data that you explicitly authorize through the integration setup process. You can disconnect integrations at any time from your account settings.
We use the information we collect for the following purposes:
Providing and Operating the Services
Authentication and Security
Subscription and Billing Management
Communications
Improvement and Analysis
Legal and Compliance
Facilitating Electronic Signatures
BuilderBlock uses SMS text messaging to deliver time-sensitive notifications to users who have opted in. This section describes our SMS practices in detail.
You opt in to receive SMS messages from BuilderBlock by checking the SMS consent checkbox during account registration at http://builderblk.com/register. The consent checkbox states: "I agree to receive SMS messages from BuilderBlock including verification codes, invoice notifications, and project updates. Message and data rates may apply. Reply STOP to opt-out anytime."
You may also manage your SMS preferences on a per-notification-type basis in your account notification settings.
Message frequency varies based on your account activity, the number of projects you are involved in, and your notification preferences. You control which types of SMS notifications you receive through your account settings.
Standard message and data rates from your mobile carrier may apply to SMS messages you receive from BuilderBlock.
You can opt out of SMS messages at any time by:
After opting out, you will receive a confirmation message confirming your unsubscription. You will not receive any more SMS messages from BuilderBlock unless you re-enable SMS notifications.
If you previously opted out and wish to receive SMS messages again, you can re-enable SMS notifications in your account settings.
For help with SMS messaging, reply HELP to any message from BuilderBlock, or contact us at [email protected].
Mobile information will not be shared with third parties/affiliates for marketing/promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
We only share your phone number with our SMS service provider (Twilio) for the sole purpose of delivering the messages described in this section.
We do not sell your personal information. We share your information only in the following circumstances:
We share personal information with third-party service providers who perform services on our behalf, including:
| Service Provider | Purpose | Data Shared |
|---|---|---|
| Stripe | Payment processing and subscription management | Payment identifiers, subscription details, billing information |
| Stripe Connect | Marketplace payment processing — enables customers to pay contractors directly through the platform and contractors to pay subcontractors. BuilderBlock may retain a platform fee on each transaction. Stripe performs independent identity verification (KYC/AML) on Contractors, including collection of taxpayer identification information (TIN or SSN) and issuance of IRS Form 1099-K where required by law for Contractors receiving payments above the applicable federal threshold (currently $5,000 in gross payment volume per tax year, subject to change by the IRS). | Payment amounts, invoice references, connected-account identifiers, customer and contractor identifiers on each transaction; for contractors: business legal name, business address, representative identity documents, TIN or SSN for tax reporting, and bank account details for payouts. Card data is never touched by BuilderBlock — entered directly into Stripe-hosted forms. |
| Firebase (Google LLC) | Push notification delivery (Firebase Cloud Messaging for Android; Apple Push Notification service proxied via Firebase for iOS) | Device push tokens, platform (iOS/Android), notification payloads (title, body, and metadata you would also see in the mobile app) |
| Anthropic (Claude API) | AI-assisted features including voice command parsing, daily log summarization, cash flow forecasting, profit fade detection, lead response drafting, engagement follow-up drafting, customer-journey analysis, and lead-source classification. Processing is request-scoped — your data is not used by Anthropic to train its models. | Text excerpts and structured aggregates relevant to each AI request. Cost data (unit cost, markup) is stripped before requests are made. Financial amounts are rounded to the nearest $1,000 when they would otherwise be sent. |
| Deepgram | Audio transcription for voice-command features and daily-log voice notes (speech-to-text) | Raw audio recordings from voice capture sessions. Recordings are deleted from Deepgram systems after transcription completes. BuilderBlock retains only the resulting transcript and a reference identifier; we do not retain audio by default. |
| Twilio | SMS message delivery | Phone number, message content |
| SendGrid | Transactional email delivery | Email address, name, email content |
| Cloudflare | Content delivery network, DDoS protection, web application firewall, and file storage (R2) | IP address, request data, uploaded files |
| Railway | Application hosting and database infrastructure | All application data (hosted on their infrastructure) |
| OpenWeatherMap | Weather data for project dashboards | Location coordinates or ZIP code |
| ip-api.com | IP geolocation for security audit logs | IP address |
| MaxMind | City/region geolocation for visitor analytics on public profiles (where configured) | IP address (processed locally via GeoLite2 database, not sent to MaxMind servers) |
These service providers are contractually obligated to use your information only for the purposes of providing services to us and in accordance with applicable privacy laws.
When you connect third-party services through our integrations, data is shared with those services as necessary to perform the integration:
You initiate and control these integrations, and you can disconnect them at any time from your account settings.
Your information is shared with other users on the platform as necessary for the Services to function:
We may disclose your information if we believe in good faith that disclosure is necessary to:
In the event of a merger, acquisition, reorganization, bankruptcy, or sale of all or a portion of our assets, your personal information may be transferred as part of that transaction. We will notify you via email or prominent notice on our website of any change in ownership or uses of your personal information, as well as any choices you may have regarding your personal information.
We take the security of your personal information seriously and implement administrative, technical, and organizational measures to protect it, including:
While we implement these safeguards, no method of transmission over the Internet or method of electronic storage is completely secure. We cannot guarantee absolute security of your information.
We retain your personal information for as long as your account is active or as needed to provide you with the Services. Specifically:
When we no longer have an ongoing business need to retain your personal information, we will either delete it, de-identify it, or securely isolate it from further processing until deletion is possible.
BuilderBlock uses cookies and similar technologies to operate and improve our Services:
Essential Cookies — We use session cookies to maintain your login state, manage CSRF protection, and ensure the security of your browsing session. These cookies are strictly necessary for the Services to function and cannot be disabled.
Functionality Cookies — We may use cookies to remember your preferences, such as dashboard layout, theme settings, and notification preferences.
Analytics Consent Cookie — On public contractor profile pages, we display a cookie consent banner before collecting any visitor analytics. If you accept, we set a cookie named bb_analytics_consent (value: accepted, SameSite: Lax, 1 year expiry) to remember your preference. If you decline, no analytics data is collected and the cookie is set to declined. You can change your preference at any time by clearing your browser cookies and revisiting the page.
Analytics — When you consent to analytics on public contractor profiles, we collect anonymized visitor data (page views, clicks, scroll depth, time on page) to help contractors understand how visitors engage with their profiles. This data is linked to an anonymized visitor hash (SHA-256 of your IP address) — we never store your raw IP address for analytics. Analytics data is used in aggregate and is never used for advertising.
Contractor-Enabled Advertising Pixels — BuilderBlock itself does not use third-party advertising cookies or sell your personal information to advertisers. However, individual contractors may choose to enable third-party retargeting pixels (the Facebook/Meta Pixel and Google Ads tags) on their own public profile pages. When a contractor has enabled paid advertising, those pixels are loaded only after you accept analytics on the consent banner and only when your browser is not sending a Do Not Track (DNT) or Global Privacy Control (GPC) signal. See Contractor-Enabled Third-Party Advertising Pixels below for the full disclosure, including the opt-out links for Meta and Google.
Most web browsers allow you to manage cookie preferences through browser settings. Disabling essential cookies may prevent certain features of the Services from functioning properly.
Some contractor public profile pages on BuilderBlock (the pages at /pro/<contractor>) may include third-party advertising and retargeting pixels — specifically the Facebook (Meta) Pixel and Google Ads tags — when the individual contractor has chosen to enable paid advertising for their profile. These pixels are third-party trackers operated by Meta and Google, not by BuilderBlock. They allow that contractor to measure ad performance and to retarget visitors with advertising on Meta and Google properties.
These pixels are off by default and appear only on the profiles of contractors who have explicitly enabled them. They are not present on the rest of the BuilderBlock platform.
We honor your privacy signals before any pixel loads. When a contractor profile includes these pixels, BuilderBlock applies the same privacy gate it uses for its own first-party analytics:
bb_analytics_consent cookie described above). If you decline, or have not yet made a choice, no third-party pixel is loaded.When a pixel does load, it is provided directly by Meta or Google and is governed by their respective privacy policies and data practices. You can review and control how these companies use advertising data here:
Consistent with the Texas Data Privacy and Security Act (TDPSA) and other applicable privacy laws, you may opt out of targeted advertising at any time by declining analytics on our consent banner, by enabling a DNT or GPC signal in your browser, or by using the third-party opt-out controls linked above.
BuilderBlock is a business-to-business platform designed for construction professionals and their clients. Our Services are not directed at children, and we do not knowingly collect personal information from children under the age of 16.
If you are a parent or guardian and believe that your child has provided us with personal information without your consent, please contact us at [email protected]. If we become aware that we have collected personal information from a child under the age of 16, we will take steps to delete such information promptly.
Our Services may contain links to third-party websites, plug-ins, and applications. This Privacy Policy does not apply to, and we are not responsible for, the privacy practices of any third-party websites or services. We encourage you to read the privacy policy of any third-party service before providing them with your personal information.
Depending on your state of residence, you may have certain rights regarding your personal information. BuilderBlock is committed to honoring these rights for all users, regardless of location.
All BuilderBlock users can:
You may request deletion of your personal information by contacting us at [email protected]. Please note that certain data may be retained where we have a legal obligation to do so (e.g., financial records for tax purposes) or where the data is necessary to complete a transaction or provide the Services you have requested.
You may opt out of:
BuilderBlock does not sell your personal information, so no opt-out of sale is necessary.
Several BuilderBlock features use automated processing or artificial intelligence to provide insights, suggest drafts, and surface patterns. We disclose these practices so you can make informed choices about your use of the Services.
When you use the voice command feature in the BuilderBlock mobile app — for example, to dictate a daily log, punch-list note, or voice message — the app records audio and transmits it securely to Deepgram for speech-to-text transcription and to Anthropic Claude for structured extraction (for example, identifying project names, task items, or quantities). Deepgram deletes the audio from its systems after transcription completes. BuilderBlock retains the resulting transcript and the structured output; we do not retain the original audio by default. If you disable voice features in your account settings, audio will not be captured or transmitted.
For contractors on qualifying subscription tiers, we may generate AI-drafted content based on your business data, including lead response drafts, engagement follow-up drafts, daily log summaries, cash flow forecasts, and profit fade analyses. These drafts are advisory only — they are presented to you for review and you choose whether to send, edit, or discard them. We strip unit-cost and markup data before sending financial information to the AI provider and round amounts to the nearest $1,000 where appropriate.
For contractors with a public profile and lead generation features enabled, BuilderBlock assigns prospective customers an automated lead score on a 0-100 scale along with a categorical label (hot, warm, or cold) based on observed engagement signals such as form submissions, email opens, email clicks, estimate views, and return visits to the contractor's public profile. The scoring formula uses fixed, non-discriminatory signals and does not incorporate demographic data.
Lead scores are advisory only. They help contractors prioritize follow-up and do not produce legal or similarly significant effects as those terms are used in state consumer privacy laws: no contractor decision regarding pricing, service eligibility, credit, employment, housing, insurance, or any other legally significant determination is made or required to be made based on a score. Contractors remain free to engage any prospective customer regardless of score, and customers are not treated differently by BuilderBlock itself based on score. Lead scoring is performed by BuilderBlock on behalf of the Contractor (see Section 13); to opt out of scoring within a specific Contractor's account, please contact that Contractor directly.
When a contractor sends certain emails to you through BuilderBlock — notably marketing-category emails such as review requests, auto-outreach follow-ups, and engagement drafts — the email contains a tracking pixel and click-wrapped links that report back to us when the email is opened or a link is clicked. This engagement data feeds the lead scoring described in 11.5.3 above. Transactional emails (account notifications, estimate deliveries, invoice deliveries, payment receipts, password reset) do NOT contain tracking pixels. You can opt out of marketing engagement tracking at any time by clicking the unsubscribe link in any marketing email or by emailing [email protected].
When contractors enable smart scheduling with an integrated calendar (Google Calendar via FreeBusy, or Apple Calendar via CalDAV), we read free/busy time-slot data — not the titles or contents of calendar events — to compute available appointment slots. Calendar access is contractor-initiated and can be disconnected at any time from account settings.
Several U.S. states have enacted comprehensive consumer privacy laws, including California (CCPA/CPRA), Texas (TDPSA), Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), and others. These laws generally apply to businesses that meet defined revenue or consumer-volume thresholds (for example, processing the personal data of 100,000 or more consumers). BuilderBlock currently operates below the applicability thresholds of these statutes, so we are not presently subject to their direct obligations. Regardless of our statutory status, we voluntarily honor the following core rights for all U.S. users:
Categories of Personal Information Collected: Identifiers (name, email, phone number, IP address); commercial information (subscription and billing data, transaction records); internet or electronic network activity (usage data, log data); geolocation data (address, GPS coordinates from time tracking); professional information (trade, licenses, insurance, company details); and audio, electronic, or visual information (profile images, uploaded photos and documents).
We do not sell personal information. We do not share personal information for cross-context behavioral advertising. To exercise your right to opt out of any sharing for cross-context behavioral advertising (CCPA/CPRA "Do Not Sell or Share My Personal Information"), submit a privacy request with request type "Delete" — visitor analytics records linked to your email will be purged.
How to submit a privacy request. Identity is verified via a short-lived email round-trip (TDPSA §541.054), so a privacy request can only meaningfully cover data we can resolve against your email address. Anonymous visitors who have never submitted a contact form on a BuilderBlock contractor profile do not have an addressable identity in our system — the visitor hash recorded for analytics is private to your browser and not known to us. If you fall in that category and want to ensure no future visit is recorded, the most effective remedy is enabling Do Not Track or Global Privacy Control in your browser (both are honored automatically and rejected before any database write). BuilderBlock provides two submission paths:
Retention of privacy-request records. Once a privacy request is fulfilled, rejected, or expires, the request record itself (a row holding the request type, your email, timestamps, and a summary of what was returned or purged) is retained for 180 days by default to support audit and contestability under TDPSA §541.054. After 180 days the request record is purged automatically by a daily retention sweep. The do-not-re-track tombstones written when a delete request is processed are NEVER purged — they are an indefinite suppression contract under TDPSA §541.101, designed so that a fulfilled delete request cannot be silently undone by a future page-load from the same browser fingerprint. Audit log entries for privacy-request state transitions are retained separately under our administrative audit-log retention policy.
If state-law thresholds later apply to BuilderBlock, we will update this Privacy Policy to reflect the additional rights and response deadlines required by statute.
When Contractors use BuilderBlock to manage information about their subcontractors, customers, team members, and project stakeholders, BuilderBlock acts as a data processor on behalf of the Contractor (the data controller). In such cases:
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will:
We encourage you to review this Privacy Policy periodically. Your continued use of the Services after the posting of changes constitutes your acceptance of those changes.
If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
BuilderBlock LLC
Email: [email protected]
Website: builderblk.com
For privacy-specific requests (access, deletion, opt-out), please include "Privacy Request" in your subject line so we can route your inquiry promptly.