3D Terrain Tool
Legal

Privacy policy

Last updated 10 November 2026

3D Terrain Tool (3dterraintool.com) is run by Jack Lambourne in the United Kingdom, who is the data controller. This page explains what is collected, why, and your choices. Questions: send us feedback or a complaint (no account needed).

The 3D tool itself

The map and 3D viewer run in your browser. The area you select is not uploaded to us. To draw the map and build your model, your browser requests map tiles, elevation, satellite and aerial imagery, building and place data straight from the services listed in Services your browser contacts below, and each of them receives your IP address and the area requested, under its own privacy policy. If your browser cannot load aerial imagery directly, our server fetches it for you instead (a relay that only contacts the imagery providers in that list), and the provider then sees our server rather than you. New Zealand imagery always goes through our server, because it needs an access key that we keep private.

Bring your own API keys (experimental). If you choose to paste a key from Esri, Mapbox or MapTiler into the settings dialog of the 3D tool, it is stored only in your browser's local storage and is sent only to that provider, straight from your browser, to fetch imagery or elevation for your model. It is never sent to our servers or through our relay, and we cannot see it. The provider receives your IP address, your key and the tiles requested, under its own terms and privacy policy. You can remove a key in the same dialog at any time, or clear this site's data in your browser.

Fonts and the mapping and 3D libraries (Leaflet, three.js and similar) are served from this site itself, so loading them does not contact Google Fonts or a code-delivery network.

Services your browser contacts

When you use the site your browser talks to the services below, in addition to our own servers (hosted on Cloudflare). Each one receives at least your IP address and browser details, and the other data shown. This is the complete list of third parties the pages and the 3D tool contact; nothing else is loaded from outside this site. "Only if" means nothing is sent unless you do that thing.

Service (operator)Used forWhenAlso receives
OpenStreetMap tile servers (OpenStreetMap Foundation, UK)The base map in the 3D tool and on the coverage pageWhenever one of those maps is shownThe map area you look at
Mapterhorn (tiles.mapterhorn.com) and Terrain Tiles on AWS (Amazon Web Services, USA)Elevation data for your modelWhen you generate a 3D modelThe area of your model
EOX IT Services (Austria): Sentinel-2 cloudless imagerySatellite imagery draped on your modelWhen you generate a 3D modelThe area of your model
National mapping agencies: swisstopo (Switzerland), IGN (France and Spain), PDOK / Kadaster (Netherlands), USGS National Map (USA), City of Vienna basemap.at (Austria), GSI (Japan)Higher-resolution aerial photographyOnly when your model's area lies inside that countryThe area of your model
DL upscale (optional)Runs a deep-learning model on the satellite picture inside your browserOnly if you tick itNothing about you is sent. The model file (about 34 MB) is downloaded from this site the first time you use it and then kept by your browser.
LINZ (New Zealand)Aerial photography for New ZealandOnly for New Zealand areas, and only via our server, which adds our access key; LINZ sees our server, not youThe area of your model
Overpass servers: overpass-api.de (FOSSGIS, Germany), overpass.private.coffee (private.coffee), overpass.cstc.org.uk (community-run; operator not stated)Buildings, places and other OpenStreetMap features on your modelWhen the 3D tool loads buildings or points of interestThe area and the kinds of feature requested
Nominatim (OpenStreetMap Foundation) and Photon (komoot, Germany)Looking up a place name or the name of a place at a pointOnly if you search for a place, or use the story builder's place lookupThe text you typed or the coordinates
Wikimedia Commons (Wikimedia Foundation, USA)Finding and showing openly licensed photosOnly if you use the Photos tabYour search and the photos you open
Esri, Mapbox, MapTiler (USA, USA, Finland)Imagery or elevation with your own accountOnly if you add your own key in "Bring your own API keys"Your key and the tiles requested
Google: sign-in (accounts.google.com)"Sign in with Google" buttonOn pages that show the button, while you are signed outWhether you sign in, and what Google normally receives
Google: profile pictures (googleusercontent.com)Showing the pictures of people who signed in with Google, on stories, comments, rankings and profilesOn pages that show such pictures, for every visitor, signed in or notNothing more; your browser is told not to send the page it came from
Google: YouTube (youtube-nocookie.com)The video players on the homepage and tutorialsOn pages with a videoCookies may be set once you press play
Google AdSenseAdvertising on the community pagesOnly for visitors who are not supporters, and only once an ads consent choice exists; personalised ads need your consentAd identifiers, as described under Advertising
Stripe (USA / Ireland)Taking supporter paymentsOnly when you press Upgrade and payYour payment details, which we never see

