Legal

LODE Terms of Service

Effective: September 8, 2026

These Terms replace the Terms of Service last updated July 9, 2026.

1. Who we are and what this agreement covers

1.1 The parties. These Terms of Service ("Terms") are a contract between EASYBUILDS LLC, a Delaware limited liability company doing business as LODE ("LODE", "we", "us"), and the person or organization that creates an account or uses the Services ("you", "Customer").

1.2 What the Services are. The "Services" are the LODE website and web application at lode.build and its subdomains, the LODE API and processing services, DOC, the email and PDF outputs LODE produces, and every page a person reaches through a link LODE generates (shared sets, issuance shares, guest review rooms, bid rooms, the contractor portal, punch lists, permit-status pages and the compiler).

1.3 Acceptance. You accept these Terms by ticking the acceptance box at signup, by clicking "I agree" or a similar control, or by using the Services. If you sign in with Google or Microsoft, you accept these Terms the first time you sign in. If you use the Services on behalf of a firm or other organization, you confirm that you have authority to bind it, and "you" means that organization.

1.4 Related documents. Our Privacy Policy (lode.build/privacy) explains how we handle personal information and forms part of these Terms. Our Security page (lode.build/security) is a plain-language description of our practices and our current list of service providers; it is informational, and where it differs from these Terms or the Privacy Policy, those control. For MOTHER LODE customers, Section 23.3 sets the order of precedence.

1.5 Business use. The Services are built for architecture, engineering and construction professionals and are offered for business use. They are not offered to consumers for personal, family or household purposes.

2. Professional responsibility

Please read this section.

2.1 LODE is a document-control tool, not a professional. LODE compiles, tracks, compares, distributes and helps you administer construction documents. LODE does not provide architectural, engineering, contracting, cost, scheduling, code-compliance, legal, financial or other professional advice or services, and nothing the Services produce is a professional opinion.

2.2 The licensed professional stays responsible. The architect, engineer or other design professional of record, and any contractor or owner using the Services, remain solely responsible for their own professional and contractual obligations: the content, accuracy, completeness and coordination of their documents; every decision made using the Services; and compliance with codes, standards and licensing rules.

2.3 Forms and certifications. Some features produce documents that a professional signs or certifies, for example pay-application forms based on AIA G702/G703, change orders, bid tabulations and award summaries, and certificates of substantial or final completion. LODE fills in and formats these documents from the information you and your team enter. LODE does not certify, approve or verify anything in them. The person who signs or issues such a document is responsible for it.

2.4 Your record is your record. Construction documents are legal records and may be evidence in disputes. LODE holds your documents to provide the Services, on the retention rules in Section 10. LODE is not your records custodian, is not responsible for meeting your document-retention, legal-hold or regulatory obligations, and will delete data as these Terms describe. Keep your own copies. The export features exist for this purpose.

2.5 DOC is assistance, not advice. DOC's output can be wrong, incomplete or out of date. It is a starting point for a professional to check, not a substitute for professional judgement. See Section 12.

3. The Services

3.1 What LODE does. LODE lets you bring drawing and specification issuances into a project record; detects sheets and specification sections; tracks each sheet's revisions across issuances; compiles the current set and revision outputs; detects references between sheets; lets your team view, mark up, measure and comment on documents, including in real time; runs the project lifecycle from planning through bidding, construction administration, financials and closeout; provides a scratch canvas ("Sketch Paper"); provides a firm-level library, lessons-learned, contact and QA/QC hub; provides DOC; and lets you share documents and workflows with people outside your firm through links. The user guide at lode.build/guide describes the product as built. Features may be added, changed or removed over time (Section 14.2 covers changes that reduce what you have paid for).

3.2 Your responsibilities. You are responsible for the devices, browsers and internet access you use, for the accuracy of what you upload and enter, for reviewing what LODE produces (including sheet detection, revision comparison, reference detection and OCR results, which can be incomplete or wrong) before relying on it, and for the people you give access to.

3.3 Desktop product. The web application is designed for desktop browsers at 768 pixels wide or more and does not run on narrower screens. Guest pages (contractor portal, punch list and permit status) are usable on a phone.

4. Eligibility and accounts

4.1 Who may use LODE. You must be at least 18 years old and able to enter a binding contract. The Services are intended for users located in the United States. If you use them from elsewhere, you do so on your own initiative and are responsible for local law.

4.2 Your account. Give us accurate registration information and keep it current. Keep your credentials confidential. You are responsible for everything done under your account, whether or not you authorized it, until you tell us at support@easybuilds.com that your account may have been compromised. One person, one login: do not share a login.

4.3 Third-party sign-in. You may sign in with a Google or Microsoft account. We receive your basic profile information (name and email) as permitted by that provider. You can revoke that access in your Google or Microsoft account settings.

4.4 Email verification and communications. We may require you to verify your email address. You agree to receive transactional and service email from us (invitations, deletion notices, payment problems, export links, terms changes). Marketing email, if we ever send it, will have an unsubscribe link.

