Mighty QuinnConsultingMighty Quinn Consulting — home

Privacy

What this website processes, why, and on what legal basis.

Last updated 30 August 2026

Not legal text yet. A checklist of what the finished policy has to cover, plus the technical facts about this site that it has to describe accurately. Needs legal review before launch.

The German version is the authoritative one. Art. 12 GDPR requires the information to reach data subjects in language they understand; this English page is a translation for information.

Controller and contact

The controller for the purposes of Art. 4(7) GDPR is Mighty Quinn Consulting GmbH & Co. KG. Full details of the company, its representation and its register entry are in the imprint.

Everything to do with data protection — access, rectification, erasure, objection, complaint — goes to one mailbox:

datenschutz@mqc.one

Requests sent there are handled there, and are not reused for any other purpose.

No data protection officer is appointed. None is required: fewer than 20 people here are constantly engaged in the automated processing of personal data (§ 38(1) BDSG), our core activity involves neither large-scale regular monitoring nor special categories of personal data (Art. 37(1) GDPR), and none of the processing described here requires a data protection impact assessment. Data protection enquiries are answered from the mailbox above.

There is exactly one processing activity beyond serving the pages themselves: answering contact enquiries.

  • Enquiries with a contractual dimension — a project enquiry, say — are processed under Art. 6(1)(b) GDPR, because answering them is a step taken at your request prior to entering into a contract.
  • All other enquiries are processed under our legitimate interest in answering business correspondence, Art. 6(1)(f) GDPR. You can object to that at any time under Art. 21 GDPR.

Name, email address and message are necessary for this; without them we cannot reply. There is no statutory or contractual obligation to use the form.

What this site actually does

Written down here so the policy describes reality rather than a template:

  • Hosted in Germany. The site runs on STACKIT, a German cloud platform, in data centres in Germany. No service outside the EU is involved, and there is no transfer to a third country.
  • Server-rendered pages from our own infrastructure. No third-party CDN and no external font provider: the Montserrat typeface is served from this same server. Your browser therefore makes no request to a Google Fonts host, and sends no IP address there.
  • Media (images, icons) is served either from this same server or from assets.mqc.one, a host we control. Nothing is loaded from a third-party image CDN, and images are resized on our own server rather than by an external service.
  • No cookies are set at all — not even for the language choice. The language lives in the URL (/en/…, /de/…). The bare domain always redirects to the German version; the browser's language setting is not read for that.
  • One setting is stored locally. If you pick "Light" or "Dark" by hand in the header, the browser keeps that choice under the key mqc-theme in localStorage, so it survives to the next visit. It is not a cookie: the value is never transmitted to our server and is only ever read by the browser itself. It holds nothing but light or dark, allows no recognition of a visitor, and is exempt from consent as a setting you explicitly asked for. On the default, "Follow system setting", nothing is stored at all — your device's setting decides on its own. You can remove the entry by switching back to the system setting, or through your browser settings.
  • No analytics are installed yet. If that changes, the intended choice is a self-hosted, cookie-free setup (Plausible or Matomo in no-cookie mode) so no consent banner is required for it.
  • Server logs are written by the ingress. Retention period and whether IP addresses are truncated: TODO — confirm with whoever operates the cluster.
  • The contact form posts name, email address and message to our own server, which delivers them through Microsoft Graph to one Exchange Online mailbox. Nothing is stored in a database and nothing goes to a third-party form service. The submitter's IP address is held in memory briefly for rate limiting and is not persisted.
  • Microsoft 365 is configured so that emails are stored within the European Union (EU Data Boundary). However, with cloud services of this nature, it cannot be completely ruled out that U.S. authorities may gain access to data or that data may be transferred to the United States as part of support and diagnostic processes. We ensure the security of data transmission and processing as follows:
    • Data Processing: We have a data processing agreement with Microsoft based on the Microsoft Data Protection Addendum (DPA).
    • EU-US Data Privacy Framework (TADPF): Microsoft is certified under the U.S. data protection agreement, which ensures an adequate level of data protection in accordance with Article 45 of the GDPR (the agreement is currently known as the "U.S. Cloud Act").
    • EU Standard Contractual Clauses (SCCs): As an additional safeguard, we have agreed with Microsoft on the EU Standard Contractual Clauses in accordance with Article 46(2)(c) of the GDPR, which are incorporated into the DPA.

Retention

  • Contact form messages are deleted from the mailbox within 14 days of arrival. If an enquiry becomes something we need to keep longer — one that turns into a proposal, say — it moves into the process meant for that and follows its retention rules, not this one.
  • Server Logs for Ingress: The STACKIT Server Audit Log stores data for 90 days and is then deleted. The retention period for application logs can be configured between 1 and 180 days. For our website, XXX TODO: Enter the actual number of days here. days are currently stored. STACKIT does not truncate IP addresses.
  • The colour scheme setting lives only in the visitor's browser and stays there until they remove it. We have no access to it.

Your rights

Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20), and the right to object to processing based on legitimate interests (Art. 21).

A message to datenschutz@mqc.one is enough for any of them.

Separately, you have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). Ours — because we are established in Ilsfeld, in Baden-Württemberg — is:

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg Lautenschlagerstraße 20, 70173 Stuttgart, Germany https://www.baden-wuerttemberg.datenschutz.de

Unlike some German states, Baden-Württemberg has one authority covering both public and private bodies.

Still open

  • Legal review of the whole policy before launch
  • Re-check the supervisory authority's address on the day of publication — authority addresses change, and this one sits in a legal notice
  • Server log retention number of days

Notes for whoever maintains this

Contact form submissions are answered and nothing more. If they are ever fed into a mailing list or a CRM, that is a new purpose: it needs a separate, unbundled opt-in on the form and a corresponding section here.

The current legal baseline is the GDPR plus the TDDDG — the law formerly known as TTDSG, renamed in May 2024. The EU "Digital Omnibus" proposal that would loosen consent requirements is still in negotiation and is not law; this policy describes the rules as they stand.