Terms of Service

By using useqr.app, the REST API, the MCP server, or any other surface we operate, you agree to these terms. If you do not, do not use the service — and note that the entire project is MIT-licensed, so you can run your own copy under whatever terms you like instead. That escape hatch is deliberate.

There is no account, so there is nothing to accept by clicking. Use is acceptance, and stopping is how you leave.

UseQR generates, decodes and verifies QR codes. Static codes are generated entirely in your browser. A keyless REST API and an MCP server perform the same work on our infrastructure for callers that want it. Everything is free, with no tier, no cap and no watermark.

We may add, change, deprecate or remove features. We may also change how the hosted API behaves, including adding limits, if abuse or cost makes that necessary. The commitment we have made publicly on free that stays free is about never putting a price, an expiry or an advertisement on what we already give you. It is not a promise that the running service is immortal.

The service and the software are provided “as is”, without warranty of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, accuracy or non-infringement. This is the same allocation of risk the MIT licence sets out, applied to the hosted service as well as to the code.

We do not warrant that the service will be uninterrupted, error-free, or that any generated code will scan on every device, in every app, at every size, on every surface. We test hard and we verify every code with a real decoder. That is a meaningful check, not a guarantee.

Some jurisdictions do not allow the exclusion of certain warranties. Where that is so, the exclusions above apply only to the extent the law permits, and your mandatory statutory rights as a consumer are unaffected.

There is no service level agreement, no support commitment and no compensation for downtime. This is a free public good maintained in spare time and paid for personally; promising availability we cannot underwrite would be dishonest, so we do not.

If continuous availability matters to your business, the correct answer is not our promise, it is your copy: the source is on GitHub and self-hosting is supported. Better still, prefer static codes, which depend on nothing we run once they exist.

This clause matters more than the rest of the page combined, so it gets its own heading rather than a line of fine print.

You are responsible for testing a generated QR code before you commit it to anything. Scan the actual artefact — the printed sticker, the pressed vinyl, the etched plate, the on-screen render — with more than one phone, in the lighting the code will actually live in, at the distance a person will actually stand.

UseQR rasterises and decodes every code it produces, which catches design choices that break scannability. What it cannot see is ink bleed, low-contrast substrate, gloss lamination, a quiet zone cropped by a print shop, a shrink-wrapped curve, a deliberately dark colour scheme reproduced badly, or a destination URL that stops working after you print. Those failures are real, they are common, and they are outside anything we can check from a browser.

We are not liable for reprints, wasted print runs, lost trade, or any other loss arising from a code that was not tested in its final physical form.

Yours stays yours. Whatever you encode — a URL, a menu, a payment string, a contact card — remains entirely your property. We claim no licence over it, no right to use it, and for static generation we never receive it in the first place. The QR images you produce are yours to use commercially, print, modify and redistribute with no attribution and no restriction from us.

Ours is MIT. The UseQR site, the QR engine and the API are open source under the MIT licence. You may fork it, self-host it, sell a service built on it and audit every line, on the licence’s terms.

The exception is identity: the UseQR name and logo are not covered by the MIT licence of the code. Use them to refer to this project honestly — do not use them to suggest a fork of yours is the official one, or that we endorse something we do not.

Your use of the service is subject to the Acceptable Use Policy, which forms part of these terms. In short: do not use anything we host to attack, defraud, or harm people. That page explains precisely which surfaces we can police and which we deliberately cannot.

The API and MCP server are keyless and currently unmetered. Please use them like someone who wants them to stay that way: cache deterministic results rather than refetching them, and do not point a load generator at them. If keeping the service up for everyone ever requires rate limits, we will add them and say so.

To the fullest extent permitted by law, neither the maintainers nor the contributors are liable for any indirect, incidental, special, consequential, exemplary or punitive damages, nor for any loss of profit, revenue, goodwill, business or data, arising out of or in connection with the service or these terms — whether in contract, tort (including negligence) or otherwise, and even if the possibility of such loss was known.

Where liability cannot be excluded, the total aggregate liability of the maintainers and contributors for all claims is limited to the greater of the amount you have paid to use UseQR, which is zero, or ten United States dollars.

Nothing here limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be limited.

You are responsible for what you encode, where you point it, and what you do with the result. If a third party brings a claim against the maintainers because of your use of the service — for example a code you generated that pointed at a fraudulent destination — that claim is yours to answer, and you agree to indemnify the maintainers against it.

There is no account to suspend. What we can do, and will do where abuse warrants it, is decline to serve particular requests to the hosted API, MCP server or image endpoints, and ask our host to block traffic. Static generation runs on your device and is not something we can switch off — nor would a switch help, since the code is open and self-hostable.

UseQR is maintained by individuals rather than a company, and no governing law or exclusive forum has been designated for these terms. Until one is stated here, any dispute is subject to the ordinary rules of jurisdiction that would apply anyway, and nothing in these terms removes a mandatory right you hold under the consumer law of the country where you live.

We will update the date at the top when these terms change. As with everything else here, this page is a file in a public repository, so each revision is a dated commit with a diff you can read for yourself. Continuing to use the service after a change means you accept the revised terms.

There is no support inbox and we have not invented one. Questions about these terms go to the issue tracker; security matters go through a private advisory.

Privacy Policy → · Acceptable Use Policy → · Report abuse →