5. Organizations, authorized users, guests and staff access

5.1 Organizations. A firm uses LODE as an organization with one Owner, any number of Admins (subject to seats) and Members. The Owner is the contracting party for the organization's subscription and is the only person who may change the plan, buy overage or Archive, export the whole account, transfer ownership or delete the organization. Admins manage projects and people; they cannot change or remove the Owner. Members work on projects they are given. Ownership may be transferred to another member, who must first hold a subscription in their own name.

5.2 Seats. Each plan includes a number of seats (Section 6.1). A seat is one named person. Seats may be reassigned when someone leaves; they may not be shared between people. Inviting someone into your organization, or letting them join automatically by verified email domain, uses a seat. Guests (Section 5.5) do not use seats.

5.3 Projects belong to the organization. Projects created inside an organization are the organization's records. They stay with the organization when a member's account is removed or deleted. Personal projects created outside any organization belong to that individual account.

5.4 You are responsible for your users. You are responsible for your Admins, Members and Guests complying with these Terms and for the permissions you give them. Collaborators can view, edit, mark up, export or share content according to those permissions.

5.5 Guests. You may give people outside your organization (contractors, bidders, consultants, owners, reviewers) access to specific documents or workflows through links LODE generates. Guests do not need a LODE account. By opening a link, a Guest agrees to use it only for the purpose it was shared, not to share it further without your permission, and to comply with Sections 11, 15 and 24 as they apply to Guests. You control who receives a link, and you can revoke a link at any time. Links expire by default: bid-room links end at award; contractor portal and punch list links expire 90 days after issue; issuance share links may be revoked or set to expire by you. Transmittal-style shares (issuance shares and compiled-set links) show exactly the files sent, not later revisions; live review links can follow a sheet's revision lineage. Files a Guest uploads through the contractor portal or punch list become part of your project record and count against your storage allowance. We record each Guest's name and email (where given), IP address, browser and open and download activity as part of your project's transmittal and audit record; see the Privacy Policy.

5.6 LODE staff access. A small number of LODE staff can access accounts and their content to provide support you ask for, to investigate abuse, security incidents or billing problems, to comply with law, and to operate the Services. Staff access is logged. We do not browse your documents for any other reason.

6. Plans, pricing and billing

6.1 Plans. Self-serve plans are Solo, Field and Studio; MOTHER LODE is a custom plan agreed in writing. Every plan includes the whole product; plans differ in capacity. The current allowances are shown at lode.build/pricing and in the app, and on the Effective Date are:

SoloFieldStudioMOTHER LODE
Monthly price$49$199$599 (list)custom
Annual price (billed once a year)$499$1,999$5,999 (list)custom
Active projects (per organization)31530custom
Seats15unlimitedcustom
Storage100 GB500 GB, pooled across the firm2 TB, pooled across the firmcustom
DOC messages per month500 per seat300 per seat4,000 pooled across the firmcustom

Project caps count active projects across the whole organization. Projects in cold storage (Section 10.4) do not count against project slots; their storage counts at one quarter. Storage counts your uploaded source files (not the compiled outputs LODE generates) and includes files Guests upload. Some DOC capabilities are available only on Field and above or Studio and above (Section 12.6). Studio's unlimited seats carry a fair-use limit of 40 people collaborating live in one document at the same time.

6.2 Overage. Additional capacity is available at the rate published on the pricing page. Each overage unit adds one active project and 20 GB of storage for as long as you keep it. Overage is billed with your subscription and can be added or removed from Settings; a unit removed part-way through a month is not prorated. MOTHER LODE overage is set by contract.

6.3 Early-adopter Studio price. For a limited time, Studio is offered at $399 per month (or $3,999 per year) to the first 25 Studio subscriptions. That price is yours for as long as your Studio subscription runs without interruption. It is not a limited-time introductory rate and it does not step up to list price. If your subscription ends for any reason, whether you cancel it, it lapses for non-payment, or you move to Archive, the early-adopter price is permanently forfeited, and any later Studio subscription is at the then-current list price ($599 per month or $5,999 per year on the Effective Date). A forfeited place is not offered to anyone else; there are 25 in total, ever. The offer may be withdrawn for new subscribers at any time and does not change the price of anyone already subscribed.

6.4 Auto-renewal. Subscriptions renew automatically at the end of each billing period (monthly or annual) at the then-current price for your plan unless you cancel before the renewal date (Section 8.1). You authorize us and our payment processor to charge your payment method for subscription fees, overage and Archive fees on a recurring basis.

6.5 Payment processing. Payments are processed by Stripe. We never see or store full card numbers. Stripe handles your payment details under its own terms and privacy policy. A valid payment method is required to hold a paid plan. None is required to create an account or to start the trial (Section 7.1).

6.6 Renewal notices. Your renewal date and amount are shown in the billing portal available from Settings. For annual subscriptions we email the Owner at least 30 days before the renewal date with the renewal date, the amount, and how to cancel. Stripe may also send invoice notices on our behalf.

