BuildPod OS Legal
Terms of Service
Terms governing access to and use of BuildPod OS by customers, organizations, admins, invited users, workers, and field users.
Agreement to terms
These Terms of Service govern access to and use of BuildPod OS by customers, organizations, owners, admins, invited users, workers, and other authorized users. By accessing BuildPod OS, creating an account, accepting an order, or using the service on behalf of an organization, you agree to these terms for yourself and, where applicable, the organization you represent.
Eligibility and authority to bind company
You must be legally able to enter into these terms. If you use BuildPod OS for a company, contractor, organization, or other entity, you represent that you have authority to bind that entity or that you are using BuildPod OS under the authority of someone who does.
Accounts and registration
Account information must be accurate and kept current. You are responsible for maintaining the confidentiality of credentials, securing devices used to access BuildPod OS, and promptly notifying BuildPod LLC if you believe access has been compromised.
Organizations/workspaces
BuildPod OS is organized around customer organizations, workspaces, jobs, crews, assets, staging, inventory, maintenance, proof, and related operational records. Organization owners and admins control access within their organization and are responsible for configuring users, roles, and operational workflows appropriately.
Owner/admin authority and responsibility
Owners and admins may invite users, assign roles, manage settings, review operational data, and control parts of the organization workspace. Owners and admins are responsible for determining who should have access and for reviewing whether access remains appropriate.
Invited users, workers, and field access
Invited users, workers, and field users may receive access to operational information needed for field use. Field access is intended for operational field workflows and does not automatically grant billing, finance, admin, or office-control permissions.
Field crew access policy
Field crew access is included for operational field use. Admin, owner, manager, operations, finance, and office-control seats are billable seats. High-cost usage such as AI, storage, media processing, OCR, transcription, and external integrations may be governed by tier limits, usage limits, or fair-use policies.
Subscriptions, billing, trials, beta, and paid conversion
Paid subscriptions, pilot access, trials, Founding Operator access, and custom plans are governed by the applicable order, written agreement, or accepted platform flow. BuildPod OS will not silently convert a pilot, beta, or unpaid evaluation into paid billing unless explicitly accepted in writing or through a clear platform flow.
Customer data ownership
As between you and BuildPod LLC, the customer retains ownership of customer data entered, uploaded, imported, or generated by authorized users in the customer’s organization, subject to the limited rights needed for BuildPod LLC to provide, secure, support, maintain, improve, and operate BuildPod OS.
BuildPod IP ownership and service license
BuildPod LLC owns BuildPod OS, ATLAS-related product logic, software, designs, interfaces, workflows, templates, documentation, trademarks, and other intellectual property. During an active authorized relationship, BuildPod LLC grants a limited, revocable, non-transferable right to access and use BuildPod OS for internal business operations according to these terms.
Use restrictions and Acceptable Use Policy
- Do not use BuildPod OS unlawfully or to violate rights of others.
- Do not attempt unauthorized access, probing, scraping, reverse engineering, or bypassing roles, permissions, billing boundaries, or entitlement limits.
- Do not upload harmful code or misuse BuildPod OS in a way that harms the service, other customers, or infrastructure.
- Use is also subject to the Acceptable Use Policy.
Third-party services and integrations
BuildPod OS may interoperate with third-party services, hosting providers, payment processors, email providers, storage systems, AI providers, or other integrations when enabled. Third-party services may have their own terms and availability, and BuildPod LLC is not responsible for third-party services outside its control.
Data imports, migrations, and professional services
Data imports, migrations, and professional services may be self-serve, assisted, paid, or separately scoped. Customers are responsible for source data accuracy and for reviewing imported data before relying on it operationally. White-glove migration or professional services require written scope and agreement.
AI/ATLAS advisory nature
ATLAS and AI-assisted features are advisory and orchestration-oriented. BuildPod OS remains the operational system of record. AI outputs may be incomplete, inaccurate, or context-dependent and must be reviewed by authorized humans before operational reliance.
Operational readiness disclaimers
BuildPod OS helps organize readiness signals and operational workflows, but it does not make field, safety, dispatch, staffing, financial, legal, tax, payroll, insurance, or compliance decisions for customers. Customers remain responsible for operational decisions and field execution.
No legal/accounting/payroll/tax/safety certification advice
BuildPod LLC is not a law firm, CPA firm, payroll provider, tax preparer, insurer, safety certifier, or compliance authority. BuildPod OS may help organize information, but customers should consult qualified professionals where legal, accounting, payroll, tax, insurance, safety, or compliance advice is required.
Service availability and maintenance
BuildPod LLC may update, maintain, modify, suspend, or discontinue parts of BuildPod OS. The service may be unavailable during maintenance, incidents, provider outages, or events outside BuildPod LLC’s reasonable control.
Suspension and termination
BuildPod LLC may suspend or terminate access for non-payment, security risk, misuse, violation of terms, legal requirement, or risk to the service or other users. Customers may request termination according to the applicable order, subscription, or written agreement.
Confidentiality
Each party may receive non-public information from the other. Confidential information should be used only for the relationship and protected with reasonable care. Confidentiality obligations do not apply to information that is public, independently developed, lawfully received from another source, or required to be disclosed by law.
Warranty disclaimer
BuildPod OS is provided on an as-is and as-available basis except where a separate written agreement states otherwise. BuildPod LLC disclaims implied warranties to the maximum extent permitted by law, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement.
Limitation of liability
To the maximum extent permitted by law, BuildPod LLC will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, or business interruption. Any aggregate liability will be limited as stated in the applicable written agreement or, if no limit is stated, to amounts paid to BuildPod LLC for the service during the applicable period.
Indemnification
Customers are responsible for their data, users, operational decisions, and use of BuildPod OS. Customers agree to defend and indemnify BuildPod LLC from claims arising from customer data, unlawful use, misuse, or violation of these terms, except to the extent caused by BuildPod LLC’s own wrongful conduct.
Governing law and venue
These terms are governed by the laws of Michigan, United States, without regard to conflict-of-law rules. Venue is in Michigan, United States, unless a separate written agreement states otherwise.
Changes to terms and contact
BuildPod LLC may update these terms as the service evolves. Material changes will be posted or communicated through reasonable means. Questions may be sent to em@buildpodllc.com.
Contact: em@buildpodllc.com
