What we save and remove
Immediate inspections
An ordinary inspection does not save a report in our application database. We read the public website address you provide and return the findings. Avoid submitting private links or addresses containing passwords, personal details or access codes.
True Measure Inspector does not require an account or email address. The inspection and saved-report pages do not use application tracking cookies or advertising analytics.
Optional saved reports
We save a report only when you select the consent box. New saved reports contain the website address, selected findings and supporting public-page evidence, report dates and versions, and the information needed to process and retrieve the report. Public website text and addresses can contain personal information.
New saved reports omit the full parsed-page record, raw structured-data blocks, response headers and unused resource inventories. The download is a selected evidence record, not a complete copy that can repeat the original inspection.
Your private link works for seven days from creation. Anyone with the link can read the report during that time. We cannot recover a lost link.
After access ends, automatic cleanup removes new saved reports and their job records from active application storage. Cleanup runs periodically; service failures can delay physical removal. A downloaded or printed copy remains under your control.
Earlier reports and provider records
Older saved reports were created under terms that allowed storage after their seven-day link expired. Automatic deletion has not been applied to those older records.
Cloudflare hosts this service. Provider logs and database recovery history are separate from active report storage. Their exact account settings and retention have not yet been verified. We cannot promise that application cleanup immediately removes every provider-held copy.
Saved reports are not enrollment in marketing emails, paid services or ongoing monitoring. Any future offer that needs your contact information will ask separately.
How True Measure Inspector reads websites
When someone checks a website, True Measure Inspector reads the same public pages any visitor can open. In website logs, its name is TrueMeasureInspector.
Before it reads a page, it opens the site’s robots.txt file. That file is where a site owner tells crawlers, the automated readers like this one, what they may visit. It follows the rules written for TrueMeasureInspector and for its older name, PublicMeasure. If neither name is listed, it follows the rules for all crawlers (User-agent: *). If a site has no robots.txt file, its public pages are treated as open. If the file can’t be read, the check stops. If the file asks crawlers to wait between visits (a crawl-delay), the check waits at least that long between its requests to the site, for waits up to 20 seconds. It stops if the site asks for a longer wait. Because each check has a time limit, waiting can mean it reads fewer linked pages and skips some of the supporting files and extra checks described below.
It reads public pages only, and at most 5 pages per check: the page entered and up to 4 linked pages on the same website. It skips links to pages such as /cart, /checkout, /account, /login and /admin. It also asks for a few supporting files, such as the sitemap and site icon, the plain http:// version of the address, and one made-up address to see how the site handles a missing page.
It does not sign in, and it does not fill in or submit forms.
To keep it off your website, add these two lines to your robots.txt file:
User-agent: TrueMeasureInspector
Disallow: /