What leaves your browser, and what doesn't

What leaves your browser

One thing: the bounding box of the area you draw. Our server needs it to fetch OpenStreetMap building and road data and Copernicus elevation tiles on your behalf — a direct request from your browser to those sources isn't practical at the scale a busy site needs, so we relay it through a server we control (see how it works). That request carries the coordinates of your box and nothing that identifies you beyond whatever your browser and network already send with any web request.

What stays on your device

Everything else. Parsing the map data, meshing the terrain, extruding buildings, running the manifold checks, assembling the layers, writing the STL or 3MF file — all of it runs in your browser, using WebAssembly, and none of it is sent anywhere. We don't see the model you build. We don't store the area you drew. There's no account, no upload, no server-side copy of your file.

Logs

Our server keeps ordinary web server logs — request path, timestamp, IP — for operating the service and catching abuse of the shared data proxy, and nothing beyond that. There's no analytics script or tracking pixel watching what you draw.