Legal

AI & Data Disclaimer

Last updated: March 27, 2026

LocalCode, LLC (“LocalCode,” “we,” or “our”) structures and presents publicly available legislative data — municipal codes, ordinances, statutes, and related government documents — to make legal research faster and more systematic. This page explains how that data is sourced and processed, and what you should know before relying on it.

1. Data Sources

All legislative content in the LocalCode platform is derived from publicly available government sources, including:

  • Official municipal code publications and their online portals
  • Third-party code publishers (e.g., Municode, eCode360) that host official government-adopted versions
  • State legislative databases and official government websites
  • Directly published PDFs and ordinance documents from municipal clerks and planning departments

LocalCode does not generate, author, or modify the substance of any legislative text. We structure, link, and organize what governments have published.

2. Editorial and Computational Processing

To build the legislative chain and code library products, LocalCode applies computational processing to raw legislative documents, including:

  • Parsing and structuring code sections from source documents
  • Identifying ordinance adoption references and linking them to the code sections they created, modified, or repealed
  • Classifying code sections into topic areas and use types
  • Tracing enabling authority linkages between local, state, and constitutional sources

This processing involves automated classification and linkage systems. While we work to ensure accuracy, automated systems can make errors — particularly in jurisdictions with complex amendment histories, multi-layered ordinances, or non-standard formatting.

3. AI-Assisted Features

Certain features of the LocalCode platform use AI-assisted processing to identify patterns, suggest classifications, or surface relevant code sections. These features are clearly labeled within the product.

AI-generated outputs are not independently verified legal opinions. They are research aids designed to help professionals identify relevant material faster — not to substitute for professional judgment or primary source review.

LocalCode does not use your queries, research sessions, or uploaded documents to train AI models without explicit consent.

4. Coverage Limitations

LocalCode does not cover every jurisdiction. Data coverage varies significantly:

  • Deep coverage: Full legislative chain tracing, ordinance linkage, and code library for select jurisdictions (currently Austin, TX as part of the pilot program)
  • Standard coverage: Structured code library without full chain tracing
  • No coverage: Many jurisdictions are not yet available. The platform indicates coverage levels per jurisdiction.

Absence of a jurisdiction from LocalCode is not a statement about the existence, validity, or accessibility of that jurisdiction's laws.

5. Currency and Timeliness

Legislative data changes frequently. Ordinances are adopted, amended, and repealed on an ongoing basis. LocalCode updates its data on a regular cadence, but:

  • There may be a lag between when a jurisdiction adopts a change and when it appears in LocalCode
  • Interim or emergency ordinances may not be reflected immediately
  • Pending legislation is not represented unless explicitly labeled

Always check the “last updated” date on any code section and verify against the official source for time-sensitive matters.

6. Not Legal Advice

Nothing in the LocalCode platform constitutes legal advice. LocalCode is a research and data platform, not a law firm. Use of the platform does not create an attorney-client relationship.

You should always consult qualified legal counsel before making decisions based on legislative data, including zoning determinations, code compliance assessments, and transactional due diligence.

7. Your Responsibility

You are responsible for independently verifying any data from the LocalCode platform before relying on it in legal, regulatory, or transactional contexts. This includes:

  • Checking primary sources (official code publications, ordinance documents, government websites)
  • Confirming currency with the relevant municipal or legislative body
  • Applying professional judgment to the completeness and accuracy of your research

8. Contact

Questions about data sources, coverage, or accuracy? Reach our data team at data@localcode.ai.