6.7 What you are charged. The price shown at checkout and in Settings, and the allowances shown in the app, are what apply to you. If a number in these Terms and the app disagree, the app is right for existing customers and we will correct the Terms.

6.8 Price changes. We may change prices. We will give you at least 30 days' notice by email before a change applies to you, and it will take effect at your next renewal after that notice. The end of the early-adopter period (Section 6.3) is not a price change. If you do not accept a price change, cancel before it takes effect.

6.9 Taxes. Prices shown include any applicable sales or use taxes, which LODE calculates and remits where required.

6.10 Refunds. Fees are non-refundable, and we do not give credits for partial periods, unused seats, unused DOC messages or unused storage. We may, at our discretion, refund or credit charges caused by our billing errors or by a technical failure on our side.

6.11 MOTHER LODE. MOTHER LODE plans are sold by written order form or agreement, which sets the price, allowances, retention and any service commitments. Section 23.3 explains which document controls.

7. Trial

7.1 What you get. Every new account starts with a 30-day trial of Solo's capabilities, limited to one active project and one seat. No payment method is required to start the trial. Nothing is charged during the trial.

7.2 During the trial. From day 20 the app shows how many days remain and lets you choose a plan and add a payment method at any time. Choosing a plan before the trial ends starts your subscription immediately at the end of the trial, with nothing charged until then.

7.3 When the trial ends. When the 30 days end, the account is locked: you can still sign in, choose a plan and add a payment method, buy Archive (Section 9) or export your data, but you cannot view, edit or add to your projects until you subscribe. Nothing is charged unless you subscribe.

7.4 After the trial. We keep your trial data for 30 days after the trial ends. If by then you have not subscribed or bought Archive, we permanently delete it (Section 10.6). We will email you before the trial ends and again before the data is deleted.

7.5 One trial per person or firm. We may refuse or end trials that are created to get around this limit.

8. Cancellation, non-payment and downgrades

8.1 Cancelling. You can cancel from Settings (through the billing portal) at any time. Cancellation stops future renewals; you keep full access until the end of the period you have paid for. No refund is given for the remainder of the period.

8.2 After the paid period. When the paid period ends the account is locked in the same way as a cancelled trial (Section 7.4): sign in, choose a plan, buy Archive, or export. There is no free tier and no read-only mode.

8.3 Data after cancellation. If you cancel, we keep your data for 30 days after your paid period ends. If by then you have not resubscribed or bought Archive, we permanently delete the account's projects and files (Section 10.6). We will email the account Owner before deletion. This 30-day clock is started by a cancellation and by nothing else; a failed payment does not start it (Section 8.4).

8.4 Failed payment. If a renewal charge fails, Stripe retries it over its normal retry window and we email the Owner. Access continues during that window. If the retries fail and the subscription becomes unpaid, the account is locked (Section 8.2): reads and writes stop. Your data is NOT deleted. Overdue is not cancellation, so the 30-day deletion clock in Section 8.3 does not start, and we do not delete an account for non-payment. The data stays until you cancel, delete the account yourself, or leave Archive (Section 9.5). Paying the outstanding amount or updating your payment method in Settings unlocks the account with everything intact.

8.5 Downgrades. If you move to a smaller plan (or remove overage) and you have more active projects, seats or storage than the new plan allows, you must archive projects or remove people to fit before the account works normally again; the app will show what is needed. Downgrades take effect at the next renewal unless Stripe's portal shows otherwise.

8.6 No pause. There is no pause or hold option. If you need to stop paying and keep your data, use Archive (Section 9).

9. Archive: paid retention when a plan ends

9.1 What Archive is. Archive keeps an account's full record, every project, file, revision and record, for as long as the Archive fee is paid, instead of the data being deleted after the 30-day window in Sections 7.4 and 8.3.

9.2 Download-only. An account on Archive cannot view, edit, share, upload to or otherwise use its projects. Two things are available: a full export of the account (Section 10.8), and restoring the account to a paid plan, which brings everything back as it was. There is no read-only browsing on Archive.

9.3 Price. Archive is priced by the plan you are leaving: $9 per month after Solo, $29 after Field, $49 after Studio (or $99, $299 and $499 per year). MOTHER LODE retention is set by contract. Archive renews and is cancelled like any subscription (Sections 6.4 and 8.1).

9.4 Buying Archive. The Owner can switch to Archive from Settings while on a paid plan, or during the 30-day window after a trial or paid period ends.

9.5 Leaving Archive. If you cancel Archive, the 30-day retention in Section 8.3 runs and the data is then permanently deleted. If an Archive payment fails and is not resolved within Stripe's retry window, the account is locked as in Section 8.4 and the data is NOT deleted; paying the outstanding amount restores it. Restoring to a paid plan at any time while the data still exists ends Archive.

9.6 Archive is the only "stop paying, keep data" state. See Section 8.6.

10. Your content: ownership, licence, retention, deletion and export

