Privacy Policy

This policy explains which personal data are processed when you visit this website or contact us. It also explains the purposes, legal bases, recipients and your rights.

1. Controller

2. General legal bases

Depending on the situation, processing is based on:

• Article 6(1)(b) GDPR when processing is necessary to answer a request relating to a possible contract or to perform a contract;
• Article 6(1)(c) GDPR when processing is required to comply with a legal obligation; or
• Article 6(1)(f) GDPR where processing is necessary for our legitimate interests, especially providing a secure, reliable website, preventing misuse and handling ordinary business communication.

Where we rely on legitimate interests, we balance those interests against the rights and freedoms of the person concerned.

3. Website delivery and security through Cloudflare

The website is delivered through Cloudflare's network and Cloudflare Workers. When a page is requested, technical data such as the IP address, date and time, requested URL, referrer, browser and operating-system information, request identifiers and security signals may be processed. This is necessary to deliver the website, defend against attacks, diagnose faults and maintain availability.

The legal basis is Article 6(1)(f) GDPR. Our legitimate interests are secure and reliable website operation and protection against misuse. The service provider is Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA. Cloudflare may process data outside the EEA. Cloudflare's data-processing terms provide safeguards including the EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. Details are available in the Cloudflare Data Processing Addendum.

Cloudflare generally acts as our processor when delivering and protecting the website. For specific security signals used to improve Turnstile and the underlying Challenge Platform, Cloudflare states that it also acts as an independent controller based on its own legitimate interests. These signals can include IP address, TLS and browser characteristics, user-agent data, site key, origin and challenge interaction data. See the Cloudflare Turnstile Privacy Addendum.

Cloudflare's technical security data are retained under the enabled service configuration and its contractual privacy and retention terms.

4. Self-hosted Plausible Analytics

We use Plausible Community Edition to understand aggregate website use and improve content, navigation and conversion paths. The analytics service is operated by us at analytics.cloud-cave.de; no Google Analytics service is deployed. Plausible records page views, referral and campaign source, general browser, operating-system, device and country information, engagement duration and scroll depth. We additionally measure three controlled website goals: a programme-card click to the contact page, a telephone-link click and a contact form accepted successfully by our server.

Plausible runs in its cookieless standard configuration. It does not set analytics cookies, use browser storage, create a persistent cross-site identifier or send analytics data to Google. Our integration disables automatic form, file-download and outbound-link capture. Goal properties are limited to controlled categories such as the selected programme, service and private, corporate or departure enquiry type; names, email addresses, telephone numbers, free-text messages and document contents are not included. Before delivery, the website removes fragments and uncontrolled query parameters from the tracked URL and strips query parameters from the referrer. Only common utm_* campaign parameters that pass a basic safety filter can remain for source attribution.

Like every web request, the request to our Plausible server technically carries the IP address and user-agent header. Plausible CE uses them transiently with a rotating daily salt to calculate aggregate unique-visitor figures; its standard analytics database does not retain the raw IP address or full user agent. Infrastructure security logs are treated as described in section 3. Processing is based on Article 6(1)(f) GDPR. Our legitimate interests are measuring aggregate demand, finding usability problems and improving the effectiveness of this website without persistent identifiers or advertising profiles. Because this configuration does not store information on or read information from the visitor's device, it is not controlled by the consent banner. Plausible explains its privacy model in its security documentation.

5. Contact enquiries

If you use the contact form, email us or call us, we process the data you provide to understand and answer your enquiry. The form requires the client type, your name and email address, target date or timeframe, starting location, a short household or assignee overview and the primary support need. Depending on the enquiry, you may optionally provide an organisation, telephone number, preferred target area or destination, selected programme and additional message. The form also creates a submission UUID and client timestamp to prevent duplicate email delivery and processes the technical Turnstile verification token described below. The UUID is not used as a visitor or advertising identifier. Please do not send passport numbers, identity documents, health information or other sensitive documents through the form.

Processing is based on Article 6(1)(b) GDPR where your request concerns pre-contractual steps or an existing engagement. For other business enquiries, it is based on Article 6(1)(f) GDPR; our legitimate interest is responding to relevant communication. Required fields are necessary for us to identify and answer the request. Without them, the form cannot be submitted.

6. Transactional email delivery and hosting through Microsoft 365

Form submissions are sent from our dedicated noreply@relocmuc.de mailbox through Microsoft Graph and Exchange Online so that Irene Adomaitis receives the enquiry and you receive a delivery confirmation. Customer replies are directed to Irene; Irene's notification can be answered directly to the email address entered in the form. Microsoft 365 therefore processes sender and recipient details, message content and technical delivery data on our behalf.

Processing follows the same legal basis as the enquiry under section 5. Microsoft acts as a service provider under its applicable data-protection terms and may use subprocessors or process data outside the EEA subject to the safeguards in its product and services data-protection addendum. See the Microsoft Products and Services DPA.

7. Cloudflare Turnstile

The contact page loads the visible Cloudflare Turnstile widget to distinguish genuine form submissions from automated abuse. Turnstile may process connection, browser, device and interaction signals and produces a short-lived verification token. According to Cloudflare, Turnstile does not read the form content. The widget itself is loaded only on the contact page.

Cloudflare may additionally inject invisible Challenge Platform or JavaScript-detection code into other HTML pages when the zone's security features require it. Processing on our side is based on Article 6(1)(f) GDPR. Our legitimate interest is protecting the website, contact form, mail systems and visitors from spam and abuse. To the extent that this necessary security technology accesses or stores information on the device, section 25(2) no. 2 TDDDG applies. Further information is available in the Turnstile Privacy Addendum and Cloudflare Challenge documentation.

8. Cookies, local storage and similar technologies

