Privacy policy

These tools are run by me, Mario, the person behind Kind of Lost (kindoflost.com). Contact: mario@kindoflost.com. Versión en español más abajo.

What you send

To plan routes the tool needs your stops: addresses and/or coordinates, quantities, time windows, service times and vehicle details. You send them by uploading a workbook, pasting a Google Sheet link or a list of addresses on the web page or in the embedded widget, from the Google Sheets add-on, or through an AI assistant connected to the MCP server. With an assistant, I never see your conversation, only what the assistant chooses to send to the tool.

Who else receives part of it

Computing real routes needs two public map services, and this is the part of your data that leaves my server:

• Address lookup (geocoding). Each address given without latitude/longitude is sent, on its own, to the US Census Bureau geocoder and, when that cannot match it or for non-US addresses, to OpenStreetMap Nominatim, and if Nominatim cannot match it or does not answer, to Photon (run by komoot, also OpenStreetMap data). Stops you give as coordinates are not sent to any of them.
• Driving times. The coordinates of the depot and the stops (not the addresses, names or quantities) are sent to the public OSRM routing server to get the drive time between every pair.
• Google Sheets. If you paste a Google Sheet link, the tool downloads that sheet from Google to read it.

Those services have their own privacy policies. If you do not want an address sent to a geocoder, give its latitude and longitude instead.

What I keep

• Address lookups. Every address that is found is kept on the server's disk together with its coordinates, so that it never has to be looked up again (for you or anyone else who sends the same address). This cache holds the address text and coordinates only — no names, quantities, times, or who sent it — and it has no expiry. Ask me and I will delete an address from it. Addresses sent from the Google Sheets add-on are never added to it.
• Driving-time tables. The drive times between a set of points are kept on disk, filed under a one-way hash of the coordinates, so the same set of stops is not re-requested from OSRM.
• Everything else is not kept. Workbooks, stop lists and results are held in memory while the solve runs — and, for the Sheets add-on and the MCP server, for at most 15 minutes after so the add-on or the assistant can collect the result — and are then discarded. They are not written to a database, not used to train any model, not sold and not shared.
• Run log. For each run I record one anonymous row: date and time, which tool, country (from the network, not your address), device type (phone or computer), the page that linked to the tool, how the data was sent (file, sheet, pasted addresses, widget, Sheets add-on or AI assistant), the number of stops served and routes, how long the solve took, whether it succeeded (with a short reason when it did not, with quoted text and numbers masked) and whether the caller looked like a browser or a script. For AI-assistant runs the row also has the assistant's app name, the assistant's short description of the request with emails, phone numbers, addresses and digits removed, and counts describing the request (how many stops, vehicles and so on). No addresses, names, email or IP address.
• Email. If you choose to leave your email for tool updates, it is stored only to send those updates, and you can ask me to delete it at any time.

The web pages use Google Analytics to count visits. To stop any one caller from overloading the server, the calling IP address is held in memory for up to 10 minutes for rate limiting only.

Fleet Route Optimizer add-on for Google Sheets

What it can access. The add-on asks Google for three permissions, and uses each for one thing only:

• spreadsheets.currentonly — to see and edit only the spreadsheet it is opened in (not your other files, not your Drive): it reads your locations, vehicles and parameters tabs, and writes the Routes and warm_start tabs and the sample tabs.
• script.container.ui — to show its menu and sidebar inside Google Sheets.
• script.external_request — to connect to my server at routing.kindoflost.com, where the routes are computed.

What it reads and when. Nothing happens until you press a button. When you press Optimize routes, the add-on reads the tabs of the current spreadsheet and sends them over HTTPS to my server. When you press Insert sample, it only downloads example data and writes it into tabs of your spreadsheet.

What I do with it. Exactly what is described above for the web tool: addresses without coordinates go to the geocoders and coordinates go to OSRM, but nothing from your spreadsheet is added to the address cache or the drive-time cache (add-on runs only read them), and everything is used only to compute the routes, which are sent back and written into your spreadsheet. The spreadsheet content is held in the server's memory while the solve runs and for at most 15 minutes after, so the sidebar can collect the result, and is then discarded. It is not written to a database, not used to train any model, not sold and not shared. Each run writes one row in the run log described above, marked as coming from the Sheets add-on. To stop any one user from overloading the server, the add-on sends Google's temporary per-user key (an anonymous, rotating identifier, not your email), which is held in memory for rate limiting only.

Google user data. The add-on's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. No AI or machine-learning model, and no third-party AI service, receives or processes any of it.

Google user data: retention and deletion

• Retention. Data the add-on reads from your spreadsheet (and the routes computed from it) is kept only in the server's memory while the solve runs and for at most 15 minutes after, so the sidebar can collect the result. It is then deleted automatically. The temporary file used to hand it to the solver process is deleted as soon as the solve ends.
• Nothing is stored. It is never written to a database, a log, a backup, the address cache or the drive-time cache. The run-log row for an add-on run holds only the anonymous counts listed under “Run log” above, with no spreadsheet content.
• Deletion. Because nothing is kept past those 15 minutes, there is no stored Google user data to delete. To stop the add-on from reading anything at all, uninstall it from Extensions → Add-ons → Manage add-ons or revoke its access at myaccount.google.com/permissions. Questions or deletion requests: mario@kindoflost.com.

MCP server for AI assistants (routing.kindoflost.com/mcp)

Everything above applies. What the assistant does with the routes it gets back is governed by that assistant's own privacy policy.

How your data is protected