10.1 You own your content. Everything you and your users upload or enter (drawings, specifications, PDFs, photos, files, markups, comments, records, contacts, project data) is "Customer Content". You own it. We claim no rights in it beyond the licence in Section 10.2. We do not sell it, do not use it to train any AI model, and do not use it to build anything other than your Services.

10.2 Licence to us. You grant LODE a non-exclusive, worldwide, royalty-free licence, sublicensable only to the service providers in Section 13, to host, store, copy, process, transmit, render, display, compile and create derivative outputs from Customer Content solely to provide, secure, support and improve the Services for you, including the features you choose to use (compiled sets, exports, sharing, DOC as permitted by your AI settings). The licence lasts as long as we hold your content under this Section and then ends, except for de-identified data under Section 11.4.

10.3 Your promises about content. You promise that you have the rights needed to upload Customer Content and to give us this licence; that your use of the Services, including sharing with Guests and enabling DOC, does not breach any confidentiality, licensing or professional obligation you owe to clients, consultants or others; and that Customer Content does not infringe anyone's rights, break the law, or contain malware.

10.4 Project cold storage. You can move a finished project to cold storage. Its files stay part of your record, do not count against project slots, count at one quarter against storage, and can be restored. Restores from deep archive take time, typically 12 to 48 hours, and restored compiled sets return to cold storage after 30 days unless you keep them out. Cold storage is a feature of every paid plan and is different from the Archive plan in Section 9.

10.5 Deleting projects, files, markups and accounts. When you delete a project, a document, a file or a markup it goes into a 30-day recovery window during which you can restore it. When you delete your account (from Settings) your subscription is cancelled, you receive an email with a link to cancel the deletion, and you can cancel it within the 30 days. What is deleted depends on the account. If your account does not belong to an organization, everything goes after the same 30-day window: your login, your profile, your personal projects and their contents. If your account belongs to an organization, we delete your login, your profile and anything personal to you, and you leave the organization, but the work you contributed to the organization's projects stays with the organization as its record, together with the attribution identifying who did it (Sections 5.3 and 10.6). An organization Owner may delete the organization, which deletes every project belonging to it, and every member's work in them, the same way.

10.6 Permanent deletion. When a recovery or retention window ends we permanently delete the data from our production systems: uploaded PDFs and originals, processed sheets, tiles, compiled sets, cold-storage copies, project files, DOC summaries and annotations, and the database records for the project, including records about the people you shared with. No copies are kept, except: (a) de-identified metrics that cannot be linked to you or your projects (Section 11.4); (b) a permanent record that an account or project existed and was deleted, with no names, emails or content; (c) copies in our routine backups until those backups are replaced in the normal course (Section 14.4); (d) what we must keep for legal, tax, security or billing reasons; and (e) the attribution on work a deleted account contributed to a project, which is part of that project's record and is described in Section 10.10. When an account is fully purged we also delete its login, profile and export bundles.

10.7 Export before it is too late. It is your responsibility to export what you need before a retention window ends. We do not restore deleted data after permanent deletion and cannot restore individual items from backups.

10.8 Export. An Owner can export the whole account from Settings at any time while on a paid plan, during a retention window, or on Archive. The export includes every project, file, compiled set, annotation, markup, comment and revision-history record the account owns, with records and metadata in machine-readable form and a manifest of its contents. Individual projects, sheets, compiled sets and files can also be downloaded from the app. Download links in export emails expire after 7 days.

10.9 Legal requests. If we receive a subpoena or other legal demand for your content we will, where the law allows, tell you before responding so you can object. See the Privacy Policy.

10.10 Attribution on work you contributed. Work done inside a project is part of that project's record, and a record of who did what is part of it: on a construction project it can matter years later which person answered an RFI, issued a revision or marked up a sheet. So where an account has contributed to a project, we retain the contributor's display name on that work as part of the project record, including after the account is deleted. The name shown on the account and an internal identifier stay attached to the documents, comments, markups and revision entries it created, while the login, the profile, the contact details and everything else personal to the account are deleted. This does not depend on whether the account belongs to an organization. An account with no organization can still be assigned to, and work on, a project owned by one, and the same reason for keeping the record applies. If you want attribution removed from an organization's records, ask the organization: it controls those records and we act on its instruction. The organization can also delete its entire record, which removes the attribution with it. Where the work was contributed to no other party, a request to remove attribution is considered individually.

11. Intellectual property, outputs, feedback and product-improvement data

11.1 Our property. The Services, the software, the interface, the guide, and the LODE, DOC, MOTHER LODE, Sketch Paper and Loder names and marks belong to EASYBUILDS LLC or its licensors. LODE is a trademark of EASYBUILDS LLC (application pending). We give you the licence in Section 11.3 and keep all other rights. You may not copy, modify, resell, sublicense, reverse engineer or build a competing product from the Services except where the law allows despite this clause.

