Clever Little Goose

Clever Little Goose LLC — Terms of Use

Version 1
Last updated: 19 August 2026
Applies to: cleverlittlegoose.com and to the general activities of Clever Little Goose LLC, including software we make available, data we publish, and our consultancy work for clients, except where something carries terms of its own.

If you're here about an app, check whether it has its own terms. Cred Count does, at credcount.app/terms, and they're the ones which apply to it.

Save a copyPDF96 KBMarkdown24 KB

The little version

Clever Little Goose LLC makes a number of different things. Some of our software is open source; some of it isn't. Some of it is free; some of it is paid for. We publish data, and we take on work for clients.

Each of those carries its own licence, terms or contract, and that document governs it. These terms are the layer underneath. They're what applies to the website and what applies where nothing more specific does. Where the two differ, the specific document wins (§2).

A few things which stay true across everything:

These terms are governed by the law of England and Wales, and nothing in them takes away rights you have as a consumer.

1. Who you're agreeing with

These terms are between you and Clever Little Goose LLC, a limited liability company organised in the State of New Mexico, USA, on 15 July 2026 under the Limited Liability Company Act (Chapter 53, Article 19 NMSA 1978), registration number 0008116920.

We'll say "we" and "us". "You" is you.

These terms are governed by the law of England and Wales. §17 explains the choice, and what it doesn't take away from you.

2. What this covers, and what overrides it

This page and these terms cover cleverlittlegoose.com (§3), and they sets the baseline for everything else the company makes available (§4 onwards).

Anything with its own terms is governed by those terms. That includes, but isn't limited to:

Where one of those says something different from this page, it wins for the thing it covers. This page fills the gaps and doesn't override a document written for the specific case.

These terms don't narrow a licence we've already granted. If anything here reads as though it adds a restriction to open-source code we've published, it doesn't. The specific licence within the code is the answer, and §4.2 says the same.

There is no account here. This website has nothing to sign up to and nothing to log into. Although none currently do, where one of our products does require an account its own terms cover it.

3. The website

cleverlittlegoose.com is a plain website. No accounts, no cookies, no analytics, no trackers and nothing loaded from anyone else's server. Privacy Policy §2.3 sets out what that means for your data.

You may read it, link to it, print it, quote it with attribution, and keep a copy of anything published here.

These documents are built to be quoted. Every section has its own address (the link beside a heading copies a link straight to that section) and its own copy button, which gives you that section as markdown with the source URL on the end. Each document as a whole is published as HTML, markdown and PDF, so you can keep the exact version you were shown.

The markdown is meant to be findable by machines as well as by people. Every page points at its markdown twin with a <link rel="alternate" type="text/markdown"> tag, and /llms.txt lists all of them in one place. If you're asking an AI assistant to read or summarise one of our policies, give it the .md address, as it's smaller, and it's the text itself rather than the page built around it.

Please don't attack this site or anything else we run, scrape it at a volume that degrades it for other people, or use anything we release to do something unlawful.

The words and design of this site are ours, subject to copyright under the Copyright, Designs and Patents Act 1988. Software and data we publish are licensed separately, and §4 is where that lives.

We don't promise the site will always be up.

4. What we make available

4.1 Each thing carries its own terms

Software, data, an app, or a piece of client work, each arrives with the document that governs it, and that document is the one that governs it. A repository has a LICENSE file. A product has its terms. A data release has its licence. An engagement has a contract.

There's not a list of them on this page. Each document travels with the thing it covers, which is the one place it can't fall out of step.

4.2 Where a project is open source

Some of what we publish is open source. Our first published project, GooseQuill, is licensed under the Apache License, Version 2.0; other projects may use different licences, and each says so in its own repository.

Where a project is published under an open licence:

Apache 2.0 grants copyright and patent rights. It does not grant trade mark rights. Our §5 explains what that means for us.

4.3 Where something is paid for

Some of what we make is sold rather than given away, and some of it is closed source. The open-source projects are open because we chose to publish them that way, not because everything is.

A paid product carries its own terms, presented before you pay, and those terms govern it. They include what you're buying, how you pay and how refunds work. Where you buy through an app store, that store is usually the merchant of record and its refund policy is the route. §11 covers the general position.

4.4 Where something is free but closed

Some of what we build costs nothing to use, but isn't open source. Some of Cred Count is an example of this. You don't pay to download or use the core app, but the codebase remains ours and isn't published under an open licence.

A free but closed source product still carries its own terms, and those define the relationship.

4.5 Where we do work for you

Where the company takes on client work, the engagement contract governs it; including the scope, fees, deliverables, ownership of what's produced, confidentiality and liability. Nothing on this page displaces a signed agreement, and where this page and a contract differ, the contract governs (§2).

If we haven't signed anything, we haven't agreed to do any work.

5. Our name, and Gordon

Gordon is the goose. He's the one standing on the front of this site: an original illustration, and the company's mascot.