• Encryption in transit. The web tool, the Sheets add-on and the MCP server only talk to my server over HTTPS (TLS), and the calls to the geocoders and OSRM are made over HTTPS. A request sent over plain HTTP is redirected to HTTPS; the add-on is only allowed to call https://routing.kindoflost.com/.
• No storage of your content. The spreadsheet or route data you send is kept in the server's memory while the solve runs and, for the Sheets add-on and the MCP server, for at most 15 minutes after, so the result can be collected. To hand it to the solver process it is written to a temporary file that is deleted as soon as the solve ends. It is never written to a database, and it is not put in logs or backups. The only things kept are the address cache (address text and coordinates, nothing else) and the drive-time cache (stored under a code made from the coordinates), both described above — and add-on runs never add to either.
• Minimal access. The add-on asks only for the spreadsheet it is opened in (spreadsheets.currentonly), never your other files or your Drive. The run log holds only anonymous counts: no names, no addresses, no spreadsheet content, no email address and no IP address.
• Isolation. Each Sheets add-on and MCP solve runs in its own short-lived process, discarded when the solve ends.
• Restricted access. Only I, the developer, can access the server and its configuration.
• No AI/ML training. Data sent to the tool, including any data obtained from Google Workspace APIs through the add-on, is not used to develop, improve or train generalized or non-personalized AI or machine-learning models, by me or by anyone else.
• Hosting. The server runs on Render (render.com) in the United States. Render provides the infrastructure only.

If you believe your data was exposed, email mario@kindoflost.com and I will answer promptly.

Changes

If this policy changes, the new version will be posted on this page with a new date.

Política de privacidad (español)

Para armar las rutas la herramienta necesita sus paradas (direcciones o coordenadas, cantidades, ventanas horarias, tiempos de servicio y datos de los vehículos), que usted envía desde la página web, el widget, el complemento de Google Sheets o un asistente de IA conectado al servidor MCP. Con un asistente, no veo su conversación, solo lo que el asistente envía a la herramienta.

Quién más recibe una parte. Cada dirección sin latitud y longitud se envía al geocodificador del Censo de EE. UU. y, si no la encuentra o no es de EE. UU., a OpenStreetMap Nominatim y, si tampoco la encuentra o no responde, a Photon (de komoot). Las coordenadas del depósito y de las paradas (no las direcciones ni los nombres) se envían al servidor público de OSRM para obtener los tiempos de manejo. Si pega un enlace de Google Sheets, la hoja se descarga de Google. Si no quiere que una dirección se envíe a un geocodificador, indique sus coordenadas.

Qué guardo. Cada dirección encontrada queda guardada en el disco del servidor con sus coordenadas, sin vencimiento, para no volver a buscarla (solo la dirección y las coordenadas: sin nombres, cantidades ni quién la envió); si me lo pide, la borro. Los tiempos de manejo se guardan bajo un hash de las coordenadas. Todo lo demás (planillas, listas de paradas, resultados) se mantiene en memoria mientras se resuelve y, en el complemento y el servidor MCP, como máximo 15 minutos después, y se descarta: no se guarda en una base de datos, no se usa para entrenar modelos, no se vende ni se comparte. Por cada corrida registro una fila anónima (fecha y hora, herramienta, país, tipo de dispositivo, página de origen, forma de envío, cantidad de paradas atendidas y rutas, duración, resultado con un motivo breve y enmascarado si falló, y si quien llamó parecía un navegador o un programa; en las corridas desde un asistente, también el nombre de la aplicación, una descripción breve del pedido sin correos, teléfonos, direcciones ni números, y conteos del pedido), sin direcciones, nombres, correo ni dirección IP. La dirección IP que llama se mantiene en memoria hasta 10 minutos solo para limitar el uso. Las páginas usan Google Analytics. Todo viaja cifrado por HTTPS; solo yo tengo acceso al servidor, alojado en Render (render.com) en Estados Unidos. Contacto: mario@kindoflost.com.

Complemento Optimizador de Rutas para Flotas (Google Sheets). Pide tres permisos: spreadsheets.currentonly, para ver y editar solo la planilla en la que se abre (leer sus hojas locations, vehicles y parameters y escribir las hojas de resultados y de ejemplo); script.container.ui, para mostrar su menú y panel lateral; y script.external_request, para conectarse a mi servidor routing.kindoflost.com. No hace nada hasta que usted pulsa un botón. Al pulsar Optimizar rutas envía las hojas de la planilla por HTTPS a mi servidor, donde se tratan igual que en la versión web (lo descrito arriba): el contenido queda en memoria mientras se resuelve y como máximo 15 minutos después, y se descarta automáticamente. Retención y eliminación de datos de usuario de Google: nada de la planilla se guarda en una base de datos, registro, copia de respaldo, la caché de direcciones ni la de tiempos de manejo (el complemento solo las consulta), así que pasados esos 15 minutos no queda ningún dato suyo que borrar; para consultas o pedidos de borrado, escriba a mario@kindoflost.com. Ningún modelo de IA ni servicio de IA de terceros recibe ni procesa estos datos. La clave temporal de usuario de Google (anónima, no su correo) se usa en memoria solo para limitar el uso. El uso y la transferencia de información recibida de las APIs de Google se ajustan a la Política de datos de usuario de los servicios de API de Google, incluidos los requisitos de uso limitado. Los datos recibidos, incluidos los obtenidos de las APIs de Google Workspace, no se usan para desarrollar, mejorar ni entrenar modelos generalizados de IA o aprendizaje automático. Puede desinstalarlo desde Extensiones → Complementos → Administrar complementos o revocar el acceso en myaccount.google.com/permissions.