Privacy policy

This is a translation for your convenience. Only the German version is legally binding: Datenschutzerklärung.

Last updated: October 2026

This policy describes which personal data are processed when you visit polismedia.de and use the services offered there: for what purpose, on what legal basis, who receives them and how long they are kept. It also applies to the English pages under polismedia.de/en/ and to my profile page at polismedia.de/aboutme/.

In short: this website sets no cookies when you open it. Audience measurement only starts once you agree in the cookie banner, and YouTube videos only load when you click them. Appointment booking, the inquiry form, the chat, video calls and my digital assistant run on servers I operate myself. Where other providers are involved, the relevant section says so.

Contents:

Controller

The controller responsible for data processing on this website is:

polisMEDIA
Ralph Kühnl
c/o Tink Tank Landfried
Bergheimer Straße 147
69115 Heidelberg
Germany
Email: kontakt@polismedia.de
Phone: +49 172 6327800

Service providers and recipients at a glance

These providers receive personal data, each only for the purpose stated. The following sections give the details.

  • ALL-INKL.COM – Neue Medien Münnich, Friedersdorf, Germany: web hosting for this website and email mailbox
  • Hetzner Online GmbH, Gunzenhausen, Germany: data center for my own servers running appointment booking, the inquiry form, the chat, video calls and Wilma
  • Google (Google Ireland Limited, Dublin, Ireland; Google LLC, USA): calendar, Gmail, travel time calculation for in-person appointments, YouTube only after you click
  • Automattic (Aut O’Mattic A8C Ireland Ltd., Dublin, Ireland; Automattic Inc., USA): Jetpack Stats only with your consent, profile pictures via Gravatar
  • Zoom Communications, Inc., USA: video room for online appointments you book through the booking system
  • Mistral AI, Paris, France: answers in the chat on the profile page
  • Anthropic PBC, USA, and OpenAI (OpenAI Ireland Ltd., Dublin, with processing also in the USA): language model, speech recognition and speech output for Wilma, some features in Treffpunkt and my assistant system
  • Pushover, LLC, USA: push notifications to my phone about new inquiries and bookings
  • Telegram FZ-LLC, Dubai, United Arab Emirates: delivery of messages you leave for me via Wilma or at the door of my virtual office
  • Stripe Payments Europe Ltd., Dublin, Ireland: payment for webinar tickets

Transfers to third countries: For transfers to the USA, the European Commission’s adequacy decision on the EU-U.S. Data Privacy Framework applies (Art. 45 GDPR) where the recipient is certified under it; otherwise I rely on the European Commission’s standard contractual clauses (Art. 46(2)(c) GDPR) where the provider offers them. There is no adequacy decision for the United Arab Emirates, where Telegram is based. If you want to avoid this, write to me by email instead of using Wilma or the door of my virtual office.

Hosting and server logs

This website is hosted by ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany. The host processes the data on my behalf (Art. 28 GDPR) on servers in Germany.

Every time you open a page, your browser transmits data for technical reasons, which the server writes to log files:

  • IP address of the accessing device
  • date and time of access
  • requested address, status code and amount of data transferred
  • the page you came from (referrer)
  • browser and operating system (user agent)

The purpose is to deliver the pages, fend off attacks and find errors. The legal basis is Art. 6(1)(f) GDPR; my legitimate interest is secure and stable operation. The data are not combined with other sources. Under the current setting at my host, the logs contain the full IP address and are deleted after 190 days.

Some pages also load program components from servers I operate myself: the contact page fetches the booking form and the available times from n8n.ralphkuehnl.de, and the home and contact pages load the Wilma icon and a small script from meet.polismedia.de. Both servers are located in the data center of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Germany. They receive your IP address and your browser identifier in order to deliver the content and prevent misuse (Art. 6(1)(f) GDPR).

Cookies and consent

This website sets no cookies when you first open it. The cookie banner asks whether you agree to the “Statistics” category. Only the audience measurement with Jetpack Stats depends on it (next section). The “Marketing” category is currently not linked to any service. I checked this on October 27, 2026, with a fresh browser: before consent, no cookie and no request to any third-party service; after consent, only the two Jetpack Stats addresses.

The banner comes from the WordPress plugin Complianz and runs entirely on this web space; no data go to the plugin’s maker. It stores your choice in these cookies in your browser, each for 365 days: cmplz_banner-status, cmplz_policy_id, cmplz_consented_services, cmplz_functional, cmplz_preferences, cmplz_statistics and cmplz_marketing. They contain only your selection, no identifier of you as a person. I do not keep a copy of your choice on the server. The legal basis is § 25(2) no. 2 TDDDG (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz, the German Telecommunications and Digital Services Data Protection Act), because the site could not respect your choice otherwise, and Art. 6(1)(f) GDPR.

