Terms of Service

The plain-English rules for using FootyCalc — including two things most calculator sites leave vague: whether you may embed our widget commercially, and what we actually permit machines to do with this site.

Effective date: · Last revised:

1. Acceptance of These Terms

By accessing footycalc.com (the "Service"), you agree to be bound by these Terms of Service. If you do not agree, please stop using the Service. The Service is operated by Richard Taylor, sole proprietor, with a mailing address at 1191 Aspen Blvd, Juneau, AK 99801, United States ("we", "us", "FootyCalc").

2. What The Service Is

The Service provides free, web-based square footage calculators and related educational content. All calculations run locally in your web browser: the arithmetic lives in /js/calc-core.js and is executed by your own machine. Submitting dimensions to a calculator does not send those numbers to us.

The Service also publishes machine-readable endpoints on purpose — an embeddable widget, an agent service document, a JSON lookup API, and an MCP server. Section 8 governs their use.

3. Use at Your Own Risk

We strive for accuracy, but our calculators are for informational purposes only. You should independently verify any numbers you rely on for:

Consult a licensed professional (architect, engineer, surveyor, appraiser, or contractor) for decisions of consequence. Where a page shows a waste factor or a coverage rate, that figure is a labeled assumption on the page, not a guarantee from a trade body — read the assumption before you buy material.

4. No Warranty

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

5. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, RICHARD TAYLOR AND FOOTYCALC WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING FROM YOUR USE OF THE SERVICE. OUR TOTAL AGGREGATE LIABILITY WILL NOT EXCEED USD $50.

6. Intellectual Property: Two Different Licenses

All content on the Service — calculators, articles, design, and code — is owned by Richard Taylor / FootyCalc or licensed to us, and protected by copyright and other laws. Because the embed widget and ordinary site use serve different purposes, they are licensed separately, and the two licenses are stated here rather than left to be inferred.

6.1 Browsing and using the site (default license)

You may use the Service itself for personal, non-commercial purposes. In practical terms: run calculations for your own project, link to any page, and quote a short passage with attribution and a link back. Business use of the pages — for example scraping them into a paid report, or republishing our guides wholesale on a commercial site — is not licensed by this section and needs written permission.

6.2 Embedding the widget (explicit commercial carve-out)

Section 6.1 does not limit the embed product. Through /developers/embed-calculator/ we additionally grant a license to embed our calculator widget in your own website or application, for personal or commercial use. A contractor site, a real-estate listing page, and a monetized blog may all embed it. Conditions of that license:

If this section and section 6.1 ever appear to conflict about an embed, this section governs the embed. That carve-out is deliberate: a "non-commercial only" clause sitting above an invite to use the widget on a business site would be a contradiction we would rather fix in the terms than leave for you to guess about.

6.3 Screenshots and results

You may share or embed screenshots of calculation results you produced — a quote from a job, a post, a bid sheet. That permission covers the picture of your own output; it is not permission to iframe the calculator page itself, which is what section 6.2 is for.

6.4 What we do not allow

7. Third-Party Content and Advertising

The Service displays advertisements through Google AdSense, and only after you click Accept on the cookie banner — see Cookie Policy and Privacy Policy. We are not responsible for the content, accuracy, or privacy practices of any advertiser. Our publisher account is disclosed in /ads.txt so you can check who is actually serving ads on this domain.

Some pages link to standards bodies, supplier data, or reference documents. Those links are for verification; we do not control the pages they point to, and a link is not an endorsement.

8. Automated and AI Access

We publish machine entry points openly, so the honest thing is to publish the rules for them too. Everything below describes what the Service actually does today, not an aspiration.

8.1 What we publish for machines

EndpointWhat it isCredentials
/robots.txtCrawl rules plus a Content-Signal preference line and an Agentmap pointer.None
/llms.txtA plain-text map of the site for language-model context.None
/auth.mdInstructions written for agents, including what not to try.None
/.well-known/api-catalog, /openapi.json, /.well-known/agent-skills/index.jsonDiscovery documents, also advertised as Link headers on the homepage.None
/ai/The service document for agents, served as Markdown.None
/api/agentRead-only JSON lookups (op=list|search|get|help).None
/mcpMCP server (initialize, tools/list, tools/call).None
Accept: text/markdown on any pageContent negotiation: the same page returned as Markdown.None

No public read endpoint requires an account, token, or key. /agent-auth/* returns HTTP 503 by design, so an agent that tries to register is told plainly that there is nothing to register against rather than being silently redirected.

8.2 What we ask automated readers to do

8.3 What we do not authorize

We do not grant a license to ingest this site for training or fine-tuning a model, or to rebuild our pages or widget as your own product. Our crawler preference states it in machine-readable form:

Content-Signal: search=yes, ai-input=yes, ai-train=no

To be equally plain about what that line is worth: Content-Signal is not part of the RFC 9309 robots.txt protocol. Section 2.2.4 of that document says only that "Crawlers MAY interpret other records that are not part of the robots.txt protocol" and that "Crawlers MAY be lenient when interpreting other records", and RFC 9309 itself states that "These rules are not a form of access authorization." So the line is a stated preference, not a technical barrier or a license we can enforce from the edge. If you are building a product that needs a training or redistribution license, email us at the address in section 12 and we will answer honestly rather than let you guess.

9. Changes to the Service

We may add, modify, or remove features at any time without notice. We may also discontinue the Service entirely. Calculator behavior can change between visits: because browsers cache our scripts aggressively for a year, you may be running an older version of the arithmetic than the one on the server for a short window after an update.

10. Changes to These Terms

When we update these terms, we post the new version here and update the "Last revised" date above. We do not send you an email about it — we have no mailing list and hold no email address for you, so continuing to use the Service after changes means you accept the new terms as published on this page. If a change is material, the only honest notice mechanism we have is the date on this page plus the entry in our internal audit ledger.

11. Governing Law

These Terms are governed by the laws of the State of Alaska, United States, without regard to its conflict-of-law rules. Any dispute that cannot be resolved informally will be brought exclusively in the state or federal courts located in Juneau, Alaska.

12. Contact

Questions or legal notices? Email [email protected], or mail:

Richard Taylor
FootyCalc — Legal
1191 Aspen Blvd
Juneau, AK 99801
United States

Worked Example: How One Request Flows

Four concrete paths through this Service, so the terms above are checkable rather than abstract. Steps 1–2 need no network at all; step 4 shows what a machine sees.

  1. A calculation. Enter length 12 and width 12 on /square-footage-calculator/. Your browser multiplies them: 12 × 12 = 144 sq ft. No request leaves the page, because the multiply is in a script your browser already has.
  2. A conversion. The same page converts 144 sq ft to square meters with the exact NIST factor: 144 × 0.09290304 = 13.37803776 m², displayed rounded to 13.38 m². Still zero requests. That is what section 2 means by "runs locally".
  3. An ad request. Only if you click Accept: the page pulls the AdSense script from Google, and Google's ad request carries the usual signals (IP-derived general location, ad cookies). That is why section 7 points at the Cookie Policy instead of pretending ads are invisible.
  4. A machine request. curl -H "Accept: text/markdown" https://footycalc.com/terms-of-service/ returns this page as Markdown; curl https://footycalc.com/.well-known/api-catalog returns the discovery linkset. Both are served without a key, which is why section 8 exists — access we grant openly should come with conditions we state openly.

Every one of those requests also passes through our hosting provider's edge, which is a separate party described in the Privacy Policy; these terms do not change what that party can log.

Sources and How to Check This Page