Terms of use

Free, and provided as-is

Every tool here is free for any purpose, commercial work included. No licence to accept, no attribution requirement, no cap on how often you run one. A mention of where something came from is appreciated and is not expected.

Provided as-is means what it says. We use these tools ourselves and we test them, but we warrant nothing about the output: not that it is correct, not that it is complete, not that it suits what you are about to do with it. If a tool gets something wrong and that costs you, the loss is yours. At a price of nothing, it is the only honest arrangement on offer.

Verify the output before you depend on it

Worth being specific, because the way each tool can mislead you differs.

• Decoding a tokenThe JWT tool shows you what a token says. It doesn't tell you whether the token is safe to trust. Signature verification needs the key, the issuer and the context, none of which a page in your browser has. Read the claims here; decide upstream.
• Generated passwords and keysThe generator draws from your browser's cryptographic random source, so the values are genuinely unpredictable. Everything after that is yours: where the value is stored, who can read it, whether it gets reused. A strong password in a plain text file is a weak secret.
• Minified CSS and JavaScriptMinification is a transformation, and a transformation can change behaviour at the edges. Run the minified file against your own pages and your own tests before it goes anywhere near production.

No uptime promise

There is no SLA and no support commitment. The site may be unreachable, a tool may change under you, and a tool may be withdrawn. None of that will arrive with notice. Free tools should not come with obligations to always be reachable, and a promise we had no reason to keep would be worth less than the honest absence of one.

Paid work is a separate agreement

If you engage Zinc Online Solutions to build something, that is a contract of its own, agreed in writing before any work starts. Nothing on this page governs it, and nothing on this page creates an obligation on either side.