You can withdraw or change your consent at any time with effect for the future: use the “Manage consent” button at the bottom of the page or delete the cookies in your browser. If your browser sends the “Do Not Track” signal, the site treats it as a refusal of statistics.

In addition, WordPress places a technical entry in your browser’s session storage recording whether your browser can display emojis (wpEmojiSettingsSupports). It disappears when you close the tab and does not leave your device. Cookies that may be set when you comment, in the chat on the profile page and in Treffpunkt are described in the relevant sections.

Audience measurement with Jetpack Stats

Only if you agree to the “Statistics” category does the site load a script from stats.wp.com and report the page view to pixel.wp.com. Both belong to Jetpack, a service of Automattic Inc., 60 29th Street #343, San Francisco, CA 94110, USA. For users in the European Union, Aut O’Mattic A8C Ireland Ltd., Grand Canal Dock, 25 Herbert Pl, Dublin, D02 AY86, Ireland, acts as the controller.

The following may be processed: IP address, browser type and version, operating system, language setting, the previously visited page, date and time, and the page of this website you opened. Your approximate location can be derived from the IP address. Clicks on links on the page are also recorded. In my test, the measurement did not set any cookies.

The purpose is to see which content is read in order to develop the structure and topics of the website. In WordPress I only see aggregated figures such as views per page, referring pages and countries, not individual people.

The legal basis is your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). You can withdraw it at any time via “Manage consent”. If your browser sends “Do Not Track”, no measurement takes place.

Recipients and retention: Automattic may also process the data in the USA. According to its own statements, the provider bases such transfers on the European Commission’s standard contractual clauses. Automattic determines how long the raw data are kept; details at automattic.com/privacy.

Fonts, videos and images

Fonts

All fonts are hosted on this web space. Font services such as Google Fonts are not loaded.

YouTube videos

On the home page and on the workbench page about the self-op studio, a video is first shown only as a preview image served from this web space. Only when you click it does your browser load the player from youtube-nocookie.com. From then on, Google receives your IP address, information about your browser and device, the address of this page and your activity in the player. In my test, the player also loaded content from googlevideo.com, ytimg.com, gstatic.com, googleapis.com and google.com. Even in privacy-enhanced mode, YouTube may store or read information in your browser.

The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Data may be transferred to Google LLC in the USA (see transfers to third countries). The legal basis is the consent you give by clicking the video (Art. 6(1)(a) GDPR, § 25(1) TDDDG). If you prefer not to, you can watch the video directly on YouTube via the link below the image or skip it.

Profile pictures in blog posts

Below blog posts, WordPress shows the author’s profile picture. It loads from secure.gravatar.com, a service of Automattic (address above). Automattic receives your IP address and browser identifier in the process, even without consent. The legal basis is Art. 6(1)(f) GDPR; my interest is to show posts together with their author. You can object to this; the contact details are given above.

Links to other sites

Links to LinkedIn, YouTube or my other sites, for example, are plain links. Data only go to the respective provider when you click the link; that provider’s privacy policy then applies.

Contact by email and phone

If you write to kontakt@polismedia.de, the message arrives in the mailbox at my host ALL-INKL.COM and is forwarded from there to my Google mailbox (Gmail, Google Ireland Limited), where I handle my mail. Google may also process data in the USA. If you call me, I note down what I need to handle your request.

I process your information to answer your request. If it concerns an assignment or preparations for one, the legal basis is Art. 6(1)(b) GDPR, otherwise Art. 6(1)(f) GDPR (interest in answering inquiries). I delete the messages once the matter is settled, unless commercial or tax law requires me to keep them.

Inquiry form on the profile page

There is an inquiry form at polismedia.de/aboutme/kontakt.html. It asks for your first and last name and email address and, if you wish, your phone number, company, role and website, as well as your request, time frame, budget and message. The wording and time of your consent to processing, the page you came from and, if present, campaign tags from the address (utm parameters) are sent along.

The form sends the information to a small program on this web space. It uses your IP address to limit the number of requests per hour and passes the inquiry on to my own server n8n.ralphkuehnl.de (Hetzner, Germany). There, a fixed rule checks for spam without any third-party service, and the inquiry is stored in my own database. I am notified of new inquiries (next section).

