Terms of Service

1. Introduction

These Terms of Service ("Terms") govern your use of Brick-by-Brick.ai ("the Service"), a Knowledge Architecture Builder operated by Spacious Enterprises LLC ("Spacious," "we," "our," "us"), a Wyoming limited liability company.

By creating an account, purchasing a build, or using the Service in any way, you agree to be bound by these Terms. If you do not agree, do not use the Service.

2. Definitions

• "Knowledge Architecture" means the structured, interconnected representation of your company's knowledge across 11 dimensions, built through the Service and delivered to the Customer as downloadable files.
• "Knowledge Architecture Builder" means the Brick-by-Brick Service that produces Knowledge Architectures. References throughout these Terms to "the Service" mean the Knowledge Architecture Builder.
• "Build" means a single execution of the Brick-by-Brick build process, resulting in a Knowledge Architecture for one company.
• "Knowledge Architecture Package" means the three deliverable files: an Interactive HTML Package, a Machine-Readable JSON Export, and a Knowledge Architecture Guide, which the Customer downloads and owns permanently.
• "Customer" or "Architect" means the individual or entity that creates an account and purchases a Build.
• "Confirmation Session" means the interactive session during which the Customer confirms, corrects, and supplements pre-collected data. The Confirmation Session includes two sub-phases: Phase 4a (Dimension Cards) and Phase 4b (Temporal Memory Pass).
• "Source Readiness Gate" means the interactive review screen presented before data confirmation begins, reporting the status of every source the system attempted to read.
• "Data Sources" or "Connectors" means third-party platforms the Customer optionally connects to the Service during the Build process (including but not limited to Salesforce, HubSpot, Google Drive, Jira, Slack, Gmail, QuickBooks, and additional connectors listed in the Data Connector Intelligence Manifest).
• "Update" means a subsequent Build that refreshes an existing Knowledge Architecture, available in three tiers based on the scope of change detected.
• "Sub-Processor" means a third-party service provider engaged by Spacious to deliver the Service, as enumerated in the Sub-Processor List.

3. The Service

Brick-by-Brick.ai is a Knowledge Architecture Builder. The Service:

• Researches the Customer's company from publicly available sources
• Optionally collects data from Customer-authorized Data Sources
• Reports the status of every source the Customer provided through the Source Readiness Gate
• Structures collected data into an 11-dimension framework
• Guides the Customer through an interactive Confirmation Session, including a dedicated Temporal Memory Pass
• Generates analytical tables, an Interdependency Graph, temporal intelligence analysis, and a Gap Report
• Delivers the completed Knowledge Architecture as three downloadable files: HTML Package, JSON Export, and Knowledge Architecture Guide

The Service orchestrates 28 specialized agents through a 9-phase pipeline. Each pre-collection source is reported to the Architect with a status indicator before the build proceeds, ensuring transparency about what data was successfully retrieved and what was not.

The Service is a knowledge structuring tool, not an advisory service. The Knowledge Architecture surfaces, structures, and connects information. It does not make recommendations, provide advice, or make decisions. The Customer is solely responsible for all decisions made using information from their Knowledge Architecture.

4. Account Registration & Authentication

To use the Service, you must:

• Create an account with a valid email address
• Register a Passkey (WebAuthn biometric authentication) as the primary login method, OR register with email and password as a fallback method for devices without passkey support
• Provide accurate company identification information
• Be authorized to represent the company for which the Knowledge Architecture is being built

Sessions are managed via secure httpOnly cookies with a 2-hour expiry. Sessions can be revoked on logout. Passwords, when used, are hashed with bcrypt at 12 rounds. You are responsible for maintaining the security of your device, passkey, and password. Spacious is not liable for unauthorized access resulting from compromised devices or credentials.

5. Purchases and Payment

5.1 Pricing

All services are prepaid. Prices are in USD and may change for future purchases; the price in effect at the time of purchase applies.

• Initial Build — $499: A complete Knowledge Architecture build for one company across 50 categories, delivered as three files (HTML Package, JSON Export, Knowledge Architecture Guide). Build session takes 3-4 hours, including a dedicated Temporal Memory Pass.
• Scope Assessment — $59: Upload your existing Knowledge Architecture for comparison against fresh data. Produces a Change Report. Fee credited toward any Update tier.
• Tier 1 Update (Minor, under 15% change) — $99: Changes auto-applied. New Package delivered.
• Tier 2 Update (Moderate, 15–40% change) — $249: Targeted re-confirmation for affected dimensions. New Package delivered.
• Tier 3 Update (Full Rebuild, over 40% change) — $479: Complete re-collection and full confirmation. New Package delivered. Discounted from $499 for returning Architects.

5.2 What Is Included in an Initial Build