Gordon, our logos, and the names "Clever Little Goose", "Cred Count" and "GooseQuill" are ours, and no licence in our code covers any of them. Our source is licensed; what the company looks like and is called isn't. That's the ordinary position, and the reason for it is that a name and a face are how anyone can tell where a piece of software came from.

Things you can do without asking:

Things to ask about first — hello@cleverlittlegoose.com:

Ask and we'll give you an answer.

6. Contributing to our open-source projects

By opening a pull request or otherwise submitting work to one of our public repositories, you licence that contribution under the same licence as the project you're contributing to. For an Apache 2.0 project, that's the arrangement its §5 already describes.

You keep your copyright. We don't ask for an assignment, and there is currently no contributor licence agreement to sign. If that changes for a project, it will say so in the project. It will only apply to contributions made after the change and it will not apply retrospectively to yours.

Only submit work you have the right to submit. Your own, or something you're authorised to contribute. Don't paste in code carrying an incompatible licence. If your employment contract says your employer owns what you write, please settle that before opening the pull request rather than after we've merged it.

Public repositories are public and durable. Anything you put in an issue, a comment or a commit message can be copied, forked and archived by people we have no relationship with, and neither we nor the hosting platform can retrieve it afterwards. Don't put personal information in one, yours or anyone else's, and don't paste in a client document, a credential or an API key. If you need to send us something that shouldn't be public, email it (§10 for security reports).

We're not obliged to merge anything. A pull request may be declined, or may sit for a while, and that isn't a judgement on it.

7. Warranties and support

What you can expect depends on what you've got.

Open-source projects are provided as is. The licence says so, and that is the position. We provide no warranty that the software is accurate, fit for your purpose or free of defects, and there is no obligation for us to fix anything or to answer anything. Issues do get read, and most get a reply, but that is a description of what happens rather than a commitment about what will.

Paid products carry the rights the law gives you, and where relevant the terms of the product itself. If you've paid for digital content, the Consumer Rights Act 2015 requires it to be of satisfactory quality, fit for purpose and as described (ss.34–36), with the remedies in ss.42–46. §15 of these terms confirms that nothing here touches that.

Client work is governed by its contract, which is where any warranty, service level or support arrangement lives (§4.4).

One thing applies across all of offerings. Some of our tools produce output using machine learning models, and models get things wrong. Where you're relying on that output for something that matters, whether it's a filing, a set of accounts, advice you're giving somebody, please check it against the source.

8. Third-party services

Some of our tools need an account or an API key that you supply. GooseQuill requires a Google Gemini API key and can't convert PDFs without one; other tools may need something else and each will say.

Where that's the case:

9. If you process other people's data with our tools

Where one of our tools runs on your computer, we have no access to what you put through it. If you use it to process documents or data containing personal information, you are the data controller for that processing, and any third-party service you've configured is your processor under your agreement with them (§8).

We have no role in it, no access to it, and no way to retrieve, correct or delete anything you've processed. If someone makes a subject access request about data you put through one of our tools, we can't help you answer it, because we've never held it.

The controller's obligations are therefore yours: a lawful basis, informed consent, appropriate safeguards for any transfer, and (where you're sending other people's personal data to a third-party AI service) quite possibly a data protection impact assessment. Our project documentation flags the specific traps where we know about them, but the due diligence is yours to undertake.

This is a signpost, not legal advice. If you're handling client material, professional obligations of confidentiality will be an additional concern for you to consider.

10. Security research

If you find a security problem in something we publish, please tell us. The address and current expectations are in each repository's SECURITY.md; where there isn't one, email security@cleverlittlegoose.com with "security" in the subject.

Report it privately first. A public issue is an exploit notice for everyone still running the old version. Valid reports get fixed, and credited if you want the credit.

We won't pursue good-faith research. If you're testing your own installation of our software, you report privately, you don't access or exfiltrate anyone else's data, you don't degrade a service other people are relying on, and you give us a reasonable chance to fix the problem before going public, then we will not bring a claim against you or ask anyone else to.

There is no bug bounty.

11. Paying us

Where something we make is paid for, its own terms set out what you're buying and on what basis (§4.3). This section is the general position.

Prices can change. A change applies to purchases made afterwards, not to something you've already bought.

12. Availability, changes, and endings

This website may go down, change or move. The published documents are archived at /versions in the form they went out (§13).

A project may be archived. We may stop developing something, mark its repository read-only, or take it out of active maintenance. Where we do, we'll say so in the project rather than let it go quiet.

An open-source project doesn't stop when we do. The code is on your disk under a licence that doesn't expire, doesn't check in with us, and doesn't need us to keep existing. If you want to carry it on, the licence already permits a fork, just rename it, per §5.

A paid product's position is set by its own terms, which is where any commitment about what happens if it's discontinued belongs.

13. Changes to these terms