The legal basis is Art. 6(1)(b) GDPR, because with your inquiry you initiate a possible assignment, and otherwise Art. 6(1)(f) GDPR. If you also tick the box for news, I store this consent as well (Art. 6(1)(a) GDPR); you can withdraw it at any time. I delete inquiries once they are settled and no retention obligation applies.

Notifications and my assistant system

When an inquiry comes in through the form or an appointment is booked, I receive a push notification on my phone via the Pushover service (Pushover, LLC, USA) and an email to my Google mailbox (Gmail). For inquiries, the push notification contains name, email address, phone number, company and request; for bookings, the key details of the appointment.

My own assistant system stores the same notifications on my server at Hetzner in Germany and deletes them after 14 days. When I ask it about new inquiries, appointments or emails, it sends the relevant content to the language model Claude from Anthropic PBC (San Francisco, USA) in order to answer me. No one but me makes decisions about you in the process.

The legal basis is Art. 6(1)(f) GDPR: I have a legitimate interest in noticing and answering inquiries and bookings quickly, including when I am on the road. For transfers to the USA, see transfers to third countries.

Blog comments

You can leave a comment below blog posts. Your name, your email address (it is not published), your website if you wish, the comment, the time, your IP address and your browser identifier are stored. The Antispam Bee plugin checks on this web space whether a comment is spam.

To show a profile picture next to the comment, WordPress creates an encoded string (hash) from your email address and uses it to ask Gravatar (Automattic) whether there is a picture for this address.

If you tick the box below the form, your browser stores your name, email address and website in cookies so that you do not have to enter them again for your next comment; these cookies expire after just under a year.

The legal basis is Art. 6(1)(f) GDPR: I want to enable discussion and detect misuse. The convenience cookies are your choice (§ 25(2) no. 2 TDDDG). Comments remain online with the post until you or I delete them; I will remove them on request.

Toby, the demo assistant

The home page features “Toby”, a demo of a personal assistant. Toby runs entirely in your browser with made-up data and without artificial intelligence. Whatever you type there does not leave your device and is not stored. The “Read aloud” button uses your browser’s speech output; depending on the browser, its maker may generate the voice over the internet, in which case only the fixed demo text goes there.

Appointment booking

If you book an appointment via this site, I process the information you enter in the booking form: name, email address, your phone number if you choose to give it, the selected type of appointment, date and time, and what you tell me about your request. For on-site appointments, the address where we meet is added.

I store these data in my own database on a server I operate (n8n.ralphkuehnl.de). The legal basis is Art. 6(1)(b) GDPR: the processing is necessary to carry out the appointment agreed with you.

Why the address is sent to a map service

If you are looking for an on-site appointment, I first ask for your postal code and town and later for the exact address. Both are transmitted to Google Maps, for a specific reason: the system uses them to calculate how long the trip takes and whether it fits between my other appointments that day. Without this calculation, you would be offered a time at which I cannot possibly be with you.

Only the address is transmitted, without a name and without any other details of the appointment. I store the result, that is distance and travel time, in my own database so that the same route does not have to be requested again and again. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Data may also be transferred to the United States. If you book an online appointment instead of an on-site one, this step does not apply at all.

Calendar, video call and email

The appointment is entered in my Google calendar. You receive a calendar invitation for it; for this, your email address is transmitted to Google. For on-site appointments, I also enter the trips there and back as separate appointments in my calendar. These entries contain the address of the meeting place and are visible only to me.

For online appointments, a video room is created at Zoom. The provider is Zoom Communications, Inc., 55 Almaden Boulevard, 6th Floor, San Jose, CA 95113, USA. The title and time of the appointment are transmitted to Zoom. Your email address is not passed on to Zoom; you receive the access link from me. I send the confirmation and reminder emails via Gmail; the provider is Google Ireland Limited, address as above.

How long the data are kept

Using the link in the confirmation email, you can reschedule or cancel your appointment yourself at any time. I keep bookings for as long as retention periods under commercial and tax law require, for no more than ten years. I delete appointments that are not related to an invoice after two years. The stored distances contain no names and are renewed or removed after twelve months.

Who operates this booking system

No external service provider is used for managing appointments. I developed the booking system myself and operate it on my own server in Germany. There is no account with a booking provider through which your data would pass.

The system was built with the help of artificial intelligence. This concerns the development, not the operation: no artificial intelligence is involved when you book. The information from your booking form is not passed to a language model, and no AI decides which appointment you get. Which times are offered follows from fixed rules, my calendar and the calculated travel time.