• Automated intelligence gathering from public sources
• Data collection from Customer-authorized Data Sources (if connected)
• Source Readiness Gate reporting the status of every source attempted
• Structuring into the 11-dimension framework
• Interactive Confirmation Session including Dimension Cards (Phase 4a) and Temporal Memory Pass (Phase 4b)
• Generation of analytical tables (standard + temporal)
• Construction of the Interdependency Graph with temporal edges
• Gap analysis across all 11 dimensions (including temporal gaps)
• Delivery as three downloadable files: HTML Package (interactive, offline-capable), JSON Export (machine-readable, powers MAIA Decision OS), and Knowledge Architecture Guide
• A Health Report, Gap Report, and Temporal Intelligence assessment

5.3 What Is Not Included

• MAIA Decision OS access (available separately at maiaos.ai)
• Custom integrations beyond supported connectors
• Consulting, advisory, or strategic recommendations

5.4 Payment

Payment is processed through Stripe at the time of purchase. All payments are in USD. All services are prepaid with no exceptions.

5.5 Refunds

If the Service fails to deliver a completed Knowledge Architecture due to a technical failure on our part, the Customer is entitled to a full refund. Refund requests must be submitted within 30 days of purchase. Refunds are not available for:

• Dissatisfaction with the content or completeness of the Knowledge Architecture
• Failure to complete the Confirmation Session
• Issues arising from the Customer's Data Sources
• Customer-side disconnections or session abandonment

6. Delivery, Ownership, and Data Deletion

6.1 Build-and-Own Delivery

Upon completion of a Build, the Knowledge Architecture is delivered to the Customer as three downloadable files:

• Interactive HTML Package: A self-contained HTML file with seven sections (Briefing, Dimensions, Graph, Tables, Gap Analysis, Health, Metadata). Works offline in any browser. Includes an Executive Intelligence Summary, interactive D3 interdependency graph, and a Company Timeline embedded within the D11 Temporal dimension.
• Machine-Readable JSON Export: A structured JSON file containing the complete Knowledge Architecture data per the KA JSON Schema Spec, suitable for integration with MAIA Decision OS, business intelligence tools, or custom systems.
• Knowledge Architecture Guide: A companion document explaining how to use the KA, connect it to MAIA Decision OS, and keep it current through Scope Assessments and tiered updates.

6.2 File Ownership

Once downloaded, the Knowledge Architecture Package files belong entirely to the Customer. The Customer may store, copy, share, back up, print, and use the files in any manner they choose. Spacious Enterprises has no access to, control over, or claim on the downloaded files.

6.3 Data Retention — Hybrid Model

All Customer build data is deleted from Spacious systems on the hybrid retention schedule described below. This includes the temporary build database, all data points, edges, analytical tables, gap reports, source status records, and any connector-derived data. After deletion, Spacious holds zero company-specific Customer data.

Hybrid retention schedule:

• Build data is retained for the longer of (a) 48 hours from session start, or (b) 24 hours after delivery — whichever applies later
• This guarantees a minimum 24-hour download window after build completion, regardless of when during the 48-hour session the build finishes
• Maximum total retention: 72 hours from session start
• Incomplete builds that do not reach delivery are deleted at the 48-hour session expiration mark

Deletion verification and audit trail:

• After data deletion, automated read-back verification confirms deletion completed successfully
• A 7-year compliance audit trail records every deletion event (build identifier, event type, timestamp, verification result) without retaining any company intelligence data
• This audit trail supports GDPR Article 30 records-of-processing requirements and similar regulatory frameworks

Deletion is irreversible — the downloaded files are the Customer's only copy.

6.4 Customer Responsibility

The Customer is solely responsible for:

• Downloading their Knowledge Architecture Package within the applicable retention window
• Storing and backing up their downloaded files
• Any loss of data resulting from failure to download before deletion

6.5 Zero Customer Data Holding

Spacious Enterprises does not store, retain, or have ongoing access to the Customer's company-specific data after the hybrid retention window. During the Build process, data is temporarily held in an isolated per-Customer database with encrypted session caching (destroyed on the hybrid retention schedule above). Deletion is automated with read-back verification.

After delivery and deletion, Spacious retains only the Customer's account information (email, name, company name, industry, purchase history) and build operational metadata (timestamps, completion status, aggregate statistics) — never the Knowledge Architecture content.

Clarification: "Zero Customer Data Holding" refers to data stored on Spacious Enterprises infrastructure. During the build, company data is processed by Anthropic's Claude API (routed via Cloudflare's AI Gateway service) and by Cloudflare's infrastructure. Anthropic may retain data for up to 30 days for trust and safety purposes per their data processing terms. Anthropic does not use API data for model training. For the complete list of sub-processors, see the Sub-Processor List. The Service also includes rate limiting on all endpoints to prevent abuse; users who exceed rate limits will receive temporary access restrictions.

6.6 Build Session Expiration

