Privacy Policy

Simon Abplanalp, c/o abplanalp-it
Schmittenweg 7, 5707 Seengen, Switzerland
Email: support@routebook.io

We process personal data only where a legal basis under Art. 6 GDPR applies:

On email engagement: links in our automated emails pass through a redirect on our own servers so we can see which messages are worth sending. We do not use tracking pixels and do not record whether you opened an email, only whether a link was clicked. Nothing is shared with a third party, and unsubscribe links are never tracked. You can stop receiving non-essential email entirely in your account settings.

On shared pages: when you create a share link, we count how often the page behind it is opened, so we can judge whether sharing is worth offering. We record which of your links was opened, the website the visitor came from, the approximate country, and, where you used one of our share buttons, which service you posted it to. We do not record who the visitor was. No account, no IP address and no cookie is stored against a view, and visitors are not tracked across websites. A visitor's IP address is held in memory only long enough to avoid counting the same reader twice, and is never stored. If you delete your account, your share links are deleted and the remaining view records no longer name you.

On the landing page: we count which language visitors' browsers ask for, so we know which languages to offer. Only a daily total per browser language, served language and approximate country is stored, never anything about an individual visitor, and signed-in members are not counted. As with shared pages, the IP address is held in memory only long enough to avoid counting a reload twice, and is never stored.

We use cookies to operate and improve our website. A cookie banner lets you manage your preferences. Necessary cookies are set without consent as they are essential for the service to function.

• Necessary: Authentication session, security tokens, your cookie choices (Art. 6(1)(b) GDPR)
• Necessary: Language cookie (NEXT_LOCALE, 12 months), set only when you choose a language in Settings, so the site keeps showing it. It holds only the language code (Art. 6(1)(b) GDPR)
• Analytics: Umami – privacy-focused, cookieless page-view statistics. It sets no cookies and does not track you across sites (Art. 6(1)(f) GDPR / consent)
• Functional: Stripe payment widgets, loaded only when you open a payment flow (Art. 6(1)(b) GDPR)
• Functional: Referral cookie (rb_ref, 30 days). When you open an invite link or a member's shared map, trip page, year recap or profile, it remembers who sent you, so that if you sign up, you and they each receive the free Pro month the invitation promises. It holds only that member's invite code or public username (Art. 6(1)(b) GDPR)
• Marketing: Reddit advertising pixel, used to measure whether our Reddit ads lead to sign-ups (Art. 6(1)(a) GDPR – consent)

You can withdraw consent at any time via the cookie banner or by clearing your browser cookies.

• Supabase (Supabase Inc., USA) – database and authentication hosting. Data is stored in the EU region (Frankfurt). Supabase acts as a data processor under a DPA. Transfer basis: Standard Contractual Clauses (SCCs).
• Vercel (Vercel Inc., USA) – website hosting and edge network. Transfer basis: Standard Contractual Clauses (SCCs). Vercel Privacy Policy.
• Stripe (Stripe, Inc., USA) – payment processing. Your payment data is transmitted directly to Stripe and never stored on our servers. Stripe is certified under the EU–US Data Privacy Framework. Stripe Privacy Policy.
• Umami (Umami Software, Inc., USA) – website analytics. Umami is cookieless and collects aggregated page views, referrer and approximate country without building a profile of you or tracking you across other websites. Umami Privacy Policy.
• Reddit (Reddit, Inc., USA) – advertising conversion measurement. If you arrive from one of our Reddit ads, the Reddit pixel records that a visit or sign-up occurred. Where you are signed in, a hashed identifier derived from your email address is transmitted so the conversion can be matched. Transfer basis: Standard Contractual Clauses. Reddit Privacy Policy.
• Google (Google Ireland Ltd., Ireland / Google LLC, USA) – Places, Geocoding and Maps APIs, used to identify and locate the hotels you record. We send the hotel name, city or place identifier being looked up; we do not send your name, email address or account identifier, and results are cached so the same place is not repeatedly queried. Transfer basis: EU–US Data Privacy Framework and Standard Contractual Clauses. Google Privacy Policy.
• Flight data providers – AeroDataBox, ADSB-DB, OpenSky Network and Planespotters, queried with the flight number, route and date you enter in order to return schedules, status and aircraft details. No account identifier is transmitted.
• Resend (Resend, Inc., USA) – delivery of transactional email (account and security messages, trip reminders, flight alerts). Resend receives your email address and the content of the message for the sole purpose of delivering it, and acts as a data processor under a data processing agreement. Transfer basis: Standard Contractual Clauses. Resend Privacy Policy.
• Cloudflare (Cloudflare, Inc., USA) – DNS for routebook.io and receipt of the emails you forward to your personal routebook.me address (Section 14). Cloudflare passes each email straight on to us and does not keep it. Transfer basis: EU–US Data Privacy Framework and Standard Contractual Clauses. Cloudflare Privacy Policy.
• Anthropic (Anthropic, PBC, USA) – reading the booking emails you forward (Section 14) to find the flights and hotel stays in them. Anthropic receives the email's text and attachments for that purpose only and, under its commercial terms, does not use them to train its models. Transfer basis: Standard Contractual Clauses. Anthropic Privacy Policy.
• Flagcdn / OurAirports / OpenFlights – public airport and flag data fetched client-side. No personal data is transmitted.