Some of these services are outside the UK and rely on safeguards such as the UK's approved transfer terms; see each provider's own policy. We removed a Russian-operated Overpass server (maps.mail.ru) and BigDataCloud's location service from the site, and the pages no longer load Google Fonts, jsDelivr, unpkg, cdnjs or esm.sh.

The story pages you can open from the community site are shown in a locked-down frame that cannot load scripts or fonts from other sites, and can load images only from Google profile pictures and Wikimedia Commons (the photos the story builder inserts), so a story cannot make your browser contact anyone else.

Accounts and the community site

You can browse without an account. If you sign in with Google we receive your name, email address and profile picture, and store them with a handle you choose. We use them to run your account, show your name and picture on stories and comments you publish, and contact you about the service. Stories, comments, reports and feedback you submit are stored on our servers (Cloudflare) and published stories are public.

You can delete your account from your profile page, which removes your profile and your stories. Some records, such as moderation reports and payment records, may be kept where we have a legal or accounting need.

Feedback and complaints

You do not need an account to send feedback or a complaint. We store what you write, the page link if you give one and the email address you give, which we use only to reply to you. If you are not signed in we also keep a short-lived code, made one-way from your IP address and the date, only so that we can limit floods of messages. The code cannot be turned back into your address, changes every day, and is blanked after two days. Feedback is read by the site owner and moderators. We delete it once it has been dealt with and is no longer needed, and you can ask us to delete it sooner.

Moderation records

When a moderator or administrator hides or removes a story or comment, restricts an account, or decides a report, we keep a record of what was done, to what, by whom, when and why (this can include the affected account's handle and, for a removed comment, the start of its text). We keep these records for as long as we need them to show that reports were handled properly and to deal with any appeal or complaint, and they can be kept where we have a legal need.

Supporter payments

Supporter upgrades are paid through Stripe. We never see or store your card details. We keep a record of the payment (amount, date and Stripe reference) for accounting and to apply your supporter status.

Cookies and similar technologies

Advertising

We show ads on the community site using Google AdSense. Google and its partners may use cookies and similar identifiers to serve and measure ads and, with your consent, to personalise them. In the UK and EEA you are asked for consent before personalised ads are used, and you can change your choice at any time from the "Privacy settings" link in the page footer. Learn how Google uses data at policies.google.com/technologies/partner-sites, and manage ad personalisation at adssettings.google.com.

Supporters see no ads and no advertising scripts are loaded for them.

Our legal bases

We process account data to provide the service you asked for (contract), keep records we are legally required to keep, and run and secure the site (legitimate interests). Advertising cookies rely on your consent.

Your rights

Under UK GDPR you can ask to access, correct, delete or export your data, object to processing, or withdraw consent at any time. Contact us through the feedback/complaint form (no account needed). You can also complain to the Information Commissioner's Office at ico.org.uk.

Who else handles data

Cloudflare (hosting, database and file storage), Google (sign-in and advertising) and Stripe (payments) process data on our behalf. The map, imagery, place and photo services in Services your browser contacts receive data directly from your browser, not from us. Some of these are outside the UK and rely on approved safeguards for transfers.

Children

The service is not aimed at children under 13 and we do not knowingly collect their data.

Changes

If this policy changes materially we will update the date above.