Privacy

What do the tools handle?

When you submit a website, sitemap or list of URLs, the server fetches those pages, extracts what it needs to build your output file, returns the result and discards everything. Page content is held in memory for the length of the request and is not written to disk. Files you validate, by upload or paste, are handled the same way: checked and discarded. If you ask the validator to check links, the server requests each link in your file, up to 60. The robots.txt tools fetch a site’s robots.txt only when you press Fetch.

What is not collected?

• No accounts, so no names, email addresses or passwords.
• No tracking or advertising cookies, and no third-party analytics or advertising scripts. Usage is counted only as anonymous daily totals (see Usage counts below).
• No record linking the URLs you submit to you.
• No storage of generated files on the server. The output exists in your browser only, which is why you should download it.

What is kept in your browser?

To save you retyping, each tool remembers its last five inputs (addresses, not file contents) in your browser’s local storage, and the site remembers whether you chose light or dark mode. It also keeps a short list of the sites this browser finished a file for in the last 14 days, and of those it has already sent a passing live-check count for, so that count is sent only once (see Usage counts). When you move a result from one tool to another, for example from the generator to the validator, it is passed through your browser’s session storage and removed as soon as the next page reads it. None of this is sent to the server. You can clear the history with the Clear button under each tool, or by clearing this site’s data in your browser.

Server logs

Like any web server, the host may record standard request logs (such as the time, your IP address, the requested address including any query string, the response status and browser user agent) for operations and security. The tools send the sites you enter in the body of the request, which these logs do not include; a link that pre-fills a tool (for example ?url=) does appear in them. These are ordinary infrastructure logs, not analytics, and are not used to build any profile of visitors.

The tool requests are rate-limited using your IP address. The address itself is never written down by the app: so that every copy of the app counts the same limit, it is turned into a code with a secret key that is held only on the server and replaced every month. The code for the rate limit is kept for about a minute; the code for the free daily run limit is kept with that day’s count of runs and deleted within two days. These codes are pseudonymous, not anonymous: while a month’s key exists, the server could tell whether a given address made a request. Each key is deleted after two months, and from then on its codes cannot be linked to anyone.

Usage counts

To learn which tools are useful, the site keeps daily totals of a few events: pages viewed, tools run, files copied or downloaded, and live files checked. For a page view, the only detail kept is where the visit came from, as a category: a search engine, an AI assistant, the name of another website, a campaign name, or none. Each total is just a number for the day. No cookie is set, and nothing identifies you, your browser or your address. Daily totals are kept for up to 400 days.

One count is worked out in your browser, not on the server. If the validator finds no errors in a live file on a site this browser finished a file for in the last 14 days, your browser sends one count, once per site. It does not show that the file you built here is the one on the site. To do this, your browser keeps a short list of those sites; the site’s name stays in your browser.

Error logs

If something fails unexpectedly, the server writes a technical error message to its log so the fault can be fixed. That message can include the address that was being processed. It is not combined with anything else or used for any other purpose.

Sites you point the tools at

The crawler requests pages from other sites on your instruction. Those sites will see the request in their own logs, including the crawler’s user agent and the server’s IP address. Only point the tools at sites you have a legitimate reason to read.

Third parties

The site loads no third-party scripts, fonts or embeds. Fonts are served from this site. Nothing on a page here calls out to another domain, and the server’s content security policy enforces that.

Who is responsible for this site?

LLMs Text Generator is run from Malaysia. For questions about this policy, or to ask about any data, write to enquiry@llmstextgenerator.com.