11.2 Outputs are yours. Compiled sets, Field Sets, Revision Records, sheet indexes, revision logs, exports, generated forms and DOC output produced from your Customer Content are part of your Customer Content and belong to you, subject to Section 2.3 and Section 12. The templates, layouts and code that produce them remain ours.

11.3 Your licence to use the Services. Subject to these Terms and payment, we grant you, your authorized users and your Guests a limited, non-exclusive, non-transferable, revocable licence to use the Services for your internal business purposes during your subscription and any retention or Archive period.

11.4 Product-improvement data. We keep de-identified, aggregated data about how the Services perform (processing times, sheet counts, error types, feature use). This data contains no file content, project names or personal information and cannot be linked back to you. Separately, LODE retains corrections you make to detected sheet numbers and titles, together with the text read from the title block, to improve reading on your own projects. These corrections are not used to improve reading for other customers.

11.5 Feedback. If you send us ideas or suggestions, we may use them without obligation or attribution.

12. DOC (AI features)

12.1 What DOC is. DOC is an AI assistant built into LODE. It can summarize what changed between issuances, annotate sheets and specification sections with change notes, answer questions about your firm's projects and about a project's record, read specification text, read a region of a drawing you select, review submittals against the specification, and search the web when a question needs outside information. DOC is powered by Anthropic's Claude models through Anthropic's API. DOC is provided as a beta feature and will change (Section 15.4).

12.2 You control what DOC can read. DOC's access is set at the account level by the Owner in independent permissions: a master switch, the general assistant, project information, phase documents (submittals, RFIs, change proposals), drawing information (sheet numbers, titles, disciplines, revisions), specifications (specification text), and full drawings (extracted drawing text and images). A project-level switch can turn DOC off for a particular project regardless of the account setting, for clients who forbid AI on their work. New accounts start with the master switch on, the general assistant on and phase documents on; project information, drawing information, specifications and full drawings are off until the Owner turns them on. Nothing from a class you have not enabled is sent to Anthropic.

12.3 What is sent to Anthropic. When you use a DOC feature, LODE sends Anthropic what that feature needs, limited to the classes you have enabled. Depending on the feature and your settings this can include:

  • the text of your question and the conversation so far;
  • text extracted from drawing sheets and, for change annotations, the previous and new text of a sheet or section;
  • a rendered image of the region of a drawing you select and ask about;
  • images you attach to a question (up to four per message);
  • specification section text and the specification index;
  • excerpts of submittal documents, for DOC Review;
  • project information: project names, numbers, phases, types, client names, issuance names and dates, sheet numbers and titles, revision summaries, sketch summaries;
  • the project's team and contacts directory (names, companies, roles, emails and phone numbers you entered), contracts data, the decision log, the phone log, and your firm's lessons learned with their authors' names, so DOC can answer whole-record questions;
  • schedule, permit, bidding, construction-administration and financial records when you ask about them.

LODE does not send your login credentials or payment information, and does not send whole PDF files. When DOC uses web search, your question (or a search derived from it) is sent to a search service through Anthropic. Under Anthropic's API terms, data submitted through the API is not used to train Anthropic's models. Anthropic's own retention and safety practices are set out in its terms; we cannot change them.

12.4 DOC output. DOC output is generated automatically and may be inaccurate, incomplete, out of date or wrong in ways that look convincing. It is assistance for a professional to check, not professional advice, and not a certification, review or approval by LODE. You must review DOC output before relying on it or passing it on. DOC Review findings are suggestions until a person on your team adopts one, and adopted findings are that person's comments. Section 2 applies to everything DOC produces.

12.5 DOC logs. LODE stores your DOC conversations so you can return to them, and keeps usage records to meter your allowance and to investigate abuse or errors. Conversations are personal to the member who had them and are not part of the account's record. If the account does not belong to an organization they are deleted with it. If it does, they are retained under Section 10.10 and stay private: no other member of the organization can read them, then or afterwards.

12.6 Plan and allowance. DOC messages are metered monthly per seat (Solo, Field) or pooled across the firm (Studio); the app shows the remaining count when you are near the limit. Some capabilities need a higher plan: specification reading is available on Field and above; drawing and region questions are available on Studio and above. Features labelled "beta" or "preview" in the app are subject to Section 15.4. We may change the models we use.

12.7 Third-party data in answers. Web-search results and other outside information DOC quotes belong to their owners and may be inaccurate. We are not responsible for them.

13. Service providers, data location, security and confidentiality

13.1 Service providers ("subprocessors"). We use the following companies to run the Services. Each processes data only on our instructions and under confidentiality and security obligations. The current list is kept at lode.build/security and, on the Effective Date, is:

ProviderWhat it does
SupabaseDatabase, authentication and file storage
VercelHosting for the web application; web analytics and performance monitoring
RailwayHosting for the processing services and job queue
Amazon Web ServicesObject storage (S3), cold storage (S3 Glacier) and archive storage classes
CloudflareObject storage (R2) in some deployments
StripePayments, subscriptions, invoices and sales-tax calculation
AnthropicDOC (AI), only as described in Section 12
LiveblocksReal-time presence, cursors and live collaboration rooms (display names, presence and cursor positions)
ResendTransactional email
PostHogProduct usage analytics
SentryError reporting
UpstashRate limiting
Google, MicrosoftOptional sign-in

