Effective date: 9 August 2026
What this website handles
The Carbon Impact Estimator for remote offsite planning only asks for the information needed to estimate flight emissions: the number of people travelling, the airports they are departing from, and the potential destination airports you want to compare. That information is used once to run the calculation and is not stored, logged, or shared with anyone else.
External services
To compute emissions, the website sends the origin and destination airport codes to the Google Travel Impact Model API. Google receives only the airport codes needed for the calculation. We do not send names, email addresses, or any other personal information.
Stored data
Emissions figures
To reduce API usage and improve performance, this website stores anonymized airport-pair emissions factors after they are first calculated: - the two airport codes - the estimated emissions per passenger - which provider produced the figure - the methodology used - the date it was calculated This data is not linked to any user, team, or individual travel plans, and they contain no personal information. We cannot identify you, your team, or your company from this information. Figures are kept for 1 year, at which point they are recalculated when a user re-enters that airport pair.
Departure airport uploads
CSV files you upload on the Estimate screen are read and processed entirely in your browser. They are never sent to or stored on our servers, and the data is discarded as soon as you close or refresh the page — well within 24 hours.
Analytics
We use Fathom Analytics and Lovable Analytics to collect anonymous visit and pageview data. This helps us understand how the website is used so we can keep improving it. Neither Fathom Analytics nor Lovable Analytics collects personally identifiable information through this website.
Cookies and tracking
This website does not use cookies, trackers, or third-party analytics beyond Fathom Analytics and Lovable Analytics. We do not run advertising or retargeting scripts.
Changes to this policy
We will update this page if the way we handle data changes. The effective date at the top reflects the most recent version.