What CityMap3D sends, and what it does not
What data leaves the browser when a map is embedded in a product: it is the first question of a security review. This page describes the boundary, request by request, so you can verify it yourself.
Your points stay in your application
The markers, results and annotations you place on the map are supplied by your own code, in the browser, to a projection interface. They are turned into screen positions and drawn.
They are not uploaded, not indexed, and not needed by us to draw them. A price, a patient, a vehicle identifier, a customer address: whatever your points mean, that meaning never leaves the page it was loaded into.
What does travel: the region on screen
To draw a place, the engine has to fetch that place. So the request that leaves the browser says which part of the world the camera is looking at, and the tiles for that region come back.
That is the whole outbound story, and it is inherent: any map that is not shipped entirely inside your bundle works this way, including the flat ones.
⚠ Worth being precise, because it is the part people gloss over: a sequence of those requests describes where a user looked. It does not describe what they were looking for, which is the part your own data holds.
No third-party calls
The engine talks to two services, both ours: the tile API and the live WebSocket channel. Nothing else. No analytics vendor, no font CDN, no ad network, no error reporter sending anything to a third party.
That means the surface you have to review reduces to our domain, and it means the map does not quietly add a processor to your own privacy notice.
Where it runs
Our infrastructure is in the European Union. The data behind the tiles is OpenStreetMap, which is public.
What a reviewer should actually do
Open the demo, open the network panel, and watch. Every request the engine makes is visible there, in order, and there is nothing in this page that you have to take our word for.
One caveat so the check holds: the demo ships an error reporter (Sentry) that the library does not contain. It is the only request that does not go to our domain.
Read on: what you plug in: canvas, scene and camera, or the legal notice.
Read more
- From an OpenStreetMap row to a shaded pixel
Spherical cells instead of a Mercator grid, real geometry at every zoom with no raster fallback, a sky computed from your date and place, and a composable shader chain. How CityMap3D turns OpenStreetMap into a 3D globe.
- Which OpenStreetMap tags become 3D geometry
Building heights and levels, ground cover, trees and street lamps placed one by one, named places. The OpenStreetMap tags the pipeline reads, and what each one becomes on screen.