A technical Google Tag Manager base container is delivered through Cloudflare's Google Tag Gateway and may load before a visitor makes a choice. This can create a first-party gateway request on relocmuc.de and a limited Google Tag Manager health or bootstrap request. When there is no valid opt-in, Consent Mode keeps every optional purpose denied and the Google Ads base tag is not triggered, so no Ads, Analytics or conversion measurement hit is sent. Depending on the enabled protection feature and the assessed traffic, Cloudflare security functions may set necessary identifiers such as cf_clearance, __cf_bm, _cfuvid or short-lived cf_chl_* diagnostic cookies. Not every visitor receives each identifier.

The open-source SafeBanner consent manager stores your choice in first-party browser storage under safebanner_consent. The record contains the time of the choice and whether the necessary, analytics and marketing categories were accepted. It is used only to remember and honour your choice and is not sent to SafeBanner, Google or another marketing provider. Necessary storage is based on section 25(2) no. 2 TDDDG because it is required to provide the privacy control you request. SafeBanner is served directly from relocmuc.de, without a separate SafeBanner or public-CDN request. The record remains until you change the choice or clear browser storage.

Google Ads conversion measurement is off by default. Without a valid opt-in, ad_storage, analytics_storage, ad_user_data and ad_personalization are denied. Cloudflare is configured to hide the visitor's original IP from Google at the gateway layer. “Accept all” grants all four signals. In SafeBanner's custom settings, Analytics controls analytics_storage, while Marketing controls ad_storage, ad_user_data and ad_personalization. Marketing consent allows the consent-gated Google Ads base tag to initialise conversion measurement and the defined conversion events described below. The base tag is configured not to send an automatic page view, Google Signals, ad-personalisation measurement or a remarketing event. Google Analytics and remarketing tags are not deployed. Withdrawing consent returns all four signals to denied. The legal basis is your consent under Article 6(1)(a) GDPR and, where information is stored on or read from your device, section 25(1) TDDDG. You can reject, withdraw or change the optional choice at any time through “Privacy choices” in the footer. See our cookie information for a concise overview.

With marketing consent, Google Ads can measure three defined website interactions: a click from a programme card to the contact page, a click on a telephone link and a contact form that our server has accepted successfully. The explicit event payload contains only controlled categories such as private, corporate or departure enquiry, the selected service and, where applicable, the programme key. The telephone event does not contain the telephone number. A telephone-link click is only a secondary signal; a separately configured call from an advertisement is counted as a qualified lead only if Google's call measurement records at least 60 seconds.

Enhanced Conversions and Enhanced Conversions for leads are enabled at Google Ads account level and managed through the Google tag. After marketing consent and in connection with a measured form lead, the tag's automatic detection may inspect the page for strings matching eligible first-party contact-identifier types, such as the email address and, where provided and detected, name, telephone or address-related data. Google normalises these identifiers and applies one-way SHA-256 hashing before transmission so that they can be matched with signed-in Google accounts for conversion attribution. Hashing does not make the data anonymous to Google. Our own conversion event does not include the additional message, household overview, timing, origin or target area as event parameters; document contents cannot be included because the website does not accept uploads. The account-level Enhanced Conversions for leads setting can also support later matching of an imported offline lead outcome, but the website itself does not currently upload offline outcomes. Google explains the current process in its Enhanced Conversions documentation.

Google Ads may process the page URL and title, referrer, browser and device information, Consent Mode signals, an advertising-click identifier where present and the defined event data for attribution, reporting and campaign optimisation. After consent, first-party Google Ads identifiers such as _gcl_aw may be stored to associate an advertising click with a later conversion. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; Google group companies and service providers may process data outside the EEA subject to Google's applicable transfer safeguards. Further information is available in the Google Privacy Policy, Google's explanation of website conversion measurement and use of conversion data.

9. Locally served fonts

The website's fonts are bundled during the build and served from relocmuc.de. A visitor's browser does not contact Google Fonts to display them.

10. Recipients and international transfers

Access is limited to persons and service providers who need the data for website operation, security, email delivery and answering enquiries. The principal service providers are Cloudflare and Microsoft 365 as described above. Data may also be disclosed where required by law or necessary to establish, exercise or defend legal claims.

Where data are processed outside the EEA, the relevant provider's adequacy mechanism, EU Standard Contractual Clauses and supplementary safeguards apply as described in its current data-processing terms.

11. Retention

Enquiry data in our active business records are kept only for as long as necessary to answer the request and manage any resulting engagement. If no contract results and no dispute or legal duty requires continued storage, the data are removed after the enquiry purpose has ended. Contract, invoice and business correspondence may be retained for the applicable statutory periods. Aggregated Plausible event data remain in our self-hosted analytics database until they are deleted under our analytics retention policy or the site is removed. Cloudflare and Microsoft retain provider-side technical, security and delivery data under the enabled service configuration and their contractual terms. The exact operational deletion schedule is reviewed with the relevant account settings and legal retention duties.

12. Your rights

Subject to the statutory conditions, you have the right to:

• access your personal data (Article 15 GDPR);
• rectification of inaccurate data (Article 16 GDPR);
• erasure (Article 17 GDPR);
• restriction of processing (Article 18 GDPR);
• data portability (Article 20 GDPR); and
• object to processing based on Article 6(1)(e) or (f) GDPR (Article 21 GDPR).

To exercise a right, contact irene.adomaitis@relocmuc.de. You also have the right to lodge a complaint with a supervisory authority. The authority responsible for many private businesses in Bavaria is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.

13. Automated decisions

We do not use the information submitted through this website for automated decision-making or profiling within the meaning of Article 22 GDPR.

14. Changes to this policy

We update this policy when the website, service providers or legal requirements change. The date at the top identifies the current published version.