What this site keeps, and what it doesn't.
ChargeCliff is a calculator. It has no accounts, sets no cookies, runs no analytics and loads nothing from anyone else's servers. Here is everything it does record, in plain terms. Last checked against the code on 2026-10-31.
In your browser
No cookies, and nothing is written to your browser's storage. There is no cookie banner because there is nothing to ask consent for. Every file the page loads (the stylesheet, the script, the fonts, the images) comes from chargecliff.com itself: no tag managers, no analytics scripts, no fonts from Google, no embeds.
When you run a calculation, its inputs are written into the page's address so the result can be copied and shared. That link holds the car, the percentages, the charger, the temperature, the model year and so on; nothing about you.
On the server
The access log. The site runs on Google Cloud Run, which logs every request: the time, the page or API call requested, the response code, your IP address, your browser's user-agent string and the referring page, if any. There are no cookies to log. These lines are kept in this site's own Google Cloud Logging for 30 days and then deleted. They are read only for page counts and are not shared with anyone.
The calculation record. Each calculation the API runs writes one line to the same log: the vehicle, which calculator was used, the inputs you entered and a short summary of the result, with the time. The line has no IP address, no session id and no account, because there are no accounts. It is kept for 30 days like the rest of the log, and exists to show, in aggregate, which cars and which questions people check.
"Use my location". This button only does anything when you press it. Your browser asks for permission, and if you grant it, your latitude and longitude are sent to chargecliff.com, which asks the US National Weather Service (api.weather.gov) for the current temperature at the nearest station and returns that to the page. The coordinates are rounded to four decimal places (about 10 metres) for that request, are not stored, and the Weather Service sees the request come from this site's server, not from your browser. One exception: if the lookup fails, the error written to the server's own log includes the coordinates that failed.
Rate limiting. To keep one script from running up the server's costs, the API counts requests per IP address in memory for one minute at a time. The counts are discarded after the minute and when the service restarts; they are never written down.
Other sites
The footer links to jaredsloan.com and the About page to LinkedIn. Following either takes you to a site with its own practices; nothing is sent to them from here.
Questions
Write to jaredpsloan@gmail.com, the same address published in this site's security.txt.