You have the following rights regarding your personal data:

• Access – request a copy of the data we hold about you
• Rectification – correct inaccurate or incomplete data
• Erasure – request deletion of your data ("right to be forgotten")
• Restriction – restrict processing in certain circumstances
• Portability – receive your data in a machine-readable format (CSV export available in Pro)
• Objection – object to processing based on legitimate interest
• Withdraw consent – withdraw any consent given at any time without affecting prior processing

To exercise any of these rights, contact us at support@routebook.io. We will respond within 30 days.

If you believe your data is being processed unlawfully, you have the right to lodge a complaint with a supervisory authority:

• Switzerland: Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter (EDÖB) – www.edoeb.admin.ch
• EU users: The supervisory authority in your country of residence

We implement appropriate technical and organisational measures to protect your data, including:

• All data transmission via HTTPS/TLS encryption
• Password hashing using bcrypt (handled by Supabase Auth)
• Role-based access controls – each user can only access their own data
• Regular dependency updates and security patches

We do not use automated decision-making or profiling within the meaning of Art. 22 GDPR.

We offer an optional Chrome browser extension that lets you import your hotel booking history from supported booking sites (currently Booking.com; additional sites may be added over time) into your routebook.io account. The extension only runs on the specific booking-site pages needed to read your trip history (e.g. "My Bookings" / trip-confirmation pages) and on routebook.io itself — it does not run on any other website.

The extension:

• Reads booking details already visible to you on the page you're viewing (hotel name, dates, price, confirmation number, and similar trip details) — it does not access your booking-site account credentials, payment details, or any page outside your trip/booking history.
• Sends the booking details it reads directly to your routebook.io account over an encrypted connection, using an authentication token you generate in Settings.
• Does not sell, share, or transmit your data to any third party. Data is only ever sent to routebook.io.
• Stores a small amount of data locally in your browser (your authentication token and a short list of already-imported bookings, used to avoid duplicate imports) — this stays on your device and is never transmitted elsewhere.

You can revoke the extension's access at any time by deleting its authentication token in Settings, or by uninstalling the extension from Chrome. Imported hotel stays are subject to the same rights described in Section 5 (Access, Rectification, Erasure, etc.) as any other data in your account.

Pro accounts can import past hotel stays from a Google Timeline export produced by the Google Maps app on your phone. The feature is optional, never runs automatically, and handles some of the most sensitive data we touch — so it is worth being precise about what happens to it.

• The export file is never uploaded. It is read and analysed entirely in your browser, on your device. Your raw location history does not reach our servers, and could not — the file is far larger than any request we accept.
• Only the overnight stays you select are sent to us, and only as a Google place identifier with a check-in and check-out date. Journeys, routes, timestamps, visits shorter than a night, and anywhere identified as your home or workplace are discarded in your browser and never transmitted.
• The place identifiers you select are sent to the Google Places API to obtain the hotel name and address, as described in Section 4. Results are cached to limit repeated lookups.
• Imported stays land in a review queue and become ordinary hotel stays only once you confirm them. Each is marked as having come from a Timeline import, so they can be found and removed together.
• Legal basis: Art. 6(1)(b) GDPR (performance of the contract), initiated by you each time you choose a file.