Build sessions that are not completed within 48 hours of initiation are automatically expired. All associated data — including session cache, uploaded document extractions, connector tokens, and pre-collected intelligence — is permanently deleted upon expiration. The Architect is responsible for completing the build session within the 48-hour session window. Expired sessions cannot be recovered or extended.

Build sessions that complete and deliver within the 48-hour window receive a download retention extension per the hybrid schedule in Section 6.3: deliverables remain available for the longer of 48 hours from session start or 24 hours from delivery. In no case shall total data retention exceed 72 hours from session start.

7. Data Sources and Third-Party Services

7.1 Optional Connectors

The Customer may optionally authorize connections to up to 26 third-party Data Sources. By authorizing a connector, the Customer grants the Service read-only access and confirms they have authority to grant such access. Write access is limited to cloud storage delivery, restricted to a Brick-by-Brick/{Company} folder. All OAuth tokens are encrypted at rest using AES-256-GCM encryption and are revoked with providers when build data is deleted.

7.2 Metadata-Only and Aggregate-Only Connector Access

For certain connector categories, the Service enforces restricted access at multiple architectural layers:

• Gmail, Outlook, Slack, and Microsoft Teams: The Service extracts metadata only — never message content, subject lines, or calendar event descriptions. Enforced at OAuth scope selection, agent prompt engineering, and automated output verification.
• BambooHR and similar HR connectors: The Service extracts aggregate organizational structure only — never individual employee names, emails, social security numbers, dates of birth, or other personally identifying information. Enforced at agent prompt engineering and automated output verification.

7.3 Third-Party Terms

The Customer's use of Data Sources is governed by the respective third-party's terms of service. Spacious is not responsible for changes to, outages of, or access limitations imposed by third-party Data Sources.

7.4 Connector Revocation

The Customer may revoke any Data Source connection at any time.

8. Source Transparency

Before any build proceeds to the Confirmation Session, the Customer is presented with a Source Readiness Gate reporting the status of every source the Service attempted to read. Each source resolves to one of five states: COLLECTED (essential data successfully retrieved), PARTIAL (essential data retrieved with optional enrichment data unavailable), EMPTY (source authorized but contained no data), LIMITED (some essential data retrieved but below threshold), or BLOCKED (essential data unavailable with explanation).

The Customer can click any source for detailed information about what was expected, what was retrieved, what was missing, and any recovery action available. This transparency is enforced architecturally: every source is required to produce a status record, and the system prevents builds from advancing without Customer review of the Source Readiness Gate.

The Service makes no claim that data was collected from sources where collection was incomplete or unsuccessful. Those gaps are surfaced explicitly.

9. Data Accountability

The Service operates on a "no silent losses" principle. Every data point the Service collects, processes, or renders is accounted for at every stage of the build. This commitment is enforced through automated verification at multiple layers of the system, not solely through process or policy. For full detail on how this commitment is enforced across source collection, card confirmation, graph construction, and deliverable generation, see Privacy Policy §7.

10. AI Processing

10.1 Use of AI Models

The Service uses AI language models provided by Anthropic (Claude Opus 4.6 and Claude Sonnet 4.6) to research, structure, and analyze company knowledge. LLM API requests are routed through Cloudflare's AI Gateway service for observability and rate-limit resilience.

For certain analytical agents that normally use Claude Opus, if Anthropic's API rate limits are temporarily exceeded during high-concurrency periods, the AI Gateway may automatically fall back to Claude Sonnet to ensure build completion. Both models are Anthropic's and operate under identical data processing terms.

10.2 AI Limitations

AI-generated content may contain inaccuracies, incomplete information, or misinterpretations. The Confirmation Session exists specifically so the Customer can verify, correct, and supplement AI-generated findings. The Customer is responsible for reviewing and validating all information in their Knowledge Architecture.

10.3 No AI Advice

The Service does not provide business advice, strategic recommendations, legal guidance, financial counsel, or any other form of professional advice.

10.4 Prompt Injection Protection

Company data provided during the build is processed within structural boundaries that separate data from system instructions. AI agents treat all company-provided content as data, not as commands. Potential injection patterns are flagged in the Knowledge Architecture export metadata for downstream consumers.

11. Intellectual Property

11.1 Customer Data

The Customer retains full ownership of all company-specific data provided to or generated through the Service.

11.2 Service IP

Spacious retains ownership of the Service itself, including the Brick-by-Brick platform, the 11-dimension framework, the 9-phase build methodology, the 28-agent architecture, the RVV governance framework, the no-silent-losses enforcement patterns, and all associated intellectual property.

11.3 Industry Knowledge Architectures

Industry Knowledge Architectures are owned by Spacious Enterprises and are shared across customers in the same industry. No customer-specific data is included.

12. Prohibited Uses

The Customer may not:

