BuildOS customer terms
This product draft is not effective. The business fields below have deliberately been left empty. It does not authorize a charge or replace a signed customer agreement. Public registration remains gated until the exact product document version is approved.
1. The agreement and service scope
BuildOS is the CRM and operations product presented by HAT Building Technologies. The contracting legal entity and customer must be identified in an approved order form before a paid service starts. That form specifies the supported modules, authorized users, subscription period, fees, implementation work, support arrangements and any negotiated terms. A separate signed agreement takes precedence where it expressly addresses the same subject.
These product terms concern authenticated workspaces, customer-facing forms and shared documents. The public HAT website has separate website terms. A feature catalog or demonstration does not promise that every connector or workflow is available for every company.
2. Accounts and workspace administration
Users must provide accurate details, verify control of their email address where required, keep passwords and authenticators private, and promptly report suspected unauthorized access. Workspace owners control invitations, roles, records and connected accounts within the service's permission boundaries. The customer must authorize those administrators and the information it uploads or shares.
One company cannot obtain another company's access by using its email domain. Workspace administration does not confer authority to recover a platform administrator's account or a shared account belonging to other workspaces. Losing a second factor may require an identity-checked support process; a password-reset email does not remove MFA.
3. Trials, pricing and connected services
The currently described trial is free while pricing is finalized, has no stated trial end date, and requires no payment details. There is no automatic charge or conversion to a paid subscription. Any future paid plan requires the customer's express agreement to the applicable price and terms. Cancellation, refunds, taxes and renewal rules must be completed in the approved order form before billing begins.
Connected Nylas, Google, Microsoft, Zoho, Intuit QuickBooks, DocuSign, HubSpot and address-routing services operate under their providers' terms and availability. Customers must have appropriate accounts and approve the necessary access. Integrations can require company-specific configuration and may be limited to explicitly supported operations. Do not connect a production account for testing without a controlled test plan.
Calculations and project visualizations support the customer's work and require review by appropriately qualified people before construction, contractual, payment or safety decisions. Current Engineering/accounting workflows retain specialized configuration; CRM onboarding does not certify them for a new company.
4. Customer data and acceptable use
The customer retains its rights in the data it supplies and authorizes the limited processing needed to provide, secure, support and recover the agreed service. It must have authority to process contacts, documents, mailbox content and other personal information. BuildOS software and product materials remain their respective owners' intellectual property.
Use the service lawfully. Do not attempt to bypass permissions, access another workspace, upload malicious content, send unsolicited bulk messages or interfere with availability. Do not store payment-card details in ordinary CRM fields or share credentials outside the restricted Credential Vault. Account and integration secrets must not be included in support messages.
The BuildOS product privacy draft describes data categories, optional processors, sharing and security boundaries. Any required data-processing agreement, international-transfer terms, security commitments and instructions for access, export, retention and deletion must be agreed with the identified contracting parties before commercial use.
5. Support, suspension and ending access
Use Help and setup to prepare a support request. Support contact details, response targets and incident-notification commitments must be completed before a paid service begins. No uptime percentage or round-the-clock support promise is made by this draft.
Access may need to be restricted to contain abuse, an active security incident or a material breach, with notice where practicable. The customer should export required records before ending service. The access period for export, final deletion schedule, backup retention and any legal hold must be agreed in the approved order form; those periods have not been supplied here. Removing a member's access does not automatically erase historical business records.
Liability allocation, warranties, indemnities, governing law and dispute resolution remain subject to authorized legal review and the signed agreement. This draft does not waive rights that cannot lawfully be waived. Material future terms must be presented before requiring acceptance; consent must record the version actually shown.
6. Business fields awaiting approval
- Contracting legal entity
- Registered country and address
- Effective date
- Support and privacy contact
- Governing law and dispute forum
- Cancellation and refund policy
- Customer-data export and deletion periods
- Support and availability commitments