Privacy Policy

Effective 19 August 2026 · updated 9 September 2026

The short version. By default your photos stay in your own Google Drive or Microsoft OneDrive and your browser loads them from there directly — we never copy them. If you choose FunTravelMap Storage, or use the copy tool, you are asking us to keep copies of those photos on our servers for you; nothing is copied there unless you say so. What we keep about you is small: your email address, your username, and the details of any map you chose to publish.

Who we are

FunTravelMap is operated by Joseph Driskell. Contact: support@funtravelmap.com.

Signing in with Google

We request one Google permission: drive.file. This is the narrowest Drive scope Google offers. It gives an app access only to files that app created — in our case, the FunTravelMap folder and the photos you upload through the app. We cannot see, list or open anything else in your Drive, including files you add to that folder from the Drive website.

From that permission we read:

File names, folder names, and creation dates.
The GPS coordinates already embedded in your photos, which Google returns as metadata — the photo files themselves are not downloaded to our servers.
Thumbnail links, which your browser loads straight from Google.
Your Google account's email address and Drive identifier, so we know whose map is whose.

The optional "import existing folders" step asks, once, for a broader session-only Drive permission so the app can copy photos you tick from an existing folder into its own album folders. That token lives only in your browser tab, is never sent to our servers, and is gone when you close the tab. You can skip this step entirely and use the file picker instead.

Signing in with Microsoft

If you connect OneDrive instead, we request Files.ReadWrite.AppFolder (access to the app's own folder in your OneDrive and nothing else), plus your basic profile and email so we know whose map is whose. The same rules as Google apply: file names, dates, embedded coordinates and thumbnail links are read; your browser loads the pictures directly from Microsoft.

Staying signed in

So you do not have to reconnect on every visit, our server keeps a session record for you: a refresh credential from Google or Microsoft that lets the app mint short-lived access tokens for the app folder above. Your browser holds only a session id. Pressing Disconnect in the app deletes that session record on our server and clears everything in your browser; the standing permission on your Google or Microsoft account itself is only removed by you, from your Google account permissions or Microsoft app access page.

FunTravelMap Storage (optional)

If you choose FunTravelMap Storage as where your photos live, or run the copy tool to copy photos from Drive or OneDrive, we store on our servers (Cloudflare R2 and D1): the photo file, two smaller versions we make from it, its name, album, date, coordinates, note and whether you made it public. The copy tool only ever copies: it never deletes, moves or changes anything in your Drive or OneDrive. The free plan holds 250 MB; Pro holds 25 GB. Deleting a photo in the app deletes all three versions from our servers. Public versions of these photos have their embedded metadata (including GPS) removed before anyone else can see them.

What else we store on our servers

On Cloudflare Workers KV and D1:

Your Google or Microsoft account identifier and email address.
Your chosen username and display name, if you claim one.
If you publish a map: album names, photo identifiers, coordinates, photo dates, titles and notes you wrote, the country each album is in, the social links and promo card you added, and which photos you left out of your passport. Not the photos themselves (unless they are in FunTravelMap Storage).
If you share your map with friends through the People feature: the list of photos you chose to share, and a server-side copy of your session credential so our server can fetch those photos for the friends you gave a key to, without making them public.
The date and running count of your sign-ins, so we can tell how many people at an organisation are using a licence.
Licence records, if you buy or are granted Pro.
Cached place lookups (a coordinate → country/city answer). These contain no account data.

Preferences — theme, language, watermark setting, your last map position, passport picks — are kept in your own browser's local storage.

Photos and public maps

Marking an album public asks Google Drive or OneDrive to make those specific files viewable by anyone with the link. From that moment the photos are served publicly by Google or Microsoft, not by us. Anyone with the link can see them, and links get forwarded.

Photo coordinates reveal where a picture was taken. Do not publish albums shot at your home, your children's school, or anywhere you would not want a stranger to have an address for.

Location blurring (Pro) rounds the pins on your shared map to a grid. When it is on, your shared map no longer hands visitors links to the original Drive or OneDrive files (which carry the exact GPS inside the photo); it serves metadata-free preview versions through our server instead, and videos are left off the shared map because a video cannot be stripped of its location while it streams. Friends you gave a People key to still see your original photos.

Making an album private again removes that permission, but anyone who already downloaded or screenshotted a photo still has it. We cannot recall that.

Advertising

Free maps show travel experiences near the pin you are looking at. These are affiliate links — if you book something we may earn a commission at no extra cost to you. Matching happens from the coordinates already on screen; no tracking pixels, no third-party ad network, no cross-site profile. Private maps show no ads at all, and Pro removes them everywhere.

Payments

Payments are processed by Lemon Squeezy, who act as merchant of record. We never see or store your card details. We receive your purchase email address and licence key so we can activate Pro. Lemon Squeezy's own privacy policy governs what they collect.

Cookies and analytics

We set no advertising or tracking cookies and run no analytics scripts. Your browser stores your preferences and your sign-in session id locally so you do not have to reconnect on every visit.

Who else sees your data

Google — provides your Drive files and handles Google sign-in.
Microsoft — provides your OneDrive files and handles Microsoft sign-in, if you use it.
Cloudflare — hosts the site and stores the data listed above.
CARTO — serves the base map tiles your browser draws the map with.
OpenStreetMap contributors, Photon (komoot) and Nominatim — answer "which country/city is this coordinate in" and "where is this place name" lookups. Your browser or our server sends them a coordinate or a place name, never your account.
Open-Meteo — the temperature shown for the city you are looking at (a coordinate only).
Google Lens — only if you tap "Look it up" on a public photo; Google then fetches that public photo.
Lemon Squeezy — processes payments.
Viator, GetYourGuide, Klook, Trip.com and other travel booking partners — only if you click an affiliate link.

We do not sell personal information.

Deleting your data

Disconnect in the app ends your session on our server and clears this browser. To have your stored record — email, username, published map, People shares, sign-in log, and any photos in FunTravelMap Storage — deleted, email support@funtravelmap.com and we will remove it. You can also revoke the app's access yourself at any time from your Google account permissions or Microsoft app access page.

Children

FunTravelMap is not intended for anyone under 13, and we do not knowingly collect their data.

Changes

If this policy changes materially we will update the effective date above and note the change on this page.