• Use the Service to build Knowledge Architectures for companies they do not represent
• Attempt to reverse-engineer, decompile, or extract the Service's underlying technology
• Use the Service to collect competitive intelligence without authorization
• Resell, sublicense, or redistribute the Service or its outputs
• Use the Service in any manner that violates applicable law

13. Build Integrity and Anti-Abuse

13.1 One Build, One Company

Each purchased Build is for a single company. The company identified during Onboarding is locked for that Build.

13.2 Build-to-Payment Binding

Each Build is bound to a specific payment transaction. One payment authorizes one Build for one company.

13.3 Company Lock

Once the Customer confirms the company identification during Onboarding, the company legal name, industry classification, and identification record are immutable for that Build.

13.4 Duplicate Build Detection

If a Knowledge Architecture already exists for the identified company under a different account, the Service will notify the Customer during Onboarding.

13.5 Correction Monitoring

The Service monitors Confirmation Session patterns for anomalous behavior and reserves the right to pause or terminate a Build if anomalous patterns are detected.

13.6 Consequences of Misuse

Violation may result in immediate termination of the Build, forfeiture of payment, suspension or termination of the Customer's account, and restriction from future purchases.

14. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, SPACIOUS ENTERPRISES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING LOSS OF PROFITS, DATA, BUSINESS, OR GOODWILL, OR ANY DAMAGES ARISING FROM RELIANCE ON INFORMATION IN THE KNOWLEDGE ARCHITECTURE.

SPACIOUS'S TOTAL LIABILITY FOR ANY CLAIM ARISING FROM OR RELATED TO THE SERVICE SHALL NOT EXCEED THE AMOUNT PAID BY THE CUSTOMER FOR THE SPECIFIC BUILD GIVING RISE TO THE CLAIM.

15. Indemnification

The Customer agrees to indemnify and hold harmless Spacious Enterprises, its officers, employees, and agents from any claims, damages, or expenses arising from the Customer's use of the Service, violation of these Terms, or unauthorized Data Source connections.

16. Service Availability

Spacious makes reasonable efforts to maintain Service availability but does not guarantee uninterrupted access. The Service may be temporarily unavailable for maintenance, updates, or circumstances beyond our control.

17. Termination

17.1 By the Customer

The Customer may close their account at any time. Closing an account does not affect any Knowledge Architecture files the Customer has already downloaded — those files belong to the Customer permanently.

17.2 By Spacious

Spacious may suspend or terminate a Customer's account for violation of these Terms, with notice when practicable. If a Build is in progress at the time of termination, the Customer will receive their Knowledge Architecture Package before account closure where technically feasible.

18. Modifications to Terms

Spacious may update these Terms from time to time. Material changes will be communicated via email. Continued use of the Service after notification constitutes acceptance.

19. Governing Law

These Terms are governed by the laws of the State of Wyoming, United States. Any disputes shall be resolved in the courts of Wyoming.

20. Regional Compliance

Spacious Enterprises honors data protection rights established under applicable law, including the EU/UK GDPR and the California CCPA/CPRA. For details on the rights available to you, the legal basis on which we process personal information, the international data transfer mechanisms we rely on, and how to exercise your rights, see Privacy Policy §9.

21. Language

Brick-by-Brick is provided exclusively in the English language. All platform interfaces, Knowledge Architecture outputs, agent-generated content, Help Center documentation, and legal agreements are authored, delivered, and supported in English only.

While Brick-by-Brick is accessible from non-English-speaking countries, it is the sole responsibility of the Architect to possess sufficient proficiency in written and spoken English to understand, interpret, and act upon all platform content. This includes but is not limited to: pre-collected data points presented for confirmation, Knowledge Architecture deliverables, Temporal Intelligence questions, Financial Intelligence questions, Source Readiness Gate status information, compliance disclosures, and all terms governing use of the platform.

Spacious Enterprises LLC does not provide translation services, multilingual support, or localized versions of any platform content. No claim arising from an Architect's inability to understand English-language content shall constitute grounds for dispute, refund, or liability.

For the complete governing framework on language of service, see the English Language Policy.

22. Related Legal Documents

These Terms of Service are part of a framework of legal documents that together govern the use of Brick-by-Brick:

• Privacy Policy — How we collect, use, and protect information
• Policy Agreement — The build-time contract summarizing key commitments
• Sub-Processor List — Current sub-processors with data categories and locations
• English Language Policy — English-only service delivery framework
• How We Protect Your Data — Technical overview of security and compliance posture

Where the documents cross-reference each other, each document's authority on its subject matter controls. These Terms of Service control on matters of account registration, payment, prohibited uses, limitation of liability, indemnification, termination, and governing law.

23. Contact

Spacious Enterprises LLC
Email: [email protected]
Legal: [email protected]
Privacy: [email protected]
Website: brick-by-brick.ai