Skip to main content
This page states what you are allowed to build with the data, so you do not need to book a call to find out.
This page is a plain-language summary. The Terms of Service, Section 21, is what actually governs, and it controls if the two ever disagree.

The short version

Why the text is unrestricted

The statutory, regulatory and constitutional text is US primary law, and US primary law cannot be copyrighted. Georgia v. Public.Resource.Org, Inc., 590 U.S. 255 (2020) settled it, holding that even annotations prepared under contract for a legislature are uncopyrightable government edicts. We claim no ownership of that text and nothing in our terms restricts your use of it. What is licensed to you is the compilation: the schema, the citations, the hierarchy, the cross-references, the metadata and the assembled corpus. That is the work product, and the restrictions below apply to it alone.
Check this with any vendor whose corpus derives from a commercial legal publisher’s codification. That layer can carry rights the raw text does not, so ask where each jurisdiction was sourced from.

What you keep if you leave

Retrieved through the API

Responses you cached during a paid term are yours to keep. There is no deletion obligation, and you may keep showing them to your customers. That includes the citations, hierarchy and cross-references those responses carry, because a cached answer is not usable without them.

Delivered in bulk

The rule differs here on purpose. On termination or expiry of a bulk arrangement you delete stored copies of our compilation within 30 days. The corpus itself is the deliverable, so permanent retention would let a single period buy it outright.You still keep anything you had independently retrieved through the API, the public-domain text, anything obtained under the Open US Law licenses, and Output already embedded in work product you delivered to your clients.
The public-domain text carries no restriction either way, and never did. Retention is not a license to redistribute. Whatever you keep, you may not resell our compilation as a standalone data product, nor use it to build a competing legal-data API or database.

What you may not do

Without a separate signed agreement, you will not:
  • systematically extract, bulk-download, scrape or accumulate the corpus for any purpose other than powering your own end-user product
  • resell, sublicense or redistribute the underlying legal data or our compilation as a standalone dataset, database, feed or API
  • offer the API, or a service substantially derived from it, under your own or a third party’s brand
  • use the API or its Output to build, train or improve a product that competes with our legal-research, statute-retrieval or legal-data API services
  • reverse engineer the API or attempt to derive its models or training data
  • exceed or circumvent your plan’s rate limits or credit allowance, including by spreading access across accounts
Each of those is available under a written agreement, so they are commercial terms and not matters of principle.

Attribution

Unless your plan waives it, display “Legal data by Vaquill AI”, linked to vaquill.ai, somewhere a user can reasonably find it in any product where the Output is shown to your end users. A footer, an about page or a data-sources page is fine. One credit per product, not one per response. The console gives you the exact snippet. It is not required for internal or back-office use where nothing is shown outside your organization, or for evaluation. Attribution can be waived commercially. Talk to us.

The open dataset

Separately from the paid API, the whole corpus is published as Open US Law:
  • Public-domain text: no restriction
  • Our compilation: CC BY-NC 4.0 from snapshot v2026.09, CC BY 4.0 before that
  • The ingestion pipelines: Apache-2.0
CC BY 4.0 snapshots (before v2026.09) already grant commercial use, redistribution, remixing and model training, irrevocably. From v2026.09 the compilation is CC BY-NC 4.0: free for research, teaching, legal aid and other non-commercial use, with commercial use under a separate license. The public-domain text stays unrestricted either way, and what you retrieve through the API is covered by the Terms, Section 21.

Still unsure?

Describe what you want to build and we will tell you which of the above it lands in, in writing, before you commit to anything. contact@vaquill.ai
Last modified on October 24, 2026