Data protection & data flows
How TravelPilot handles data – data-minimising, aggregated and transparent.
- signed configuration
- daily counters
- Local: sessions, language, pause
- aggregated reports
- Control centre: admins and reviewers only
- No full URLs, search content, destinations, names, cookies or payment data.
- No user or device ID, no personal profile; travellers do not need an account.
- Counting happens locally in the browser; only daily counts per website and rule are transmitted – plus the chosen reason category when someone continues outside the company tool.
- Small values are suppressed in reports; no freely combinable filters.
- Measured values are client observations and are not intended for sanctions against individuals.
- Transparency report for the works council and data protection, with data categories and limits.
- With every transmission, hosting providers technically process the IP address (logs with limited retention). TravelPilot itself does not store IP addresses.
- Retention: daily counters 25 months, duplicate identifiers 14 days, admin audit 36 months.
Sub-processors (technical)
- Vercel Inc. – hosting of the web application and API, execution region Frankfurt (fra1); global edge network. Technically processes IP addresses in access logs.
- Supabase Inc. – database and sign-in, project in an EU region (Frankfurt planned). API and auth logs contain IP addresses with plan-dependent retention.
- Intertours Reisen & Events GmbH – provider, operation and support (only with your approval).
This overview describes technical data flows. It replaces neither the privacy policy nor the data processing agreement; Intertours provides these separately.