We do not use session replay or screen recording. Office-document conversion runs on software we host ourselves; it is not a third party.

13.2 Changes to providers. We may add or replace providers. We will update the list at lode.build/security and, for a new provider that will handle Customer Content, give at least 30 days' notice by email or in-app notice before it starts.

13.3 Data location. We store and process Customer Content in the United States. Providers may have support staff elsewhere under their own commitments.

13.4 Security. We use administrative, technical and physical safeguards designed to protect Customer Content, including encryption in transit and at rest, hashed passwords, least-privilege access controls and row-level security in the database, token-scoped guest links, and logging of staff access. Our current practices are described at lode.build/security. No system is perfectly secure and we do not guarantee that unauthorized access will never occur. We will notify you of a security incident affecting your Customer Content as required by law and without undue delay.

13.5 Confidentiality. We will treat Customer Content and non-public information about your business as confidential, use it only to provide the Services, and disclose it only to the providers in Section 13.1, to your users and Guests as you direct, and as required by law (Section 10.9). You will treat non-public information about the Services (pre-release features, security details, pricing offered to you privately) as confidential. These duties last for as long as we hold the information and for three years after, except that trade secrets stay protected for as long as they are trade secrets.

13.6 Data-processing terms. If you need a data-processing agreement or a security questionnaire completed, email support@easybuilds.com.

14. Availability, support, maintenance and backups

14.1 No service-level commitment on self-serve plans. We work to keep the Services available and fast, but Solo, Field and Studio come with no uptime or response-time guarantee and no service credits. Service commitments, where offered, are set out in a MOTHER LODE agreement.

14.2 Maintenance and changes. We may take the Services down for maintenance, preferably outside US business hours and with notice in the app where practical, and may change or retire features. If we retire a feature that is material to a plan you have paid for annually, you may cancel and we will refund the unused portion of that year.

14.3 Support. Support is provided by email at support@easybuilds.com during normal business hours; response times are not guaranteed.

14.4 Backups. LODE maintains routine backups of its databases and file storage. Backups are for restoring the Services as a whole, not for recovering individual items you deleted. Deleted data leaves the backups when they are replaced in the normal course.

15. Disclaimers

15.1 As is. TO THE FULLEST EXTENT THE LAW ALLOWS, THE SERVICES, DOC AND ALL OUTPUTS ARE PROVIDED "AS IS" AND "AS AVAILABLE", AND WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

15.2 What we do not promise. We do not promise that the Services will be uninterrupted, error-free or secure; that sheet detection, revision comparison, reference detection, OCR, specification parsing or DOC output will be complete, accurate or fit for your purpose; that outputs will comply with any code, standard, contract or professional requirement; or that stored data will never be lost. You are responsible for reviewing the record LODE builds and for keeping your own copies.

15.3 Third parties. We are not responsible for third-party services you connect or link to (Google, Microsoft, Stripe, websites DOC cites) or for content Guests or other users upload.

15.4 Labelled features. Features marked "beta", "preview", "experimental" or "coming soon" in the app or the guide may be incomplete, may change or be withdrawn without notice, and are provided without any commitment. DOC is provided as a beta feature and will change.

15.5 Some places do not allow these disclaimers. Where the law does not allow a disclaimer, it applies to the fullest extent it does.

16. Suspension and termination

16.1 By you. You may stop using the Services and cancel at any time (Section 8) or delete your account (Section 10.5).

16.2 Suspension by us. We may suspend an account, a user or a link immediately if we reasonably believe it is being used in breach of Section 11 or Section 24 (acceptable use), it presents a security risk to the Services or others, it is subject to a legal demand, or fees are unpaid past Stripe's retry window (Section 8.4). We will tell you why and, where we can, give you a chance to fix the problem. We will lift a suspension when the reason is resolved.

16.3 Termination by us. We may terminate these Terms and your account: (a) immediately for a material breach that is not fixed within 10 days of notice, or that cannot be fixed; (b) immediately if you become insolvent or stop trading; (c) for any other reason on 30 days' written notice, in which case we will refund any prepaid fees for the period after termination.

16.4 What happens on termination. Your licence ends. Sections 10.6 to 10.8 govern your data: unless we terminated for your breach, you get the 30-day retention window and the export features; if we terminated for your breach or for a legal reason, we may shorten or refuse the window where necessary. Sections 2, 10, 11, 12.4, 13.5, 15, 17, 18, 20, 21, 23 and any payment obligations survive termination.

17. Indemnities

17.1 By you. You will defend, indemnify and hold harmless EASYBUILDS LLC and its members, managers, officers, employees and agents from third-party claims, and the resulting damages, costs and reasonable attorneys' fees, arising from: (a) Customer Content or your use of it, including documents you issue, certify or distribute using the Services; (b) your or your users' or Guests' breach of these Terms or of the law; (c) your professional services or the project itself; or (d) a dispute between you and a Guest, client, contractor or other third party.

