Privacy Policy
This policy explains what information WeBuilt (“WeBuilt”, “we”, “us”) collects through getwebuilt.com, through WeBuilt Contractor OS and its account and billing pages, and when you contact us; how we use it; and the choices you have. Use of WeBuilt’s services is governed by our Terms of Service, which this policy is part of. “WeBuilt” means WeBuilt LLC, a Utah limited liability company, 2340 N 400 W Unit E1, Provo, UT 84604. Questions: hello@getwebuilt.com.
Two kinds of information
We handle information in two roles. For our own relationship with you (visitors, prospects, Account Owners and Authorized Users of Contractor OS), WeBuilt decides how the information is used, as this policy describes. For the records a contractor keeps in its workspace (its customers, leads, employees, estimates, invoices and conversations), the contractor decides; WeBuilt processes those records only to provide the service, on the contractor’s instructions, as described under “Customer Data we process for contractors”.
Information we collect
- What you give us in our forms: your name, company, trade, email address, optional mobile phone number, what you tell us about your business, and any optional answers (such as company size, current software, and preferences).
- Text-message consent: if you tick the optional text-message box, we record your phone number, that you opted in, the date and time, the page you used, the exact consent wording you saw, and limited technical details (your browser type and a one-way hashed version of your IP address) so we can show when and how you consented.
- Website usage: we record a small set of on-page events (for example, which sections were viewed or which sample question was tapped in the Studly demo). These events contain no names, email addresses, phone numbers, or text you type. We also use Google Analytics to understand how visitors find and use the site: it sets first-party cookies (such as
_ga) and sends Google information like the pages you view, how you arrived, your device and browser type, and your approximate location. We don’t use advertising cookies. - Account and workspace information (Contractor OS): the email address and identity-provider identifiers you sign in with (an emailed one-time code, Google or Microsoft), your name as shown in the workspace, your role (owner, editor or viewer), your company’s name and Contractor ID, invitations you send or accept, your plan and billing status, session information (such as “Remember me” on a device), and support requests you make. We also record a small set of categorical usage events and, as on the website, Google Analytics measures how the app is used.
- Billing information: when you start a paid plan, Stripe, our payment processor, collects your payment details directly. WeBuilt receives and keeps your Stripe customer and subscription identifiers, plan, billing status, invoice history and the email address on the account. WeBuilt never stores card numbers.
- Terms of Service acceptance: when you accept our Terms for your company, we record the version accepted, the date and time, your account email, the exact statement you agreed to, and limited technical details (your browser type and a one-way hashed version of the IP address), so that both of us can show which version applies.
- Studly and AI features: the questions you ask Studly and the answers it gives are kept in your workspace’s history. Where a feature answers, words, plans or summarizes with a language model, the question and the relevant workspace records are sent to the model to produce that response (see “AI model provider” below).
- Facts you ask Studly to remember: if an Account Owner or administrator asks Studly to remember something, we save it in your workspace with who added it and when. Studly uses it in later conversations for your company, for anyone in your company who uses Studly, and sends it to our AI model provider when it answers. It may include details about your customers. Studly refuses to save passwords, card and bank numbers, Social Security numbers and health details. The Account Owner or an administrator can delete any of it. Deleting a saved fact stops Studly from using it, but past stored conversations still contain its words. These facts are workspace records: they’re included in an export and deleted with your workspace.
- Messages you send us: emails and, once our text program is active, text messages you send to WeBuilt, including replies such as STOP or HELP.
Customer Data we process for contractors
A contractor’s workspace holds information about its own customers, prospects, employees, subcontractors and jobs. The contractor owns that information and decides why and how it is used; WeBuilt hosts and processes it only to provide, secure and support the service and as the contractor directs in the app. We do not sell it, we do not share one contractor’s records with another, we do not benchmark contractors against each other, and we do not use it to train general-purpose AI models. If you are a contractor’s customer or employee and have a question about your information, contact that contractor first; we will help the contractor respond to the extent the product allows. If a law that applies to a contractor requires a written data processing agreement, the contractor can contact us.
Time tracking and location (Contractor OS)
Time tracking is an optional Contractor OS feature that a contractor (the “employer”) turns on for its own company. It is not on for every company. It is included in Crew Max. On monthly Crew it is available as a paid add-on at $19/month, added from your account page after you subscribe. It is not sold on yearly Crew. On Solo and on earlier plans WeBuilt switches it on only for a company whose Account Owner has asked for it and to which WeBuilt has recorded a grant, including a grant already recorded, and it is not switched on automatically for a new account on those plans. When an employer uses it, WeBuilt processes the following on the employer’s instructions, as described under “Customer Data we process for contractors”:
- Employee details and assignments: the employee’s name and work email address, the jobs the employer assigns to them, and the employee’s sign-in identifiers.
- Time records: clock-in and clock-out times, unpaid breaks, the time our servers received each action, any correction request an employee sends, and any correction, review note or approval the employer records.
- One location reading at each clock action: only at the moment the employee taps Clock In or Clock Out, and only after the phone or browser asks the employee for permission, the app takes a single reading of the device’s location. We save that reading (latitude, longitude and the accuracy the device reported) with that punch, together with the distance from the jobsite the employer set up and a result of inside, outside or unverified.
What we do not do. WeBuilt does not track an employee’s location continuously or in the background. The app does not read location between punches, while it is closed, or while the employee is off the clock, and it does not build a route or location history. Location is read only from an employee’s own tap on a clock button. An employee can decline the permission request or turn location off for the app or the device at any time.
Jobsite addresses. When office staff enter a jobsite address, WeBuilt may send that address to the U.S. Census Bureau Geocoding Service to estimate the jobsite location. Employee GPS readings collected at Clock In and Clock Out are not sent to that service. The service returns an estimate of the location from street data, not a surveyed building position, and WeBuilt shows it to the office as an estimate.
If location is declined or unavailable, the employee can still clock in and out. The punch is saved without a verified location, marked “unverified” and flagged for the employer to review. A reading that is outside the jobsite radius is saved and flagged the same way, and a reading whose reported accuracy is wider than the jobsite radius is saved but shown as unverified, not as inside. Neither case blocks or removes the recorded time by itself.
Who sees it and what they can do. The employer, not WeBuilt, decides how the time records are used. The employer’s authorized users can see the time records, including each saved location reading, and can correct a punch (the original punch and its location are kept, and every correction records who made it, when and why), approve the week’s hours, and export approved hours as a CSV file. An employee sees their own time records and can ask for a correction. Our hosting providers process these records for us as described under “Who we share information with”. We do not sell location readings or time records, use them for advertising or marketing, or use them to train AI models, and we do not share them between companies. Time tracking does not connect to payroll or accounting software, and it does not send or pay anything.
Employees: your employer decides whether to use time tracking and why. Ask your employer for a copy of, or a correction to, your time records. Location readings are part of the time record and are kept for as long as the employer’s workspace keeps its records (see “How long we keep information”).
How we use information
- To respond to you, set up walkthroughs, and manage walkthrough requests and applications.
- To create and run your company’s workspace, sign you in, apply your plan and roles, and keep your records available to your company.
- To bill you through Stripe, manage your subscription, and keep the records that tax and accounting rules require.
- To send the emails you’d expect, such as confirming we received your request, account and billing notices, and notices about changes to the Terms of Service or this policy.
- If you opted in to texts: to send marketing and customer care text messages as described in our SMS Terms.
- To answer your questions through Studly from your own company’s records, and to provide support.
- To improve the website and the service and understand which parts are useful, using the usage events and analytics described above.
- To keep records of consent, acceptance and opt-outs, to secure the service, prevent abuse and investigate problems, and to meet legal obligations.
Some of our messages may be prepared or sent with the help of automated or AI-assisted tools. Your information is used for WeBuilt’s own communications with you.
Text messaging (SMS) and mobile information
We do not sell, rent, or share mobile opt-in information or text-message consent with third parties or affiliates for their marketing or promotional purposes.
We share mobile phone numbers and consent status only with the service providers that help us deliver WeBuilt’s own messages — our messaging provider and the wireless carriers — and only as needed to send and route those messages. Text-message opt-in data and consent are excluded from any other sharing described in this policy.
Opting in to texts is optional and is not a condition of purchase. You can opt out any time by replying STOP. See the SMS Terms for details.
Studly by text. If you link your mobile phone to Studly in the WeBuilt app, we record that phone number, the account and company it is linked to, when you linked it, and the texts you send to and receive from Studly. We use them to answer your questions about your own WeBuilt account and to send you account notifications. The text of your questions and the relevant records are sent to our AI model provider to prepare the answer, in the same way as when you ask Studly in the app. Linking is optional, you can unlink your phone in Settings at any time, and you can reply STOP to stop texts. We do not use this to text your customers.
Who we share information with
We do not sell your personal information. We share it only with service providers that operate WeBuilt’s website, application and communications on our behalf, under their obligations to protect it:
- Hosting and data storage: our hosted-application platform (Hedy), which runs on Amazon Web Services in the United States, for the website, Contractor OS and their data.
- Email delivery: the email service provided through our hosting platform (Amazon Simple Email Service).
- Text-message delivery: Telnyx, our messaging provider, and the wireless carriers that deliver messages.
- Payments and billing: Stripe, which processes payments and holds your payment details under its own privacy policy.
- Website analytics: Google Analytics, provided by Google LLC, which receives the website and application usage information described above. See how Google uses information from sites that use its services.
- Jobsite address lookup (time tracking): the U.S. Census Bureau Geocoding Service, which receives only the jobsite street address that office staff type, to estimate the jobsite location. It does not receive employee names, time records or employee location readings.
- Address suggestions (Contractor OS): Google Places, part of Google Maps Platform, provided by Google LLC. While office staff type an address, such as a jobsite address, WeBuilt’s servers send the characters typed so far to Google, which returns suggested U.S. street addresses; when one is chosen, Google returns its full address and map location, which WeBuilt saves with the record. The requests come from WeBuilt’s servers, not your browser, and do not include your name, email, company, employee details, time records or employee location readings. Google processes these requests under its own terms and privacy policy.
- AI model provider: when a Studly feature answers, words, plans or summarizes with a language model, WeBuilt’s servers send the question and the relevant records directly to Anthropic, PBC (Claude models, through Anthropic’s API), which processes them as our subprocessor under its commercial terms to produce the response. Anthropic does not use this information to train its models. Each company’s use is capped daily. WeBuilt does not use your information to train AI models. We will update this list before we add or change a provider.
An Account Owner can connect supported business software, such as QuickBooks Online, to Contractor OS. WeBuilt reads those records so Studly can answer from them and does not change anything in that software. Other connections, calling and texting with a contractor’s own customers, and call recording are not offered yet. When any of them is offered, we will describe the providers and the information involved here before it is switched on.
We may also disclose information if required by law, to protect our rights or the safety of others, or as part of a merger or acquisition, in which case this policy continues to apply to it.
How long we keep information
- Form submissions: for as long as needed to respond to you and manage our relationship, or until you ask us to delete them.
- Text-message consent and opt-out records: for at least four years after your most recent opt-in or opt-out, so we can demonstrate consent and honor opt-outs. If you opt out, we keep your number on a do-not-text list so we don’t message you again.
- Workspace records: for as long as the company’s plan is active, and for at least ninety days after it ends so the company can return or take a copy; after that we may delete them. A verified Account Owner can ask for earlier deletion.
- Time records, including the location reading saved with each punch: as part of the employer’s workspace records, for as long as the employer’s plan is active and at least ninety days after it ends, as described for workspace records above. The employer’s own retention decisions and legal duties to keep or delete employee time records are the employer’s.
- Account, billing and Terms acceptance records: for the life of the account and afterwards for as long as tax, accounting and other laws require, or as needed to evidence the agreement.
- Security and audit records (for example sign-in, access and change logs): for a limited period needed for security, troubleshooting and compliance.
Your choices and requests
- Reply STOP to any WeBuilt text to stop texts.
- Block or delete cookies in your browser settings, or install the Google Analytics opt-out browser add-on, to stop Google Analytics from measuring your visits.
- Email hello@getwebuilt.com to access, correct, or delete your information, or to stop other communications. We’ll respond within a reasonable time.
- Account Owners can ask for a copy of their company’s workspace records in a reasonably usable electronic format (we aim to fulfil requests within thirty days), or for deletion of the workspace, by emailing us from the Account Owner’s address. We verify the request before acting on it. Deletion is subject to legal, billing, security and backup retention requirements.
- Employees using time tracking should ask their employer for access to, or correction of, their time records and location readings; the employer can correct punches in Contractor OS. You can also decline or withdraw the device’s location permission at any time. Contact us if you are unable to reach your employer.
- Authorized Users (people invited into a company’s workspace) should ask their company owner about records held in that workspace; contact us for your own account information.
Security
We use encrypted connections (HTTPS), server-side access controls and workspace isolation, and we limit access to WeBuilt personnel who need it. No system is perfectly secure, but we work to protect your information. If we become aware of unauthorized access to information in our systems, we will notify the affected Account Owners by email without undue delay after we have discovered and investigated the incident and determined that it is reportable, consistent with the laws that apply; our internal target is to do so within 72 hours of that determination where feasible.
Children
WeBuilt is a business service for contractors. It isn’t directed to children under 18, and we don’t knowingly collect their information.
Changes
If we change this policy, we’ll update the version and effective date above and keep the history below. For material changes we notify Account Owners by email and in the app at least thirty days before they take effect. Material changes to how we handle text-message information won’t apply to your existing consent without notice.
| Version | Effective | Summary |
|---|---|---|
| 2.7 | November 21, 2026 | Updates who may use Contractor OS time tracking: included in Crew Max, available as a paid add-on on monthly Crew at $19/month, and otherwise only by a recorded grant, including a grant already recorded. Does not change what location data is collected, when it is collected, or how long it is kept. |
| 2.6 | November 12, 2026 | Discloses Studly by text: a WeBuilt customer may link their mobile phone to Studly; we record the number, the linked account and the texts exchanged, and send questions and the relevant records to the AI model provider to answer them. |
| 2.5 | November 4, 2026 | Discloses facts an Account Owner or administrator asks Studly to remember: saved in the workspace, used in later conversations for that company, and sent to the AI model provider. |
| 2.4 | November 3, 2026 | Names Anthropic, PBC as the AI model provider: Studly’s questions and the relevant records go directly to Anthropic’s API (Claude models) as WeBuilt’s subprocessor, replacing models made available through our hosting platform. Anthropic does not use this information to train its models, and each company’s use is capped daily. Says that an Account Owner can connect supported business software, such as QuickBooks Online, which WeBuilt reads and does not change. |
| 2.3 | November 2, 2026 | Discloses address suggestions: while office staff type an address in Contractor OS, WeBuilt sends what has been typed to Google Places (Google Maps Platform) to suggest U.S. street addresses and, for the chosen one, its full address and map location. Employee details, time records and employee location readings are not sent. |
| 2.2 | October 28, 2026 | Discloses the jobsite address lookup: when office staff enter a jobsite address, WeBuilt may send that address to the U.S. Census Bureau Geocoding Service to estimate the jobsite location. Employee GPS readings collected at Clock In and Clock Out are not sent to that service. |
| 2.1 | October 27, 2026 | Adds optional Contractor OS time tracking, switched on only for companies that ask for it and accept this version: employee time records and a single location reading taken only when an employee taps Clock In or Clock Out, with no continuous or background location tracking. |
| 2.0 | October 24, 2026 | Adds Contractor OS accounts and workspaces, billing through Stripe, Terms of Service acceptance records, Studly and AI model providers, retention periods, security-incident notice, and export and deletion requests. |
| 1.1 | October 24, 2026 | Adds Google Analytics to website usage and the provider list. |
| 1.0 | October 10, 2026 | First policy: website forms, text-message consent and the WeBuilt text program. |
Contact
WeBuilt LLC · 2340 N 400 W Unit E1, Provo, UT 84604 · hello@getwebuilt.com · getwebuilt.com