Privacy notice
Updated August 23, 2026
Electroute is operated by SparkLabs AI Inc. It does not require an account, and it never asks who you are.
Product measurement
We run our own copy of Umami analytics on Electroute’s server. It records a page view and a short list of product actions: selecting a destination or origin, requesting and receiving or not receiving a route, broad route-speed and stop-count ranges, opening or completing a stop change, requesting a return trip, seeing the arrival question, changing language, and opening this notice.
The page view is always recorded as the home page. We remove search terms, URL parameters, fragments, and the path of any referring page. Analytics never receives the places you type or select, coordinates, origin, destination, route, exact distance or duration, vehicle, charge level, charger or site identity, connector, arrival-question identifier, or your answer to that question.
Umami processes your network address and browser details to produce a one-way anonymous session code and broad technical information such as browser, device type, language, and approximate country or region. The network address itself is not stored. The code’s salt changes every day, so visits on different days cannot be recognised as the same browser. We set no analytics cookie, create no account or advertising profile, and never use session replay or heatmaps.
We keep this product measurement for thirteen months and its daily backups for fourteen days. It is not shared with an analytics vendor or joined to an arrival answer.
Arrival answers
Separately, we keep your answer to the question “did it work?” after a stop we suggested.
We store which charging site the question was about, whether you answered yes, no, or not at all, when that happened, and the two facts needed to read the answer later — the connector type and what the app was showing about availability at the time.
We do not store anything that would let that answer be traced to you or joined to another one. No account, no cookie, no session identifier, no IP address, no origin, no destination, no route. Two answers from the same person are indistinguishable from two answers by different people. That is how the data is shaped, not a policy we apply to it — which also means there is no history of you to request, export, or delete, because none exists.
We keep these answers for twenty-four months, so that a winter can be compared with the winter before it.
What we do not keep
We do not store the places you search for, the places you select, the routes we plan, the roads those routes follow, or the charging stops we suggest. None of it is written to either Electroute data store.
Normal server security logs may record that a request happened and from where. They do not record what you searched for, the coordinates of your trip, or our credentials.
Google Maps Platform
As you type a place, the browser sends that text to Google to provide suggestions. If you choose “Use my location,” your coordinates are sent only after that action. When you plan a trip, the selected origin and destination coordinates are sent through Electroute’s private routing service to Google Routes. The map requests the displayed area from Google.
Google’s handling of this data is governed by the Google Privacy Policy. Electroute keeps no copy of any of it.
Where the information comes from
Vehicle specifications and imported static charger locations, connectors and power come from dated public datasets. Road distance and driving time are calculated by Google Routes. Energy and arrival-charge figures use a simplified winter model and are shown as ranges, never as single numbers. TomTom is queried for live availability at selected stops; a count is shown only when the station can be matched unambiguously, otherwise availability stays unknown. Every displayed availability figure carries how old it may be. Where our charging records for an area are known to be incomplete, the plan says so.
Contact
Questions: hello@electroute.com.