Imported stays carry the same rights as any other data in your account (Section 5) and can be deleted individually, or all at once under Settings → Hotels.

Where a flight in your account was cancelled or arrived late enough to cross the threshold of an air passenger rights regime covering that route — currently EU Regulation 261/2004 and its UK equivalent, Canada's Air Passenger Protection Regulations, and Brazil's ANAC rules — we may show a notice, and send one email, pointing you to a partner who handles such claims. The eligibility check runs on our own servers using flight data already in your account; nothing about your flights is shared with the partner unless you choose to click through and file a claim yourself.

• Outbound partner links pass through routebook.io/go/… so the click can be counted. We store the partner, the time, the placement the link was shown in, and — where applicable — your user ID and the flight it related to.
• An opaque identifier for the click is passed to the partner so that a successful claim can be attributed to us for commission purposes. It contains no name, email address or flight details.
• No advertising cookies or third-party tracking pixels are set by this feature.
• Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operating and financing the service). You can object at any time under Section 5, dismiss any individual notice in the app, and unsubscribe from the corresponding emails via the link in each one.
• If you delete your account, click records are kept but detached from you: the user ID is set to null, leaving an anonymous count.

These notices are generated automatically and are not legal advice. Whether compensation is actually owed depends on the cause of the disruption, which we cannot determine.

We may update this privacy policy from time to time. The current version is always available at routebook.io/privacy-policy. Material changes will be communicated by email.

If you are in Brazil, the Brazilian General Data Protection Law (Lei nº 13.709/2018, "LGPD") also applies to how we process your personal data. This section adds to the rest of this policy.

• Legal bases (art. 7 LGPD): performance of the contract for your account, flights, stays and payments (art. 7, V); compliance with legal obligations for payment records (art. 7, II); legitimate interest for usage data, email engagement, shared page views and affiliate click counts (art. 7, IX); and consent for the marketing pixel (art. 7, I).
• Your rights (art. 18 LGPD): confirmation that we process your data; access; correction of incomplete, inaccurate or outdated data; anonymisation, blocking or deletion of unnecessary or excessive data; portability; deletion of data processed with your consent; information about whom we share data with; information about the possibility of refusing consent and its consequences; and revocation of consent. You may also ask for a review of decisions made solely by automated processing (art. 20); we make none.
• International transfers (art. 33 LGPD): your data is stored in the EU and processed by the providers listed in Section 4, some of them in the USA. These transfers rely on standard contractual clauses and the other safeguards described there.
• Data protection officer (encarregado): Simon Abplanalp, reachable at support@routebook.io. Requests are answered free of charge, within 15 days where the LGPD requires it.
• Complaints: you may lodge a complaint with the Brazilian National Data Protection Authority (ANPD) – www.gov.br/anpd.

You can forward booking confirmations to a personal address at routebook.me, shown in Settings. This is optional and only happens when you, or a forwarding rule you set up, send an email there.

• The email is received by Cloudflare and passed straight to our servers. Its text and any PDF attachments are sent to Anthropic, which reads out the flights and hotel stays: dates, airports, flight numbers, hotel names, prices and confirmation numbers.
• We do not keep the email itself. We store only the flights and stays found, which wait in a review queue until you confirm or discard them, and a short log of each email received (the time, the sender's domain such as swiss.com, and the result) so that Settings can show you what happened to it. The log is deleted after 90 days, and flights you never reviewed after 60 days.
• Your address contains your username and a random part. Anyone who knows it can send email to it, so keep it to yourself; you can replace it at any time in Settings, which stops the old one immediately.
• After each email we send you a short reply, through Resend (Section 4), saying what was found.
• Legal basis: Art. 6(1)(b) GDPR (performance of the contract), initiated by you each time an email is sent to your address.