These statements apply to appointment booking. Something different applies to the chat on my profile page; it is described in the following section.

Chat on the profile page

My profile page at polismedia.de/aboutme/ has a chat window. There, a language model answers questions about my work. The window only opens when you click it. You can read the whole page without using the chat.

Nothing is sent without your consent

Before you can write, you tick a checkbox. Until then, the input field and the send button stay locked. The legal basis is Art. 6(1)(a) GDPR, that is your consent. You can withdraw it at any time: the chat window has a button “Einwilligung zurücknehmen” (withdraw consent) for this, and an informal message to me is just as sufficient. The withdrawal takes effect for the future. At your request, I delete messages that have already been stored.

What is processed

The following are stored: your message, the model’s answer, a random identifier of the conversation, the time, the page you were on, your IP address, your browser’s identifier (user agent) and the wording of the consent that was shown to you. I store the IP address in full; it is used to detect misuse and to limit the number of requests per hour.

If you write your name or contact details in the chat, these are stored as well. Please do not enter anything there that goes beyond an initial inquiry. For everything else, the inquiry form and appointment booking are available.

Who generates the answer

Your message is transmitted to Mistral AI, a company based in Paris, France. The models used are mistral-large-latest for the answer and mistral-embed for searching my own specialist texts. The processing takes place within the European Union; it does not involve a transfer to the United States.

The answers come from a language model and may be wrong. They are initial information, not advice and not a commitment. No automated processing decides on your request; the chat merely prepares a conversation with me.

Where the data are stored and for how long

Your message first goes to a small program on this web space (polismedia.de/aboutme/chat.php), which passes it on, together with your IP address and browser identifier, to my own server n8n.ralphkuehnl.de. The server is located in the data center of Hetzner Online GmbH in Germany. There, the data are stored in a database I operate myself. I delete the conversation log after six weeks. I delete the conversation memory, which the model uses to keep the context within a conversation, seven days after the last message. A daily routine takes care of both.

In addition, the history of the current conversation is kept in your browser’s session storage so that the window is not empty when you change pages. This storage is cleared as soon as you close the browser tab. The chat does not set a cookie, and the profile page does not embed any external services when it is opened.

Video calls and my virtual office (Treffpunkt)

For video calls, I use my own service “Treffpunkt” (German for “meeting point”) at meet.ralphkuehnl.de, meet.pawcademy.eu and meet.polismedia.de. It runs entirely on my own server at Hetzner Online GmbH in Germany, including the relaying of video and audio. You need no account and no app; everything your browser loads for it comes from my server. For technical reasons, the server processes your IP address and your browser’s identifier.

During the call

Video and audio are transmitted in encrypted form via my server to the other participants and are not stored in the process. Chat messages and reactions go only to the participants and are not stored either. What is recorded is the name you enter when joining, your role in the call and the times you joined and left. I delete these entries after 90 days.

A blurred or replaced background and the noise filter for the microphone are calculated exclusively by your browser. Your own background images stay on your device and are not uploaded. Files shared in the chat and the shared whiteboard go directly to the other participants over the meeting connection; my server does not store them.