17.2 By us. We will defend you against a third-party claim that the Services, as provided by us and used as permitted, infringe a United States patent, copyright or trademark or misappropriate a trade secret, and pay the damages and costs finally awarded or agreed in settlement. This does not cover claims arising from Customer Content, DOC output, your combination of the Services with other things, or your use after we told you to stop. If such a claim is made or likely, we may procure the right for you to keep using the Services, modify them so they do not infringe, or, if neither is practical, terminate the affected Services and refund prepaid fees for the unused period. This is our entire liability for infringement claims.

17.3 Procedure. The party seeking indemnity must notify the other promptly, give the indemnifying party control of the defense and settlement (no settlement may admit fault or impose obligations on the indemnified party without its consent), and cooperate at the indemnifying party's expense.

18. Limitation of liability

18.1 No indirect damages. TO THE FULLEST EXTENT THE LAW ALLOWS, NEITHER PARTY IS LIABLE TO THE OTHER FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, BUSINESS, GOODWILL OR DATA, OR PROJECT DELAYS, COST OVERRUNS OR REWORK, ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF ADVISED OF THE POSSIBILITY.

18.2 Cap. TO THE FULLEST EXTENT THE LAW ALLOWS, EACH PARTY'S TOTAL LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICES WILL NOT EXCEED THE GREATER OF (A) THE FEES YOU PAID US IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (B) ONE HUNDRED US DOLLARS ($100).

18.3 Exceptions. Sections 18.1 and 18.2 do not limit: (a) a party's indemnity obligations under Section 17; (b) liability for breach of Section 13.5 (confidentiality); (c) your obligation to pay fees; (d) liability for gross negligence, wilful misconduct or fraud; or (e) any liability that cannot be limited by law.

18.4 Basis of the bargain. These limits are an essential part of the agreement and apply even if a remedy fails of its essential purpose.

19. Export controls, sanctions and government use

19.1 You may not use the Services in violation of US export-control or sanctions laws, and you confirm that you are not on any US government restricted-party list and are not located in an embargoed country. Do not upload data that is controlled under ITAR or other export-control regimes without our written agreement.

19.2 If you are a US federal, state or local government entity, the Services are "commercial computer software" and "commercial computer software documentation" provided on these Terms; if your procurement rules require different terms, contact us before using the Services.

20. Governing law and dispute resolution

20.1 Governing law. These Terms are governed by the laws of the State of Delaware without regard to its conflict-of-law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