If we change these terms, we'll publish a new version and update the date at the top. New terms are effective from the publication date, unless we've told you otherwise. Nothing that has been published is rewritten: every version is kept at /versions as the exact page, markdown and PDF that were live at the time, so you can show what this document said on a given day.

The number tells you whether your position changed.

Editing this page has no effect on a licence already granted (§4.2), or on the terms of something you've already bought (§4.3).

14. What we're not liable for

Some liability can't be excluded, and we don't try. Nothing in these terms excludes or limits our liability for:

Subject to that, and so far as the law allows:

Anything we publish without charge is provided as is, with no warranty that it is accurate, complete, uninterrupted or fit for any particular purpose (§7). We are not liable for:

Where our liability can't be excluded but can be limited, it's limited to the greater of £100 and everything you have paid us in the twelve months before the claim.

This section is the baseline. A paid product's terms or a signed engagement contract may set liability differently for the thing they cover, and where they do, they govern it (§2). Whether a particular exclusion is fair is ultimately for a court (§15).

Where a licence carries its own limitation of liability, it applies alongside this section rather than instead of it, and neither is meant to leave you with less than the law allows you to keep.

15. Your consumer rights

If you're a consumer (defined as an individual acting outside your trade, business, craft or profession) this section beats everything above it.

Part 2 of the Consumer Rights Act 2015 applies to these terms, whether or not you've paid us anything (s.61). Any term here that is unfair is not binding on you (s.62), and a court can strike it out. If anything in §14 or §17 is unfair, it doesn't bind you and the rest of this document carries on without it.

Where you have paid for digital content, the Act's quality rights apply to it together with the remedies in ss.42–46. Digital content should be of satisfactory quality, fit for purpose, as described (ss.34–36), and nothing in these terms or in a product's own terms limits them. You also have the cancellation rights in the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, subject to the digital content exception that applies once delivery starts with your agreement.

You keep, and nothing here affects, your rights under the Digital Markets, Competition and Consumers Act 2024, the Misrepresentation Act 1967, and the general law of negligence.

If you're a consumer outside the UK, you keep every mandatory protection your own national law gives you, whatever §17 says.

16. Privacy

How this company handles personal data is set out in our Privacy Policy. It isn't part of this contract as it's a notice about what we do, not something you agree to, but it's the accurate description. §3 and §9 both point at it.

Products and projects have their own notices, because each raises its own questions. Cred Count's is at credcount.app/privacy. GooseQuill's is the PRIVACY.md in its repository, covering what the tool does with your documents rather than what the company does with your email. Nothing in one changes anything in another.

For anything about personal data, the address is privacy@cleverlittlegoose.com. For anything about these terms it's hello@cleverlittlegoose.com. The split exists so a request with a legal deadline on it doesn't sit behind general correspondence.

17. Governing law and where disputes go

These terms, and any dispute arising out of them or out of this website, are governed by the law of England and Wales, and the courts of England and Wales have jurisdiction.

That's a real choice, and here's what it doesn't do:

A licence or a contract may say something different, and where it does, it governs the thing it covers (§2). Apache 2.0 specifies no governing law at all, which is deliberate on its part.

Before any of that: email us. hello@cleverlittlegoose.com. Almost anything is fixable in a paragraph.

18. Export control

We're a US company, so software we publish is subject to US export control law, and to sanctions and export rules wherever you are.

Published open-source software is treated more lightly than people often expect. Publicly available source code, released without restriction, generally falls outside the Export Administration Regulations' controls. We don't ship encryption products, and nothing we publish is designed for a controlled use.

You're responsible for complying with the rules that apply to you. Don't download, use or redistribute our software if you're in a country subject to a comprehensive US embargo, if you're on a US Government list of prohibited or restricted parties, or if doing so would breach a sanction that applies to you.

19. The boring but necessary bits

Severability. If any part of these terms is held unenforceable, the rest stays in force.

No waiver. If we don't enforce something, that doesn't mean we've given it up.

Entire agreement. These terms, together with any licence, product terms or contract covering what you're actually using, are the whole agreement between us. Neither of us is relying on any statement made elsewhere, but nothing here excludes liability for fraudulent misrepresentation, or your rights under the Misrepresentation Act 1967 to the extent they can't be excluded.

Assignment. You can't transfer your rights under these terms. We can transfer ours if the business is sold or restructured, and a licence already granted goes with it.

Third parties. A person who is not a party to these terms has no right under the Contracts (Rights of Third Parties) Act 1999 to enforce any of them. This doesn't affect rights anyone has under a licence we've published, which stand on their own.

No partnership. Nothing here makes either of us the other's agent, partner or employee, and forking our code doesn't make you a representative of ours (§5).

20. Contact

Clever Little Goose LLC
1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, USA
hello@cleverlittlegoose.com · privacy@cleverlittlegoose.com (data protection)

Security reports: §10. Questions about the name: §5. Everything else, including a hole in our reasoning, email is the right route and a person reads it.

These terms are meant to be read, not clicked past.