Privacy policy
DeutschLast updated: 2026-11-13.
Controller
Tim Beyer
Kolonnenstr. 8
10827 Berlin
Deutschland
Email: hello@trailvid.com
Competent supervisory authority: Berliner Beauftragte für Datenschutz und Informationsfreiheit
Overview
TrailVid creates cinematic travel animations on your device. Your trips, themes, and finished videos are created and stored locally on your device; rendering and video encoding happen on your device, not on our servers. There is no user account and no server-side database of your trip content.
The cases where data leaves your device are described below: maps/routing lookups, audience measurement, feedback and, on iOS, subscription verification, iCloud sync and local-network streaming to an Apple TV.
Your rights
Under the GDPR you have the following rights:
- Access (Art. 15 GDPR)
- Rectification (Art. 16)
- Erasure (Art. 17)
- Restriction of processing (Art. 18)
- Data portability (Art. 20)
- Objection to processing based on legitimate interests (Art. 21)
Where we process data based on your consent, you can withdraw it at any time with effect for the future — the anonymous baseline measurement can be controlled in the app settings or via the notice on the website.
You also have the right to lodge a complaint with a data protection supervisory authority; the one competent for us is named above under “Controller”.
Hosting and server logs
The website, app delivery, our API (api.trailvid.com), and our tile service (tiles.trailvid.com) run on a hosting provider. When you access them, technically necessary connection data, including your IP address, is processed for delivery, security, and to limit abusive requests (rate limiting).
For sharper globe detail, the app requests imagery tiles from our first-party tile service. The requested tile coordinates indicate the map region currently being viewed; they are not your device’s GPS location and are not sent to Mapbox.
Cloudflare, Inc.
- Purpose
- Hosting the app, marketing site, API, and tile service; delivering close-range globe detail; verifying and storing subscription status; security and abuse prevention.
- Data
- IP address; Request metadata (user-agent, timestamps); Requested detail tile (tile coordinates / viewed map region); Edge logs; App-specific Apple transaction identifier, signed app proof and subscription status
- Legal basis
- Art. 6(1)(b) — providing the requested app function; Art. 6(1)(f) — legitimate interest in secure, functioning operation.
- Transfer
- USA — Data Privacy Framework (where certified) + Standard Contractual Clauses (SCCs).
- Retention
- Connection data is transient; edge logs follow Cloudflare's rolling cycle. Subscription records remain during access and for up to 90 days after its last verified end. Signed proofs are processed for verification without being stored.
In-app subscriptions
Apple handles purchases and payments. To verify and restore Pro access, our API at Cloudflare processes an Apple-signed app proof and its app-specific transaction identifier. It checks subscription status with Apple and processes signed change notifications from Apple. We retain the identifier, product, validity, renewal and refund status. Signed proofs are neither stored nor logged. We receive no payment details or Apple account contact details, and do not link the identifier to analytics or trip content. Processing is necessary to provide the purchased service (Article 6(1)(b) GDPR).
We delete subscription records within 90 days after the last verified end of access. A check without a confirmed purchase is retained for 90 days from verification or the first unsuccessful attempt. A later purchase or restore can recreate the record. Apple retains its own purchase and billing records under its retention rules.
Audience measurement
To improve the product and measure usage we use audience measurement processed in the EU. Without your consent, a cookieless baseline uses a server-side hash that changes daily. It stores no persistent analytics identifier on your device. The device model helps us assess performance and stability. Only with your explicit consent do we store a random identifier for this app installation to link usage across sessions. We do not join that identifier to your Apple identity, name, email address or trip content. You can withdraw your consent at any time.
If you enable Detailed analytics, we may infer your approximate country from your internet connection to understand how TrailVid is used in different markets. Only the country is retained for these statistics; PostHog discards the IP address before storing the analytics event. We do not retain city-level location or coordinates for these statistics or derive this information from your trips or photos.
We measure events such as “export finished”, “theme edited” and use of subscription options. This includes counts, formats, durations, the selected billing period and purchase or restore outcome. Apple account or transaction identifiers, signed proofs, payment details and trip content (place names, titles, captions) are excluded from analytics. We do not use session replay.
We ask for your consent to enriched analytics once inside the app, after you finish or skip the introduction; if you decline, the anonymous baseline is all that runs. Independently of that, App settings → Privacy lets you switch between “Off”, “Anonymous” and “Detailed” at any time. “Off” disables the anonymous baseline entirely as well.
With your current Detailed analytics consent, on iPhone and iPad we ask Apple whether an Apple advertising campaign led to your download. The short-lived AdServices token is sent directly to Apple and is not stored by us. Campaign, ad-group, keyword and ad identifiers, attribution type and placement may be linked to the random installation identifier in PostHog to measure exports and purchase outcomes by campaign. We do not retain an Apple account or device identifier, exact ad timestamps or campaign country. Withdrawing consent deletes the local attribution; previously collected events follow the stated retention rules. If you chose Detailed before campaign measurement was introduced, your original choice stays in effect. Updating the app does not prompt you again or enable campaign measurement for that choice. Apple controls its own advertising records under its privacy policy.
PostHog, Inc.
- Purpose
- Audience measurement and error tracking to improve the product; with consent, measuring which Apple advertising campaigns lead to app usage.
- Data
- Cookieless daily-rotating server hash (treated by PostHog as non-personal data); Event names and non-identifying properties (counts — including how many countries a trip spans, never which ones — formats, durations; never trip content); Device type and model (e.g. "iPhone15,2") to interpret performance and stability by hardware tier; Exception traces; Subscription option views, selected billing period and purchase/restore outcome; no Apple account or transaction identifiers, signed proofs or payment details; With app opt-in: a random identifier for this app installation, used to link usage across sessions; With Detailed analytics consent: may include approximate country inferred from the internet connection; no city-level location or coordinates; With current iOS consent: Apple campaign, ad-group, keyword and ad identifiers, attribution type and ad placement; no Apple account or device identifier and no attribution token
- Legal basis
- Baseline: Art. 6(1)(f) legitimate interest (cookieless, no storage on your device). Enriched (app opt-in only): Art. 6(1)(a) consent.
- Retention
- Per the PostHog project retention settings.
Map and route data
When you search for a place or build a route for car, bus, walking, or cycling, our server fetches the required geometry from a maps provider. What is transmitted is the search term you typed or the rounded coordinates of your stops — not your IP address, because the request is made server-side.
Mapbox, Inc.
- Purpose
- Geocoding and route directions for the trip the user is building.
- Data
- Typed search text; Quantized stop coordinates (location data); End-user IP is NOT sent (the Worker proxies server-to-server)
- Legal basis
- Art. 6(1)(b) (performing the requested feature) + Art. 6(1)(f).
- Transfer
- USA — Data Privacy Framework (where certified) + Standard Contractual Clauses (SCCs).
- Retention
- Responses cached at the edge (geocoding ~7 d / directions ~30 d), keyed on normalized query/coords — no IP or user id in the cache key.
Feedback
When you send feedback in the app, your message, an optional reply email you provide, and technical diagnostics (app version, platform, screen size, user agent) are transmitted to our issue tracker so we can act on it. Nothing is sent before you tap “Send”; your trip content is not transmitted.
GitHub, Inc. (Microsoft)
- Purpose
- Receiving and acting on user-submitted feedback.
- Data
- Message text; Optional reply email; Device diagnostics (app version, platform, screen size, user-agent); No trip content; sent only on explicit submit
- Legal basis
- Art. 6(1)(a) consent / Art. 6(1)(b) handling the request.
- Transfer
- USA — Data Privacy Framework (Microsoft) + Standard Contractual Clauses (SCCs).
- Retention
- For as long as needed to handle the report.
iCloud sync and Apple-TV streaming (iOS only)
On Apple devices, your trips, themes, and settings can sync between your devices via the private iCloud database of your own Apple account. The content resides in your own iCloud; we operate no server for this.
If an Apple TV is paired, trip and theme changes are streamed directly to that device on your local network (peer-to-peer, no external server).
Apple Inc.
- Purpose
- App Store distribution, billing and verification of in-app subscriptions; syncing the user's trips/themes/settings across their own Apple devices (CloudKit); silent push (APNs) to trigger sync; retrieving photo previews from the user's iCloud Photos library; with consent, attributing a download to an Apple advertising campaign.
- Data
- Trip and theme content including photo metadata and GPX files (in the user's own private iCloud); Push tokens; Photo identifiers and image downloads from the user’s iCloud Photos library; App-specific transaction identifier, purchased product, validity, renewal and refund status; For optional ad attribution: short-lived AdServices token and connection data for the direct request to Apple
- Legal basis
- Art. 6(1)(b) for requested features; Art. 6(1)(a) consent for optional ad attribution.
- Transfer
- USA — Standard Contractual Clauses (Art. 46 GDPR) and Apple's supplementary safeguards.
- Retention
- iCloud content remains until the user deletes it. Apple manages purchase, billing and advertising records under its own retention rules. TrailVid holds the AdServices token in memory only during the request.
Photo import (iOS only)
When you add photos, the app reads metadata from the photos you authorize (location, capture time and portable iCloud photo references) on your device. This metadata and any GPX files you add are saved with your trip so you can refine the selection and the places derived from it later. Analysis happens on the device. If iCloud sync is enabled, this trip data is transferred to your private iCloud; a paired Apple TV can receive it through your local network. When you view photo previews, Apple Photos may download the required images from your iCloud Photos library. Previews are cached temporarily on your device. TrailVid does not store image data in trips or upload it to our servers.
Local diagnostic captures
In the developer menu, you can choose to record diagnostics and export them as a file. Depending on the capture, the file contains trip and camera data or metadata from the last photo import. The capture stays on your device. When you export it, you choose where to save it or whom to share it with through your device’s sharing controls. These files are not automatically sent to us with feedback or analytics.
International data transfers
Some of the providers named above process data in the USA. Depending on the provider, these transfers are safeguarded by the EU-US Data Privacy Framework (where the provider is certified) and/or by Standard Contractual Clauses under Art. 46 GDPR; the basis that applies to a given provider is stated above with that provider. The Data Privacy Framework currently stands but is under legal challenge — the Standard Contractual Clauses remain in place as a standing safeguard should it fall away. You can request a copy of these safeguards from the address given above under “Controller”.
No automated decision-making
There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.
Retention
Content stored on your device remains there until you delete it. Server logs and cached route responses are cached only for operation and deleted on a rolling basis. Feedback is retained for as long as needed to handle it.
Changes to this policy
We update this policy when the underlying processing changes. The version published here at the time applies.