Detailed terms and acceptable use notes
Read moreThis long-form section expands the Terms and Conditions into practical guidance: what acceptable use looks like on a tools website, what not to do, and how to treat tool outputs responsibly. The goal is clarity for users and a consistent, indexable policy page for search engines.
Acceptable use (practical examples)
Acceptable use means using tools for legitimate tasks without harming the service or other users. Typical acceptable workflows include creating drafts, converting files, checking metadata, formatting text/code, or calculating values for comparison.
Unacceptable use includes attempts to break security, overload systems, or automate scraping in a way that degrades performance. It also includes using outputs to mislead, impersonate, or conduct illegal activity.
If you are unsure about a workflow, keep it simple: use the tool for its intended purpose and avoid mass automation.
- Allowed: personal, educational, and business use for legitimate tasks.
- Not allowed: abusive automation, scraping that harms performance, or attempts to bypass security.
- Not allowed: illegal, harmful, deceptive, or impersonation content generation.
- Not allowed: uploading content you don’t have rights to use.
Outputs are conveniences, not guarantees
Tools are designed to save time. Outputs may be drafts, templates, conversions, or calculations based on the inputs you provide. Because inputs vary widely, outputs cannot be guaranteed to be correct for every use case.
For critical uses—legal, compliance, medical, or finance—you must verify results. This is especially important when using template-style generators or any AI-assisted drafting workflows.
Treat outputs as starting points. Review, test, and validate in your own context before relying on them.
- Review and verify outputs before publishing.
- Test developer outputs in your environment.
- Keep backups of important documents.
- Avoid sensitive data in online tools.
Security and performance expectations
We may use security controls such as rate limiting and abuse detection to keep the service stable. These controls help prevent spam, scraping, and automated abuse.
If you encounter an issue that looks like a false positive (for example, you are blocked after many requests), contact support with the tool URL and a description of your workflow.
Respecting these limits keeps the service fast for everyone.
- Do not attempt to bypass rate limits or protections.
- Avoid high-frequency automated requests.
- Report issues with the page URL and steps to reproduce.
Where to find all public pages
For transparency, the site provides a sitemap page and machine-friendly sitemap files. These help users browse the website and help search engines discover the public routes.
You can open the sitemap page to browse categories, tools and policy pages in one place.