Skip to content

Privacy

The short version: there are no accounts, no advertising, no cookie banner because there are no tracking cookies, and your itinerary lives at a private URL that only you have.

This is a supplement to the Berlin Concierge privacy notice, covering only what the trip planner does that the rest of the site does not: storing an itinerary, and taking a payment. Everything in the parent notice still applies.

Who is responsible

The same operator as the rest of Berlin Concierge — named in full in the Impressum, which is where the registered details live rather than being duplicated here. Contact: hello@conciergeberlin.de.

What we store when you build an itinerary

The answers you gave in the intake — your dates, how many adults and children, your pace, budget band, chosen interests, anything you asked to exclude, whether you need step-free access, and which part of Berlin you are staying in — together with the itinerary we built from them. This is stored so the trip URL keeps working when you come back to it.

We do not ask for your name, your email address, your phone number or your address, and there is no account to create. Legal basis: Art. 6(1)(b) GDPR (performance of a contract you requested).

Your request also goes on our internal job board

Your plan is written by a person in Berlin rather than generated automatically, so when you submit the intake a copy of those same answers is placed on our internal job board — together with your trip link and the short code — because that is how someone here knows there is a plan to write. It holds no categories of data beyond the ones listed above.

The board is our own system, on the same server, reachable only with a password, and it is the same place the enquiries from our contact form are held. It is not a third party and your answers are not sent anywhere else. Note that it does hold your trip link, which is the only credential your itinerary has.

A copy on the board is a second place your request exists, so a request to delete your trip covers both. Legal basis: Art. 6(1)(b) GDPR, the same contract.

The trip URL is the only credential

Your itinerary is reachable by anyone who has its link, and it is excluded from search engines. There is no password, because there is no account. That is a deliberate trade — it means we hold nothing that identifies you — but it also means that if you post the link publicly, the itinerary is public. If you need a trip removed, send us the link.

Payment

Payment is handled entirely by Stripe Payments Europe, Ltd. on their own hosted checkout page. Your card details never reach this server and we never see them. We receive, and store, only the confirmation Stripe sends us: the payment reference, the amount, the currency, and the email address you gave Stripe for the receipt. Stripe may transfer data to the United States under the EU–US Data Privacy Framework and their own standard contractual clauses; see stripe.com/privacy. Legal basis: Art. 6(1)(b) GDPR, and Art. 6(1)(c) for the records we must keep for tax.

The concierge service

If you message the concierge, that conversation happens on WhatsApp and is subject to WhatsApp's own privacy terms, which we do not control. We keep the conversation only for as long as needed to help you during your stay, and we link it to your trip only by the short code shown on your itinerary.

Server logs

This service runs on a virtual server rented from Hostinger International Ltd., 61 Lordou Vironos str., 6023 Larnaca, Cyprus, which acts as our processor under Art. 28 GDPR. The server itself is located in Germany, so no third-country transfer arises from the hosting. Hostinger processes everything stored here, including your intake answers and your itinerary, by virtue of operating the machine.

The server produces standard technical logs — IP address, timestamp, the page requested, user agent — which exist to keep the service running and to investigate abuse, and are kept for a short period. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operating a secure service).

Cookies and analytics

None. This site sets no cookies and runs no analytics at all. Typefaces and the map library are served from our own server rather than a CDN, so loading any page here contacts no third party at all.

The map on an itinerary page is loaded only when you press the button, because it fetches map tiles from OpenStreetMap's servers and that is a third-party request we would rather you opted into. Pressing it sends your IP address to OpenStreetMap and to nobody else: the map software comes from this server, so no CDN is involved. Links to venue websites, to OpenStreetMap and to the BVG journey planner are ordinary links; following one takes you to that operator's site under their terms.

How long we keep things

Unpaid itineraries are deleted after 365 days, and we keep at most the 2,000 most recent — so a free itinerary may go sooner than that if the service is busy, and its URL then stops working. Deleting an itinerary deletes everything built from it. Paid itineraries are kept for as long as the tax record requires, currently ten years under §147 AO, because the payment is a commercial transaction. You can ask us to delete an itinerary sooner.

The automatic deletion above covers the itinerary itself. The copy on the internal job board is removed by hand, as the enquiry record it is, so if you want your request gone entirely say so and we will clear both.

Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object (Art. 21), and to complain to a supervisory authority — in Berlin, the Berliner Beauftragte für Datenschutz und Informationsfreiheit. Because we hold no identifying information about you, the practical way to exercise these rights is to send us the trip link: hello@conciergeberlin.de.