20.2 Talk to us first. Before starting any formal proceeding, the party with a complaint will email the other (to us: support@easybuilds.com; to you: the Owner's account email) with a short description of the dispute and what it wants, and both parties will try in good faith to resolve it for at least 30 days.

20.3 Arbitration. If the dispute is not resolved, it will be settled by binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, by a single arbitrator, in New Castle County, Delaware, in English, with hearings by video where the rules allow. Judgment on the award may be entered in any court with jurisdiction. Either party may instead bring an individual claim in small-claims court if it qualifies, and either party may seek an injunction or other equitable relief in court to protect intellectual property or confidential information. Questions about whether this Section 20.3 is enforceable are for a court.

20.4 Costs. Arbitration fees are allocated under the AAA rules.

20.5 No class actions; no jury. TO THE FULLEST EXTENT THE LAW ALLOWS, CLAIMS MAY BE BROUGHT ONLY IN AN INDIVIDUAL CAPACITY AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS, CONSOLIDATED OR REPRESENTATIVE PROCEEDING, AND EACH PARTY WAIVES ANY RIGHT TO A JURY TRIAL.

20.6 Opt-out. You may opt out of Sections 20.3 and 20.5 by emailing support@easybuilds.com within 30 days of first accepting these Terms with the subject "Arbitration Opt-Out", your name, your firm and the account email. Opting out does not affect anything else in these Terms.

20.7 Courts for everything else. For any claim not subject to arbitration, the state and federal courts located in Delaware have exclusive jurisdiction, and each party submits to them and waives any objection to venue.

20.8 Time limit. Any claim must be brought within one year after it arises, unless the law does not allow that limit.

21. Notices, contact, copyright complaints, publicity, assignment

21.1 Notices to us. Legal notices to LODE must be sent by email to support@easybuilds.com.

21.2 Notices to you. We may give you notice by email to the Owner's account address, by a notice in the app, or by posting on lode.build. Keep your email address current.

21.3 Electronic contracting. You agree that clicking, ticking or using the Services is your electronic signature and that electronic notices satisfy any requirement that a notice be in writing.

21.4 Copyright complaints. If you believe content on the Services infringes your copyright, email support@easybuilds.com with: a description of the work; where the material is on the Services; your contact details; a statement that you believe in good faith the use is unauthorized; and a statement, under penalty of perjury, that the notice is accurate and you are authorized to act. We will respond as the law requires and may remove content and terminate repeat infringers.

21.5 Assignment. You may not assign or transfer these Terms without our written consent, except to a successor of your whole business who agrees to be bound. We may assign them to an affiliate or a successor in a merger, acquisition or sale of assets, and will tell you if we do.

21.6 No third-party beneficiaries. Only you and we have rights under these Terms; Guests get only what Section 5.5 gives them.

21.7 Publicity. We may identify you by firm name and logo as a LODE customer on our website and in sales materials unless you tell us not to at support@easybuilds.com. We will not describe your projects without your written permission.

22. Changes to these Terms

We may change these Terms. For changes that materially reduce your rights or increase your obligations we will give at least 30 days' notice by email to the Owner and by a notice in the app before the new version takes effect; other changes take effect when posted with a new effective date. If you do not agree, cancel before the new effective date. Using the Services after the new effective date means you accept the new Terms. Changes do not apply to a dispute that arose before the new effective date.

23. General terms

23.1 Entire agreement. These Terms, the Privacy Policy and any order form or written agreement for MOTHER LODE are the whole agreement between us about the Services and replace any earlier terms, proposals or understandings. Terms on a purchase order or vendor portal do not apply.

23.2 Changes must be in writing. Except as Section 22 allows, these Terms can be changed only by a written agreement signed by both parties (email exchange counts for MOTHER LODE order forms if it says so).

23.3 Order of precedence. If there is a conflict: a signed MOTHER LODE agreement or order form controls over these Terms for that customer; these Terms control over the Privacy Policy on commercial matters and the Privacy Policy controls on personal-information matters; both control over the Security page and the guide, which are informational.

23.4 Independent parties. We are independent contractors. Nothing here creates a partnership, joint venture, agency or employment.

23.5 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control (natural disaster, epidemic, war, terrorism, civil unrest, labour dispute, government action, power or internet failure, or failure of a third-party service), except that this does not excuse payment obligations.

23.6 Severability and waiver. If any part of these Terms is unenforceable it will be enforced to the extent permitted and the rest stays in force. Not enforcing a right is not a waiver of it.

23.7 Interpretation. Headings are for convenience. "Including" means "including without limitation". Section references are to these Terms. "Effective Date" means the date shown at the top of these Terms.

24. Acceptable use

You, your users and your Guests may not:

  • use the Services for anything unlawful, or to infringe or misappropriate anyone's rights;
  • upload malware, or anything that interferes with or disrupts the Services or the networks and providers behind them;
  • probe, scan or test the security of the Services without our written permission, or attempt to access accounts, projects or data you are not authorized to see;
  • share logins, share a seat between people, or use links, tokens or Guest access beyond the scope they were given;
  • circumvent plan limits, meters, expiries or access controls;
  • scrape, crawl, bulk-download or use automated means to access the Services other than the export features and any API we publish;
  • copy, modify, translate, reverse engineer, decompile or create derivative works of the Services, or use them to build or benchmark a competing product, except where the law allows despite this clause;
  • resell, rent or provide the Services to third parties as a service bureau (sharing your project record with your own Guests is fine);
  • use DOC to produce content that misrepresents a professional's stamp, seal, signature, certification or opinion, or present DOC output as a professional's work without that professional's review;
  • upload personal information you have no right to share, or data subject to export controls or special regulatory regimes (for example, protected health information or classified information) without our written agreement;
  • send spam or unsolicited messages through the Services, including through transmittals and share links;
  • use the Services in a way that breaches your obligations of confidentiality to a client or others.

We may investigate suspected violations and take the actions in Section 16.

Annex: summary of retention windows

Informational. The Sections control.

EventWhat happens right awayData kept forThen
Delete a project, file, sheet or markupEnters recovery; can be restored30 daysPermanently deleted
Delete your account (no organization)Subscription cancelled; email with cancel link30 days (cancellable)Everything permanently deleted: login, profile, projects and their contents
Delete your account (in an organization)Subscription cancelled; email with cancel link; you leave the organization30 days (cancellable)Login, profile and anything personal permanently deleted; your contributed work and its attribution stay with the organization
Organization deletes its accountEvery member is notified30 daysThe organization's entire record is deleted, including every member's work in it
Trial endsAccount locked: choose a plan and add a payment method, buy Archive, or export30 days after the trial endsPermanently deleted unless you subscribed or bought Archive
Cancel a paid planFull access until the paid period ends, then locked30 days after period endPermanently deleted unless you resubscribed or bought Archive
Payment failsAccess continues through Stripe's retry window; then lockedNo deletion clock runsNothing is deleted. The account stays locked and the data stays until you cancel or delete it
On ArchiveDownload-only: full export, or restore to a paid planAs long as Archive is paidCancel Archive, then 30 days, then permanently deleted
Move a project to cold storage (any paid plan)Project leaves active slots; storage counts one quarterFor as long as your plan is paidRestore any time (12 to 48 hours from deep archive)