On request, I set up a meeting with end-to-end encryption. Video, audio, chat and files are then encrypted in the browsers; the key is contained only in the link (after the # sign) and does not reach my server. Anyone who has the complete link can take part – so only pass it on to participants.

Recordings and transcripts

I only record a call if I announce it beforehand; while a recording is running, all participants see a clear notice.

For a transcript, each person’s audio is recorded separately. My browser uploads the audio segments to my server; from there they are sent to OpenAI (OpenAI Ireland Ltd., Dublin, with processing also by OpenAI in the USA) to be converted into text. As soon as the transcript is finished, I delete the audio recordings. I keep the transcript with the names of the speakers for following up on the call and delete it as soon as I no longer need it for that. From the transcript, my server has the language model Claude by Anthropic PBC (San Francisco, USA) create minutes with key points and tasks, which I keep in the same way; on request, I send them to the participants by email.

I can also record a call as a video, that is video and audio as they appear and sound on my screen. My browser stores this file exclusively on my own computer; it goes neither via my server nor to any other service. I also keep it only for following up and delete it as soon as I no longer need it for that.

The legal basis for a recording is your consent (Art. 6(1)(a) GDPR). If you do not agree, just say so, and I will not record. You can withdraw consent you have given at any time.

Live captions

In some meetings, I switch on live captions; all participants can see this. Your browser then sends your individual utterances via my server to OpenAI to be converted into text; the text is distributed to the other participants. Anyone who wants to read captions in another language has the lines translated by Claude (Anthropic) via my server. Audio and text are not stored in the process. You can switch off captioning of your own voice in the meeting at any time. The legal basis is Art. 6(1)(f) GDPR (comprehensibility, including across language barriers).

AI assistance in meetings

In some meetings, I switch on AI assistance; all participants then see the notice “KI hört mit” (AI is listening). As with live captions, your browser sends your utterances via my server to OpenAI to be converted into text. My server keeps the transcript in working memory only and has Claude (Anthropic) use it to create a short summary for latecomers, sticky notes for the shared whiteboard and answers from my digital assistant Wilma when she is addressed in the meeting. If you wish, translated utterances can be read aloud to you; the voice output is generated by OpenAI. The transcript is not stored and is deleted at the latest at the end of the meeting; voice outputs are kept in working memory for no more than 15 minutes. You can switch off transcription of your own voice at any time. The legal basis is Art. 6(1)(f) GDPR (collaboration and comprehensibility in the meeting).

Tickets for webinars

Some webinars require tickets. When you register or order, I store your name, email address and the status of the ticket, and for paid tickets also the identifiers of the payment transaction, in order to send you your personal access and check whether it is valid. Each ticket is valid on one device at a time; for this, I keep track of which session it is currently being used in. Payment is handled by Stripe (Stripe Payments Europe Ltd., Dublin, Ireland, with processing also in the USA); your email address and the payment details you enter at Stripe are sent there. Stripe creates the payment receipt. I delete the ticket data 30 days after the webinar; I keep booking and invoice records for as long as tax and commercial law require. The legal basis is Art. 6(1)(b) GDPR (contract or registration).

Invitations and rooms

If I invite you by email, the invitation is sent to you via my Google Mail account (Google Ireland Ltd., Dublin, with processing also in the USA). I note the recipient address and time with the room and delete this note after 90 days. I delete rooms for individual appointments about one week after the appointment.

If I invite someone spontaneously, I send the link from my own phone via the messenger of choice or by text message. For people I bring in more often, I store their name and mobile number in my Treffpunkt for this purpose until I delete the entry. Such a personal link is valid for six hours.

My virtual office

My virtual office is at meet.ralphkuehnl.de/r/ralph (short link: /buerobesuch on my websites). Its door is open, set to knock or closed. Treffpunkt reads from my calendar whether I am currently in an appointment; it only sees the start and end of my appointments, no information about the people involved.

If you knock, I receive your name as a notification on my devices. This push message is sent in encrypted form via the push service of the respective browser maker, which cannot read its content.

Door viewer: if your camera is switched on, I see a small still image from it every few seconds while you are waiting, so that I know who is at the door. The image is kept only in my server’s working memory, is not stored and is gone as soon as you are let in, turned away or leave. The page points this out before you knock; in the waiting room, you can cover the viewer or switch off the camera.

Messages at the door: if the door is closed, you can leave me a text or voice message. A voice message is converted into text via OpenAI. The message is delivered to me via the messenger Telegram (Telegram FZ-LLC, Dubai, United Arab Emirates). I delete the audio recording after delivery, and the text, the transcript and my replies after 90 days. You can read my reply at a link that only you know.

For conversations with my digital assistant, the section “Wilma – digital assistant (AI)” applies.

Stored in your browser

When you join, Treffpunkt sets a technically necessary cookie with a random identifier of your device (valid for one year). It uses this to assign host rights and exclusion from a room. In addition, your browser remembers your name, your device selection and chosen backgrounds in its local storage for next time; this information does not leave your device. The legal basis is § 25(2) no. 2 TDDDG (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz, the German Telecommunications Digital Services Data Protection Act).

Legal basis and transfer to third countries

If a call relates to an inquiry or an assignment, the legal basis is Art. 6(1)(b) GDPR; otherwise it is Art. 6(1)(f) GDPR: I have a legitimate interest in a secure video conferencing service that I operate myself and that works without accounts and third-party providers. Transfers to the USA are covered by the EU Commission’s standard contractual clauses (Art. 46 GDPR) and, where the respective provider is certified, by the EU-US Data Privacy Framework (Art. 45 GDPR).

Wilma – digital assistant (AI)

On some pages, you can talk or write to Wilma, my digital assistant. Wilma is an AI. She answers questions about my services and about the content of my websites, looks for available appointments with you, prepares a booking or passes on a message to me. Using her is voluntary; you can reach me just as well via the contact form, email or appointment booking.

Where Wilma runs

Wilma runs on my own server (meet.polismedia.de) at Hetzner Online GmbH in Germany. Until you click “Ask Wilma” or “Talk to Wilma”, this page loads only the Wilma icon and a small script from there. For technical reasons, my server receives your IP address and your browser’s identifier. The conversation itself and the services named below are only loaded after the click. During the conversation, I use your IP address in working memory only, to limit misuse (for example the number of conversations per hour); it is not stored with the conversation. Wilma does not set cookies. Your browser merely remembers in its session storage whether Wilma’s short introduction has already been shown.

Which services are involved

If you speak, your browser only records what you say once you allow access to the microphone, and sends it to my server. From there, the recording is sent to OpenAI to be converted into text; it is not kept afterwards. You can also write instead and switch off the microphone at any time.

Your message or its transcript is sent, together with the conversation so far, to the language model Claude by Anthropic PBC (San Francisco, USA), which formulates Wilma’s answer. Wilma’s answers are converted into speech by OpenAI (OpenAI Ireland Ltd., Dublin, with processing also by OpenAI in the USA).

Transfers to the USA are covered by the EU Commission’s standard contractual clauses (Art. 46 GDPR) and, where the respective provider is certified, by the EU-US Data Privacy Framework (Art. 45 GDPR). According to both providers, data processed via their programming interfaces are not used to train their models and are deleted after a short period.

What is stored and for how long

I do not store the wording of the conversation. It is kept in working memory only while the conversation is running and is discarded when you close the window or when nothing happens for 30 minutes. Afterwards, the language model creates a short summary for me: what it was about, what came of it (for example a booked appointment or a message left for me), what is still open and, if you gave it, your name. In addition, I store the time, duration, the page on which you opened Wilma and the number of conversation turns. I delete these summaries automatically after 90 days.

Appointments and messages to me

Wilma never books on her own. She shows you a summary of the appointment; only when you confirm it does my booking system create the appointment. The section “Appointment booking” of this policy applies to this.

If you ask Wilma to pass something on to me, I store your message with your name and, if given, contact details on my server and delete it after 90 days. It is delivered to my phone via the messenger Telegram (Telegram FZ-LLC, Dubai, United Arab Emirates).

Legal basis and limits

Where an inquiry, an appointment or a possible assignment is concerned, the legal basis is Art. 6(1)(b) GDPR; otherwise it is Art. 6(1)(f) GDPR: I have a legitimate interest in answering inquiries in a friendly and prompt way even when I am not available myself. You grant access to the microphone in your browser and can withdraw it there at any time.

Wilma’s answers come from a language model and may be wrong. Wilma relies only on the content of my websites, the appointments available for booking and my instructions; what is binding is what I confirm to you myself. No automated decision is made about you.

Your rights

You have the right to

  • access the data stored about you (Art. 15 GDPR),
  • rectification of inaccurate data (Art. 16 GDPR),
  • erasure (Art. 17 GDPR),
  • restriction of processing (Art. 18 GDPR),
  • data portability (Art. 20 GDPR).

Objection (Art. 21 GDPR): Where I base processing on my legitimate interest (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. I will then stop processing the data unless there are compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defense of legal claims.

Withdrawal (Art. 7(3) GDPR): You can withdraw consent at any time with effect for the future. Processing carried out until then remains lawful.

There is no automated individual decision-making, including profiling (Art. 22 GDPR). You are not obliged to provide me with data. Without your information in the form, the booking or the chat, however, I cannot handle your request there.

An informal message to kontakt@polismedia.de is enough for any request.

Complaints to the supervisory authority

You can lodge a complaint with a data protection supervisory authority, in particular in the member state of your residence, your place of work or the place of the alleged infringement (Art. 77 GDPR). The authority responsible for me is:

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg)
Lautenschlagerstraße 20
70173 Stuttgart
Germany
Phone: +49 711 615541-0
Email: poststelle@lfdi.bwl.de
Web: www.baden-wuerttemberg.datenschutz.de

Data security

This website is only delivered encrypted (HTTPS). Beyond that, I use technical and organizational measures to protect your data against manipulation, loss, destruction and unauthorized access, and I adapt them to the state of the art.

Changes to this privacy policy

If the services of this website or the legal requirements change, I will update this policy. The version published here at the time of your visit applies.