← Back to Build

Privacy Policy

Effective November 5, 2026

Who runs Build

California First Strategies LLC runs Build and is responsible for the information this policy describes.

Accounts and company work

Build stores sign-in and profile information, company memberships and roles, settings, and records you or your team put into the service. These include contacts, deals, jobs, plans, models, takeoffs, quotes, RFIs, change orders, documents, messages, files and payment records. Company access follows membership, role and record permissions; some roles cannot see dollar amounts. A company login and a personal account are distinct, even when linked. Company administrators manage access to company work.

Private records and public work

Company records are not automatically public posts. Public profiles, published posts, public projects and milestones, artifacts, shared models, the public Map and Verified Work can be viewed according to their visibility or link settings. Some assistant actions, including public profile edits, project and milestone changes, and artifacts, show immediately. Draft posts and project updates wait for Studio review. Recipients can see records shared with them and may keep their own copies. A public link or publication can reach people outside your company.

Assistants and connected accounts

When you authorize an assistant through OAuth or a connection token, it can request the tools available to that connection, subject to your company access. Results returned to the assistant can contain company contacts, correspondence, document text, filenames, prices if your role permits them, and other records needed for the request. The assistant provider handles those results under its own terms and privacy policy. Connect only providers you trust with this information. Turn off a connection in Settings under Connect your assistant, or use OAuth revocation, to stop future access through it. Revocation does not recall information already returned or undo completed actions. Manage copies and conversations with that provider separately.

Activity and security records

Build records activity, document versions, sends, link visits and responses so people can follow their work and check what happened. Shared-document and model events can record the time, action, browser information and network address; these are not proof that a particular person read a document. Company assistant calls keep a request identifier, caller and company, tool, outcome, timing, affected record identifiers, an input hash and a shortened input copy with secret-named fields redacted. Emails and short text can remain in that copy. API and infrastructure logs support rate limits, security and troubleshooting. Do not put passwords or unrelated sensitive information in tool requests.

Build PlanReader and File Radar

Build PlanReader can report a computer identifier, label or hostname, operating system, app version and recent presence so Build can show which computer is available. File Radar scans the folders configured on that computer. Its local map and previews stay on the computer; a scan itself does not upload file contents or download online-only files. Build can receive paths, filenames, job identifiers, file type, size, modification time and availability. With copy recognition enabled, it can also receive fingerprints and drawing metadata such as sheet, page count and markup state. Company file settings can limit shared names and paths to fingerprint-based records. You can pause radar and change its folders and recognition settings. Previously recorded metadata can remain in Build. Uploading a file, using a cloud reading feature, or authorizing a local file request is a separate action that can transmit file contents.

Connected mail and sending

You can connect a Gmail mailbox to your account or company. Build asks Google for permission to read mail and to compose mail, and stores an encrypted refresh token for the connection. Build then follows new messages in Inbox and Sent: it reads their headers and snippets, and reads the full message and its attachments when the mail carries files, so plans, proposals and other documents can be filed to the right job and folder. Build reads the text of messages you sent so drafts it writes for you match how you write. When you ask, Build creates, rewrites or discards Gmail drafts, and sends from your mailbox a request you approved, such as a price request to a vendor. Mail delivered or forwarded to a company’s Build address can include full message content, attachments and links. Attachment holding and filing depend on company settings. Disconnecting a mailbox removes its stored connection secret and attempts to revoke provider access; mail already filed stays filed. Other Build sending features can send documents, requests, invitations and notifications, record recipients and delivery activity, and use company and connection permissions where applicable. Review recipients and content before authorizing a send.

Public business directory

Build’s company and vendor directory is public by design. It contains business names, places, business contact details, websites, license information and trades, including contributed business facts, facts recorded from source documents, and facts collected from public business websites, license-board records and directories. Company facts record their source kind, source reference where supplied, and observation time. Directory facts are separate from a company’s private quotes, purchase orders, notes and relationship records. Companies can claim a listing through the ownership checks. Permitted users can submit profile corrections with a reason; changes are logged. Claimed companies can correct their own facts, and permitted users can use Fix or Forget on company facts. Forget hides a fact rather than erasing its history. For a source question, a correction you cannot make, or a removal request, contact us with the listing link and information at issue. A listing is not an endorsement or proof that the company has joined Build.

Phone features

With device permissions you grant, phone features use photos and the camera for uploads, stories, model viewing and scans, microphone and speech recognition for voice features, and location for local discovery and location-based features. Location can be precise if you allow it. Selected uploads, scans and submitted voice requests can leave the phone to provide the feature. Push registration stores an installation identifier, notification token, authorization state, linked accounts and device information such as app and system version, label, time zone and locale. Manage permissions and notification choices in the app and device settings.

Use and service providers

We use information to run accounts and company tools, share work you choose, deliver messages and notifications, support community features and creator payments, prevent abuse, and troubleshoot and improve the service. Build uses Supabase for authentication and storage, Twilio for sign-in codes and text messages, Stripe for payments and payouts, and mail, hosting, analytics and connected-service providers for the relevant features. Stripe processes payment card details. Information sent to connected assistant providers or GitHub is also subject to their policies. We do not sell personal information or use it for cross-app advertising.

Controls, retention and deletion

Settings provides profile visibility, connection and account controls. Deleting a personal account removes its sign-in and linked personal profile data through the account deletion process; active subscriptions and payment accounts must be closed successfully first. Transaction, payout and subscription history can remain with the personal user reference cleared. A company-issued work login is ended by the company; you can unlink it from your personal account or ask a company administrator to remove you. Personal account deletion does not promise deletion of company business records, sent documents, recipients’ copies, public business facts, security logs or backups. We retain records needed to operate the service and address security, disputes, payment, tax and legal obligations. Retention varies by record type; there is no single automatic deletion deadline for all company data. Contact us for access, correction or deletion requests that the app does not resolve.

Text messages

If you tick the box on your crew invite, or turn texts on at builderslive.org/texts, Build texts your work schedule to your phone. Build keeps your number, your company, the words you agreed to, when you agreed, and whether each text was delivered. Your company can see whether a text reached you. Twilio delivers the texts and handles your number and the message to do that. Reply STOP to any text to stop them; Build keeps the record of your agreement and your STOP as proof.

We do not sell your phone number. We do not share your phone number, or your agreement to get texts, with anyone for their marketing, and we do not use them for advertising. Sign-in codes are separate: Build sends them only when you ask for one.

Google user data

Build’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Build uses Gmail data only to provide the mail features described above, which you see in the app: filing mail and attachments to your jobs, writing drafts in your voice, and sending requests you approve. Build does not use Gmail data for advertising, does not sell it, and does not use it to train generalized artificial intelligence or machine learning models. Build transfers Gmail data only as needed to provide those features (for example, to an assistant you connected when you ask it about your mail, and to the hosting and storage providers that run Build), to comply with law, or as part of a merger or acquisition. People at Build do not read your Gmail data unless you agree for specific messages, it is needed for security such as investigating abuse, or the law requires it. Disconnect the mailbox in Settings at any time, or remove Build’s access on your Google Account’s third-party access page.

Contact

For privacy questions or requests, email support@builderslive.org.