The terms that govern using OmniKitly

1. Accepting these terms

Using OmniKitly — running a tool, creating an account, calling the API — means you accept these terms. If you do not accept them, the only tools you can use without an account are the ones marked as running entirely in your browser, and even those are offered under the terms below.

2. What OmniKitly is

OmniKitly is a collection of file and text utilities. Some run entirely in your browser; some upload your file to a processing service for the duration of one job, as declared on that tool's own page. The privacy page describes exactly which mode each tool uses and why.

3. Accounts

Most tools need no account. An account exists for bulk jobs, processing history, saved API keys and workflows synced to your session — not as a gate in front of ordinary use. You are responsible for the accuracy of the information you give us and for anything done under your account, including through an API key you generate. Tell us at the contact page if you believe a key or your account has been compromised, and revoke it from your account settings the moment you suspect that.

You must be able to form a binding contract to create an account — in most places, that means being at least 18, or the age of majority where you live. We do not knowingly offer accounts to anyone below that age.

4. Your files, and what we do with them

You keep ownership of anything you upload or process here. Using a tool grants us only the narrow, temporary license needed to run that job: to read the file, process it, and return the result to you. We do not claim any broader license, we do not use your files to train anything, and we do not look at file contents outside of running the job you asked for.

For a server-side job, the file exists on the processing service only for as long as the job needs it, per the retention window described on the privacy page. Deleting a result yourself, or letting it expire, removes it on our end too.

You are responsible for having the right to upload what you upload. Do not use OmniKitly to process content you do not have the rights to, or content that is illegal to possess or distribute where you are.

5. Acceptable use

Beyond the general rule against illegal content, a few uses are refused outright rather than merely discouraged:

• Bulk or unsolicited email sending, address harvesting, or anything that uses the email tools here as a spam pipeline. The email category is inspection and validation only — header analysis, record checks, previews of mail you already have.
• Attempting to bypass the fair-use limits described on a tool's own page, including through multiple accounts, automated key rotation, or traffic designed to look like something other than what it is.
• Probing, scanning or attacking the service or the infrastructure it runs on, beyond the ordinary use of the tools as provided — the SSL checker, redirect checker and similar tools are for inspecting addresses you have a legitimate reason to look at, not for scanning ranges you do not control.
• Reselling or rebranding the service without a separate agreement with us.
• Anything designed to degrade the service for other people, including deliberately triggering worst-case processing loads.

We can suspend or terminate access — an account, an API key, or a session — for a real violation of this section, and we will tell you why when we do.

6. Fair use and rate limits

Every tool carries limits: on file size, on how many jobs you can run in an hour, and in some cases on how much of a file is processed. Those limits exist to keep the service usable for everyone on shared infrastructure, and the number you hit is stated in the error itself when you hit it, not hidden behind a generic refusal. Limits differ between anonymous use, a free account and other plans as they become available, and we can adjust them as the service grows.

7. API use

The API is governed by these same terms. An API key is yours alone to use — do not share it, and do not build a service on top of it that resells access without agreeing that separately with us first. We can revoke a key that is being misused, with notice where that is practical.

8. No warranty

OmniKitly is provided as it stands, without a warranty that it will be uninterrupted, error-free, or fit for a particular purpose. This is an early build, said plainly on the site itself — a tool can have a real limitation, and where we know one, we try to state it on that tool's own page rather than let you find it the hard way. That does not amount to a guarantee that none remain undiscovered.

We are not responsible for loss caused by a tool producing an incorrect result, by the service being unavailable, or by a file being deleted once its retention window has passed. Keep your own copy of anything that matters until you have checked the result.

9. Limitation of liability

To the extent the law where you are allows it, OmniKitly's liability to you for anything arising from your use of the service is limited to direct damages, and does not extend to indirect, incidental or consequential loss — lost data, lost business, or similar. Nothing in these terms is meant to exclude a liability that cannot lawfully be excluded, such as for our own gross negligence or fraud.

10. Changes to the service and these terms

We can add, change or remove tools, and we can update these terms as the service changes — most often to describe something new that has actually shipped, in keeping with the rest of this site. A material change to these terms will be reflected in the date at the top of this page. Continuing to use OmniKitly after a change means you accept the updated terms; if you do not, stop using the service.

11. Ending your use

You can stop using OmniKitly at any time, and delete your account from the account page when that feature is available to you. We can suspend or end an account for a real breach of section 5, or discontinue the service, or a part of it, with reasonable notice where that is practical.

12. Questions

If anything here is unclear, or you think we have got something wrong, use the contact page rather than guessing. We would rather answer a question about these terms than have you work around them.