Security and data handling
What happens to what you put in
For a procurement or IT team deciding whether a pilot can go ahead. Limited to what is true of the code and the hosting today, including what has not been written yet.
Tools that never send your data anywhere
- Questionnaire response kit — The pasted questionnaire and every draft stay in your browser.
- Energy per kg, scrap cost and air-leak tools — Every figure you enter stays in your browser.
- Plastic Packaging Tax, machine energy, allocation and CCA pages — Every figure you enter stays in your browser.
- Share links — Your inputs travel after the # in the link, which browsers never send to a server. Anyone you send the link to can read them.
Spreadsheets
CSV files are read in your browser. An Excel file (.xlsx) is sent to the website's server to be unzipped, because that needs a parsing library; it is capped at 4 MB, only the first worksheet is read, and nothing is stored — the rows come straight back to your browser.
Forms, hosting and analytics
- The early-access and contact forms store what you submit in a Supabase (PostgreSQL) database hosted in London (AWS eu-west-2).
- The website and its server functions are hosted by Vercel. The signed-in TrueGauge application's backend runs on Railway, with its data in the same London database.
- Page views and page performance are measured with Vercel Web Analytics and Speed Insights. Nothing you type into a tool is sent to them. How Vercel describes them.
Not written yet
- A data-retention and deletion policy for the signed-in applications.
- A data-processing agreement for pilot customers sharing plant data.
- Terms of use reviewed by a solicitor.
Until those exist, please agree in writing with us what plant data a pilot needs and how it will be handled before sharing any. The public tools need none of it.
Questions: ceo.punargen@outlook.com. How the figures themselves are made is on the methodology page.