Security & Local Processing

Last reviewed: 2026-07-17

ChargeEstimateKit calculators are designed for quick estimates that run in your web browser. The calculator code reads the values in the visible form, performs the arithmetic on the current page, and replaces the visible result. The site does not require a login, create user accounts, or provide a saved-calculation dashboard. This page explains that local calculation boundary without claiming that loading a website involves no network activity.

What stays in the browser during a calculation

When you change an input and select Calculate, the active values are read from the form by JavaScript in the page. The formula runs in that browser tab and the result is written back to the result area. The ordinary Calculate action is not implemented as a request to a ChargeEstimateKit calculation server. Preset buttons, reset, and the first estimate shown when a page opens use the same browser-side calculation path.

  • The current form values remain in the page memory while you use that tab.
  • The visible result is derived in the browser from those values and the published formula.
  • Resetting the form restores its defaults; closing the tab removes its active in-page state.
  • No ChargeEstimateKit account or site-owned saved-input database is used by the calculators.

A value may still return after a reload when it is present in the page URL. That is a property of the optional share-link feature, not a hidden saved calculation. Browser autofill, extensions, or session restoration may also retain information under the browser's own settings. ChargeEstimateKit does not control those browser features.

Values that can appear in a share URL

Selecting Copy link with inputs creates a URL whose query string contains the calculator's current fields. Depending on the tool, those fields can include battery capacity, starting and target charge percentages, charger power, charging efficiency, electricity price, fees, distance, vehicle efficiency, voltage, current, or phase. The exact parameter names and values are visible after the question mark in the copied URL. Opening that link applies the supported parameters to the matching form so another person can reproduce the estimate.

Treat a share URL as information you are deliberately disclosing. It can appear in browser history, bookmarks, copied messages, screenshots, email systems, workplace chat archives, referrer information where applicable, and hosting and security logs. Anyone who receives the complete URL can read its parameters. The form is designed for planning numbers, not personal records, so do not enter or share an account number, service address, meter identifier, vehicle identifier, password, payment detail, or a value that you consider sensitive. You can remove the query string and reload the clean page URL to return to default inputs.

What the calculator does not send

The Calculate event does not intentionally upload the form fields to a ChargeEstimateKit calculation API, user profile, or site-owned calculation database. The calculator does not connect to vehicle telematics, read an odometer, sign in to a utility account, request a live tariff, access a charging-network account, or contact a payment service. Values such as usable battery capacity, observed charger power, and electricity price must be entered or confirmed by you because the site does not retrieve them from those systems.

This boundary applies to the site's calculator implementation. It should not be interpreted as a promise that no software on your device can observe a page. Browser extensions, accessibility tools, password managers, antivirus products, managed-device software, corporate proxies, and the browser itself operate under their own settings. Use a browser profile you trust and avoid entering private data that is not needed for an estimate.

What ordinary web requests can transmit

Local arithmetic does not make the website an offline application. Loading a page requires an ordinary HTTPS request to the hosting infrastructure. That request can include an IP address, browser and device headers, the requested path or full URL, date and time, and information used for delivery, abuse prevention, and security logging. If you open a share URL, its query string is part of the requested URL and may therefore be included in hosting and security logs.

The site also includes Google AdSense code for site verification and advertising. That script is obtained from Google and may make third-party requests or process data under Google's terms, consent requirements, and the site's Privacy Policy. A browser may also request fonts, scripts, styles, icons, or other static assets needed to display the page. ChargeEstimateKit does not label those hosting, asset, or advertising requests as local-only processing. Calculation in the browser and network delivery of the website are separate facts.

Verify the behavior in the Network panel

You can inspect the distinction yourself with browser developer tools. Menu names vary slightly between Chrome, Edge, Firefox, and Safari, but the following test uses the standard Network panel. A clean browser profile or private window makes the list easier to interpret because extensions can add unrelated requests.

  1. Open a calculator page, then open Developer Tools before beginning the test.
  2. Select Network and reload once. The initial document, static assets, and possible third-party requests will appear.
  3. After the page is ready, clear the Network list so the next action starts from an empty view.
  4. Change one calculator input, select Calculate, and confirm that the visible estimate changes.
  5. Filter by Fetch/XHR and inspect any new rows. The calculation should not require a ChargeEstimateKit calculation endpoint or a form-value request payload.
  6. Select Copy link with inputs separately. Inspect the address copied to the clipboard and identify the query parameters after the question mark.
  7. Paste the link into a new tab only if its values are safe to share, then repeat the Network inspection to see that the full URL is part of the page request.

The Network panel is a practical way to observe browser requests during a specific session. It is not a universal audit of your operating system, extensions, upstream network, or third-party services. If a request is unclear, inspect its domain, method, query string, request payload, initiator, and timing rather than assuming that every request contains calculator values.

Data-minimization checklist

  • Enter only the technical or price values required by the selected formula.
  • Use rounded planning numbers when an exact account value is unnecessary.
  • Do not paste text from a bill, charging receipt, account screen, or vehicle profile into a numeric field.
  • Review every query parameter before copying, bookmarking, or sending a share link.
  • Remove the query string from the address bar when you no longer need a reproducible link.
  • Report unexpected behavior without attaching passwords, payment details, or complete private documents.

Calculator fields are intended for quantities such as kWh, kW, percentages, distances, and prices. They are not intended to identify a person, household, vehicle account, or utility account. Using the minimum information needed keeps the estimate easier to review and reduces what can be exposed if a URL is shared accidentally.

Advertising placement boundary

Ads are not intended to appear inside calculator forms, result cards, warning messages, reset buttons, or navigation. If advertising is enabled, placements should remain visually separate from interactive calculation controls and should not interrupt a user entering values. An ad request is a third-party network activity; it is not part of the local arithmetic used to produce the estimate.

What this page does not guarantee

This page describes the current intended calculator behavior and its processing boundaries. It is not a penetration-test report, a certification of every browser or third party, or electrical, installation, billing, tax, legal, privacy, or vehicle safety advice. Site code and third-party services can change, so the review date is shown above and the verification steps remain available to users.

Reporting a concern

Use the Contact page to report a privacy, security, or correction concern. Include the affected page, browser name and version, approximate time, the action you took, the request domain if relevant, and steps that reproduce the issue. A cropped screenshot with private values removed can help. Do not email passwords, payment information, account identifiers, full utility bills, complete charging receipts, or other sensitive records. Reports are reviewed as maintenance feedback and do not create an emergency monitoring or professional advisory service.

Report a security or privacy concern