Privacy

Who we are

The Ensign Toolbox is run by Ensign Advanced Systems Ltd. There is no account and no sign-in, so we do not hold a profile of you. Our wider privacy and cookies notice covers the Ensign website.

Your files

The tools run in your browser. The files you open, the pages you edit and the numbers you type into a calculator are not uploaded to us, and nothing in this site’s code sends them anywhere. The only files the site fetches are its own static assets, such as the sample PDFs.

Ensign Pack saves your work in progress, including the PDFs you added, in your browser’s own storage (IndexedDB) so it survives a reload. That copy stays on your device.

Error reports

When the site crashes in your browser, it sends a report to our own error tracker (GlitchTip, self-hosted by us), so we can find and fix the fault. We do this for everyone, including people who have Do Not Track switched on or have turned analytics off, because without it we cannot see failures that only happen on other people’s machines. A report contains:

• The error message and the stack trace.
• A few lines of our own source code around each point in the trace, which is how we see what failed. This is our code, not your document.
• The address of the page you were on. Any part after a ? is replaced with a placeholder, apart from a short list of harmless display settings such as view or sort. This matters because calculators keep your inputs in the address; those values are not sent. The tool’s name in the address is.
• Your browser and operating system as reported by the browser, and the version of the site you were using.
• The last 100 or so actions the page recorded before the crash: clicks, page changes, console messages and network requests, with the same address clean-up applied.

What we remove or never collect:

• Cookies, request bodies, most request headers, your name or any user identity (we never set one), and the IP address field the tracker would otherwise fill in.
• Variables held in memory, and details of the machine such as processor and memory.
• Credential-shaped text (tokens, passwords, user names embedded in links) found in messages and source lines.

Reports are not tied to you, and we have no way to ask which person a report came from. Two limits to be honest about: error messages and console output are passed through as written, so a message could in principle carry text that is not in our list above, and the server that receives a report necessarily sees the connection it arrives on. We do not use reports for anything except fixing faults.

Usage analytics

We count how the tools are used, so we know which ones matter and which are failing. The events are:

• A page view, with the page’s route, and the start and end of a visit.
• That a tool was opened, run, succeeded or failed: the tool’s name and type, the engine used, a duration band (for example “1-5s”) and a broad failure category (for example “corrupt”). Never the file name, the file contents or your calculator inputs.
• That a calculator produced a result, with the calculator’s name only.
• Your browser language, the site version, and a random identifier for your browser (kept in local storage) and for the current tab (kept in session storage). The random identifiers are not linked to a name or account.

Analytics sends nothing if your browser sends Do Not Track, or if you have switched it off with the “Anonymous analytics” control in the footer. Turning it off takes effect straight away, and the choice is remembered in your browser.

Cookies and browser storage

The site sets cookies only when you sign in with an Ensign account. They keep you signed in: toolbox_access_token (15 minutes), toolbox_refresh_token and toolbox_session (7 days). Your browser’s scripts cannot read them, and signing out removes them. Without signing in, no cookies are set.

It uses your browser’s local storage for: the tools you used recently, the options you last chose for each tool, your light or dark theme, your analytics opt-out, and the random browser identifier above. Session storage holds the random tab identifier, and the times of recent automatic returns from the sign-in page (so it cannot loop). IndexedDB holds the Ensign Pack work in progress described above. Clearing your site data removes all of it.

Contact

Questions about any of this can go to Ensign through the contact page.