Terms of Service.

These Terms govern your use of Architecture Studio (“Arch Studio”, “we”, “us”), operated by Alpaca Labs, LLC, a Delaware limited liability company, 169 Madison Ave., Suite 15497, New York, NY 10015. Arch Studio is an ALPA product.

By creating an account, connecting Arch Studio to an assistant, or using the hosted service, you agree to these Terms. If you use Arch Studio on behalf of a firm, you confirm you have authority to accept these Terms for that firm, and “you” includes the firm.

Our Privacy & data handling page explains what data we process and how. It is part of how we run the service, and you should read it alongside these Terms.

• Privacy & data handling

Arch Studio gives architects and design firms skills, tools, agents and workflows for architecture and firm work. It works inside an assistant you choose. That assistant, and any external reference sources or tools a workflow calls, are provided by other companies under their own terms and policies. We do not control them and are not responsible for them.

The hosted service is currently a preview. Features may change, be added, or be removed, and we do not yet offer service-level commitments.

Arch Studio comes in two forms:

• The hosted service. A hosted MCP connection you add to an assistant such as Claude or ChatGPT, together with the website, your account, and any firm modules you use (for example, Materials Library). These Terms cover the hosted service.
• The open-source plugin. The public plugin runs locally in Claude Code or Codex with no account. Its code is licensed under its own open-source license (currently MIT), and that license, not these Terms, governs your use of the code. If you use the plugin together with the hosted service, these Terms apply to the hosted part.

• Open-source plugin

• You need an account to use the hosted service. Give accurate information and keep your sign-in secure. You are responsible for activity under your account.
• You must be at least 18 and using Arch Studio for professional purposes.
• The hosted service is organized around firms. Accounts belong to a firm, and a firm’s records are available only to verified members of that firm.
• Firm admins can manage firm settings, including membership and the firm-wide usage data switch. The firm is responsible for who it admits and what its members do in its workspace.
• When someone leaves a firm, the firm, not that person, keeps control of the firm’s records.

Use Arch Studio lawfully and for its intended purpose. We may suspend access or remove content that we reasonably believe breaks these rules.

Do not:

• break the law or infringe anyone’s rights, including intellectual property and privacy rights;
• upload content you do not have the right to use or share;
• access another firm’s data or another person’s account, or try to get around access controls, rate limits, or security measures;
• disrupt, overload, probe, or attack the service or its infrastructure;
• reverse engineer the hosted service, except where the law allows it or where the code is published under an open-source license;
• resell, sublicense, or provide the hosted service to others as your own service without our written agreement;
• use the service to build a competing product by systematically extracting its content or outputs;
• post client documents, confidential project details, credentials, or access tokens in public GitHub issues.

• You own your content. Project files, drawings, documents, prompts, tool inputs, and the records your firm creates (for example, Materials Library records) remain yours or your firm’s. We claim no ownership of them.
• Permission we need to run the service. You give us a limited permission to host, process, and transmit your content only as needed to perform the tools and module operations you or your firm request, and to keep the service secure.
• No training. Stored firm module records are never used for model training, general product improvement, corpus building, or cross-firm analysis.
• Where data lives. The open-source plugin keeps records in your own workspace and stores nothing on our servers. The hosted MCP receives only the inputs supplied to it and stores no project records unless your firm uses a record-holding module. Details are on the Privacy & data handling page.
• Export and deletion. Your firm can request a full portable export of its module records, and deletion of them, by contacting help@architecturestudio.ai.
• Your responsibility. You confirm you have the rights and any client permissions needed to use the content you put into Arch Studio and into your assistant.

Arch Studio uses AI assistants. Their output can be incomplete, out of date, or wrong, even when it cites sources.

• Output is a starting point for qualified review. It is not professional architectural, engineering, legal, code-compliance, zoning, or other professional advice, and it is not a stamped or sealed document.
• Licensed professionals remain fully responsible for any design, specification, code, zoning, life-safety, product, or regulatory decision, and for checking every output against original sources and the applicable law before relying on it.
• Do not rely on output for decisions that affect health, safety, permits, or contracts without that independent professional review.

The hosted service collects bounded usage data linked to a pseudonymous account identifier and, where available, your firm. It does not include your prompts, conversations, tool inputs, project files, outputs, or access tokens. Usage data is on by default. You can turn it off for your account, and a firm admin can turn it off for the whole firm. The open-source plugin honours AS_TELEMETRY_DISABLED=1.

What we collect, how long we keep it, and how to turn it off are described on the Privacy & data handling page. If this section and that page differ, the Privacy & data handling page controls.

• Usage data on the Privacy & data handling page

The open-source plugin is free. The hosted service is currently free for firms during the preview.

If we introduce fees for the hosted service or any module, we will give you notice before they apply to you, and you will be able to stop using the paid part before you are charged. We will not move you onto a paid plan or charge you without your agreement, and we will give at least 30 days’ notice by email before any fee applies to features you already use. Any paid plan will come with its own pricing and payment terms.

• You can stop using Arch Studio at any time and ask us to delete your account by contacting help@architecturestudio.ai.
• We may suspend or end your access if you break these Terms, if required by law, or to protect the service or other users. Where reasonable, we will tell you first.
• We may discontinue the hosted service or a module. If we do, we will give reasonable notice and a way to export your firm’s module records, with at least 30 days’ notice.
• After an account or firm ends, data is handled as described on the Privacy & data handling page. The ownership terms in “Your content and project data”, and the sections “AI output is not professional advice”, “No warranties”, “Limitation of liability”, “Indemnity” and “Governing law and disputes” continue to apply.

The service is provided “as is” and “as available”. To the fullest extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, accuracy, and non-infringement. We do not promise that the service or its output will be uninterrupted, error-free, complete, or suitable for your project.

Some jurisdictions do not allow some of these limits, so they may not all apply to you.

To the fullest extent the law allows:

• we are not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, data, or business, including losses from relying on AI output;
• our total liability for all claims relating to the service is limited to the amount you paid us for the hosted service in the 12 months before the claim (US$0 while the service is free).

You will defend and indemnify Alpaca Labs, LLC against third-party claims arising from your content or from your breach of these Terms.

We may update these Terms as the service changes. For material changes, we will notify account contacts by email (a service notice about terms, separate from Product updates) and update the effective date above, before the change takes effect. We will give at least 30 days’ notice. If you keep using the hosted service after the change takes effect, the updated Terms apply. If you do not agree, stop using the service and delete your account.

These Terms are governed by the laws of the State of New York, without regard to conflict-of-law rules. Disputes will be resolved by binding individual arbitration in New York, New York, and you waive any right to bring or join a class or representative action. Either party may bring an individual claim in small-claims court.

These Terms and the Privacy & data handling page are the whole agreement between you and us about the hosted service, unless your firm has a separate signed agreement with us, which then controls. If any part of these Terms is unenforceable, the rest stays in effect. Our not enforcing a provision is not a waiver. You may not transfer these Terms without our consent; we may transfer them as part of a reorganization or sale of the business.

• Private support, account questions, account deletion, and data export, deletion and privacy requests: help@architecturestudio.ai
• Public product issues: the public GitHub issue tracker (public; keep client information and credentials out)
• Postal: Alpaca Labs, LLC, 169 Madison Ave., Suite 15497, New York, NY 10015

• Private support and privacy requests
• Public issue tracker