Privacy Policy

TourVision iOS app & website — last updated 18 June 2026

TourVision turns the photos from a trip into a map video that plays back on your device. This page explains what data the app processes, what stays on your device, and what leaves it.

What stays on your device

• The photos you pick — TourVision reads each photo's location and capture time via the system's photo picker, but does not upload the images anywhere.
• Your trips and compositions — saved locally in the app's sandbox. No account, no sign-in, no sync.
• Exported videos — saved straight to your Photos library when you tap Share.

What leaves your device

Three categories, listed in the order of how much detail each one carries.

Basemap tile requests

When the app draws a map, it requests image tiles from Stadia Maps using a per-app API key. The request URL contains the geographic area being shown (tile coordinates) but no identifier tied to you. Tiles are served by Stadia Maps under their own privacy policy.

Route lookups (when you ask for road-following routes)

If you choose Walk, Bike, or Drive routing for a leg, TourVision sends the latitude/longitude of the leg's anchor points to OpenRouteService to compute a road-following path. No identifier and no other photo or trip data is sent. Straight-line routes do not call any external service.

Anonymous usage analytics

To learn which features are used and whether trips successfully export, TourVision sends anonymous events to PostHog (processed in the European Union).

Each install gets a random UUID at first launch. That UUID is the only thing tying events together — it is not derived from any device identifier and is never linked to your name, email, account, IDFA, or any external identity.

What the events contain:

• Counts and timings of in-app actions — for example, onboarding.action, trip.create.completed, editor.session, export.completed, feature.used.
• App version, device class, locale, days since first launch.
• Coarse, bucketed properties: e.g. exported video size as a bucket (5–20 MB), trip duration in seconds, clip count.

What the events never contain:

• Photo content, file names, or capture metadata.
• Precise or coarse location (no coordinates, country, or city).
• Your name, email, phone number, or any contact info.
• Any device identifier (no IDFA, no IDFV, no advertising id).

You can turn analytics off any time in Settings → Help improve TourVision. When the toggle is off, no events are sent. To request deletion of an install's already-collected events, email the address below with the anonymous distinct id shown in Settings (we will surface it there in a future build) and we will have PostHog purge them.

This website (tourvision.com)

The marketing site uses privacy-first, cookieless analytics — the same PostHog project, processed in the European Union. Because no cookies or local storage are written and no advertising identifiers are used, the site shows no cookie-consent banner.

We record only:

• A page view per page (which page, and the referring site), so we know how people find us.
• A click on the Download on the App Store button, so we know whether visitors go on to the App Store.

We do not run session recording, heatmaps, autocapture, ad-network pixels, or any cross-site tracking on this website.

What we do not do

• We do not track you across other apps, or across websites other than our own.
• We do not use the IDFA. The app does not show the ATT prompt.
• We do not sell or share data with advertising networks.
• We do not run third-party SDKs other than the ones listed above.

Children

TourVision is not directed to children under 13. We do not knowingly collect data from children.

Changes

If this policy changes, we will update the date at the top of this page. Material changes will also be summarized in the App Store "What's New" for the version that introduces them.

Contact

Questions or deletion requests: mads@mapstory.io.