Skip to content
routebase

Privacy Policy

Last updated: 23 August 2026

1. Controller

Routebase GmbH, Wegedornstraße 253Q, 12524 Berlin, Germany
E-Mail: hello@routebase.dev

2. What this website processes

This website is a static marketing site. It carries no forms and asks you for no personal data. By default it sets no cookies: we measure visits with a cookieless, privacy-friendly analytics service that stores nothing on your device and collects no personal data (see section 4). Cookies are only ever set if you consent to advertising measurement (see section 5) — if you decline, or never answer, none are set. Beyond that, the only data processed here is the technical connection data every web server records (see section 3).

3. Hosting and server logs

The site is delivered via Microsoft Azure (global edge network and hosting). When you visit, technical connection data (IP address, user agent, timestamp, requested resource) is processed to deliver the site and to protect it against abuse. Access logs are retained for 30 days in a log store located in the EU, after which they are deleted automatically. Legal basis: Art. 6 (1) (f) GDPR — our legitimate interest in operating and securing the website. Microsoft processes this data on our behalf as our processor.

4. Web analytics

We use a privacy-friendly web analytics service. It does not use cookies, does not store anything on your device, and does not collect or retain personal data: your IP address and user agent are processed transiently to derive aggregate, non-identifying statistics (page views, referrer, country, device type) and are never stored. Because nothing is stored on or read from your device, no consent is required for this measurement. Legal basis: Art. 6 (1) (f) GDPR — our legitimate interest in understanding aggregate site usage.

The service is Pirsch Analytics, provided by Emvi Software GmbH, Nickelstraße 1b, 33378 Rheda-Wiedenbrück, Germany, with all data processed and stored on servers in Germany. Emvi Software GmbH processes this data on our behalf as our processor. More details: pirsch.io/privacy.

5. Advertising measurement (Google Ads)

We advertise on Google Search. To find out which ads lead to sign-ups, we use the Google Ads conversion tag provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. It stores and reads information on your device and can transfer data to Google LLC in the United States, based on the EU-US Data Privacy Framework and standard contractual clauses. We measure conversions only — we do not use remarketing, we do not build advertising audiences, and we do not use Google Analytics.

This happens only if you consent. Legal basis: your consent, Art. 6 (1) (a) GDPR and § 25 (1) TDDDG. Without consent the tag is not loaded and sets nothing on your device. You can withdraw your consent at any time with effect for the future via the Cookie settings link at the bottom of every page — withdrawal is as easy as giving consent. The full, current list of cookies and their lifetimes is shown in that consent dialog.

Your consent decision is recorded and stored for us by our consent management provider, so that we can demonstrate it as required by Art. 7 (1) GDPR. The provider acts as our processor and stores this data within the European Union. Note that the measurement described in §4 (Pirsch) is unaffected by this decision: it is cookieless, needs no consent, and is not part of the consent dialog.

6. Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction of processing, data portability, and objection. You also have the right to lodge a complaint with a supervisory authority — for us, the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit).

7. The Routebase application

This policy covers the marketing website only. The Routebase application (app.routebase.dev) is governed by the separate application privacy policy.

8. Changes

We will update this policy if the way this website operates changes (for example, if hosting or logging changes). The date at the top indicates when it was last revised.