> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/help-and-resources/legal.md).

# Legal

Built By DAO publishes an application while its housing, investment, and contract programs have separate availability and approval requirements. The entity form, governing jurisdiction, signed agreements, service providers, and production contract addresses must be finalized through the appropriate approval process.

## One product, several legal relationships

The model may involve a non-operating holding layer, cohort operating entities, property-specific entities, registered businesses, a private investment vehicle, members, residents, contributors, and service providers. Their exact relationships are not created merely by a dashboard role, NFT, token balance, or governance vote.

The applicable signed agreement controls:

* entity ownership and governance rights;
* leases, occupancy, property purchase, and financing;
* contribution, employment, contracting, safety, and intellectual-property terms;
* investment subscriptions, eligibility, disclosures, and transfer limits; and
* privacy notices, provider terms, and dispute procedures.

## What the contracts do

Smart contracts enforce defined on-chain permissions and state: membership, credentials, token provenance, bounded spending, custody, Treasury rails, proposals, voting, vesting, bookings, business ledgers, and related lifecycle rules. They do not independently decide the legal effect of those records.

EQTBLT records its source: Contribution EQTBLT or Rent rebate EQTBLT. It has no guaranteed cash price, automatic redemption right, employment classification, tenancy right, property title, or investment return. BLTBY is a separate, future transferable-token workstream and is not bundled into the private investment offering.

## Minimal professional boundary

The platform should preserve accurate facts and records, then let approved agreements and qualified professionals determine legal, accounting, labor, housing, securities, and tax treatment. It should not create speculative classification engines, member tax calculators, automatic forms, or legal conclusions simply because a risk could exist.

## Current documents

* [Terms of Service](/help-and-resources/terms-of-service.md)
* [Privacy Policy](/help-and-resources/privacy-policy.md)
* [Contributor participation](/help-and-resources/contributor-agreement.md)
* [Governance and compliance boundaries](/governance/compliance.md)
* [Smart Contract Catalog](/developers/contracts.md)

Final launch documents must identify the actual operating entity, jurisdiction, providers, effective dates, contact channels, and approved dispute process before they are presented as binding terms.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.builtbydao.com/help-and-resources/legal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.