Assessing Microsoft 365 Copilot for a GxP workflow
Copilot can find information and draft a convincing answer in seconds. Before using that answer for a quality task, check whether it draws on the correct effective document and whether the task permits this use. Start the assessment with the intended use.
Assess the specific task, authorised sources, access permissions and how a qualified person will check the output. Approval of a bounded use does not approve the product for every GMP activity. The 2025 Annex 22 consultation draft excludes generative AI and large language models from its proposed scope for critical applications. Evaluate the actual use under the applicable requirements, including the consequence of a reviewer accepting an incorrect answer.
Identify the product and the specific task
Microsoft documentation now also uses the name Microsoft Copilot for Microsoft 365 Copilot. Earlier names remain in use. Identify the enterprise service, licence, enabled features and data access that your assessment covers. Assess consumer products, extensions and custom agents separately where their scope or data flows differ.
Describe the task more precisely than “assistance”. Structuring meeting notes, assessing a deviation and preparing a batch decision have different implications. Define the inputs, output, users and permitted follow-up action. Effects on quality and data integrity may be indirect. If staff read only a generated summary, the assistant may become the effective basis for a decision.
As of 14 October 2026, Annex 22 was a 2025 consultation draft. It excluded generative AI and LLMs from its proposed model scope and advised against their use in critical GMP applications. The draft conferred no general authorisation and did not itself create a binding prohibition. Assess the actual process against the applicable regulatory framework.
A statement that a human reviews the output does not amount to approval for general use. Actual impact determines criticality. Describe which content the model can influence and how errors would be detected. The responsible process owners decide the allowed use and its limits. Resolve open questions before relying on an output. This guide does not recommend assigning autonomous quality decisions to a general-purpose language assistant.
Review access permissions before introducing Copilot
Microsoft describes an enterprise service that makes organisational content available according to existing user permissions. If those permissions are already too broad, users may discover information they should not have. Review SharePoint libraries, groups, guests and other connected sources. A sharing link that drew little attention for years may become consequential once the content is searchable in a new way.
Use representative roles. A person authorised for site A might have no right to see confidential matters at site B. Test direct questions and summaries. Seeing a citation does not establish that permissions were enforced. Assess extra data paths created by extensions and agents separately. Check that the actual enterprise configuration supports the vendor's description of access controls.
An answer can accurately summarise the wrong source. Decide which documents govern the task. Keep drafts, historical revisions and current approved instructions distinguishable. Check whether users can tell which source the answer relies on and where it applies. Convincing wording alone does not establish that the right document was used.
Compare answers with independently prepared reference information. Include omissions, exceptions, tables and conflicting sources. Open the cited passage and check whether it supports the claim. Define when the assistant must state that it cannot answer reliably and direct the user to the original document or responsible contact. Unsupported additions drawn from general model knowledge can mislead users in a regulated process.
Worked example of a question about an internal SOP
Suppose an employee asks how to handle an illegible label. The collection contains an effective SOP, an earlier revision and a draft for Site B. The permitted use is to find the correct source for Site A and direct the employee to the relevant passage for review. The tool must not authorise the process or generate an alternative action. Assess this use case with the responsible process experts before the pilot.
Include an unambiguous question, a question that omits the site, conflicting source documents and a user without access. Expect an appropriate answer or a clear statement of the limitation. Evaluate it against prepared sources and criteria. The matrix is our test aid. It gives no assurance about universal Copilot functionality or regulatory approval of this use case.
Test cases for the SOP question
Test case
Expected control
Observable result
Correct SOP
Applicable source and revision
Relevant passage in the original
Site unspecified
Establish the missing context
No unsupported assignment to a site
Earlier revision
Distinguish which revision is valid
The historical version is not presented as current
Define what the reviewer checks, including the source, completeness, figures, exceptions, scope and permitted use. A general instruction to check every AI output is inadequate if the reviewer lacks time or suitable references. Reviewers need process knowledge and a clear route for handling deviations. Match the review to the consequences of using the answer.
Test the control with deliberately incorrect outputs. Does the reviewer detect an omitted exception or a wrong number? Do they know when the answer must not be used? A signature without effective review does not adequately control the risk. Record permitted tasks and any prohibited or unapproved uses in terms staff can follow. Informal demonstrations do not establish that routine use is safe.
For the specified enterprise service, Microsoft says it excludes prompts, responses and data accessed through Microsoft Graph from foundation model training. Check the product, contractual terms and features in use. Also assess storage, retention, web search, extensions and actual data flows. This enterprise commitment does not extend automatically to consumer products.
A cloud assistant can change when its service, model, features or source connections change. Identify which changes matter and how you will learn about them. Rerun representative questions after suitable triggers. A test report covers the assessed scope and date. Assign responsibility for monitoring the service and investigating new failure patterns.
Record the task, criticality, inputs, sources, roles, output, review and permitted follow-up. Identify open points and actions. Define participants, data and boundaries for the pilot. Evaluate results against criteria set beforehand. Time saved can measure benefit, alongside measures of substantive quality.
For routine use, assign ownership, training, error handling and change assessment. Fit Copilot into existing operational processes so staff can act on the controls. The Annex 22 article explains the draft status in detail. Here the decision concerns the actual Microsoft service, the uses your controls can support and the limits that remain.
Assess the limits of Copilot through one defined task
Start with a bounded task, such as finding an internal SOP, and consider the consequences of a wrong answer. With the process owner and IT, we check source versions, actual access permissions and how a knowledgeable person can verify the result. A suitable, limited use may be tested in a pilot. If critical consequences or weak source controls cannot be managed adequately, the task needs a different solution. We record the basis for the decision and the limits of use. Human confirmation alone does not establish suitability.
FAQ on Copilot in GxP processes
Is Microsoft 365 Copilot already validated for GxP use?+
Validation evidence relates to a specific task, its data, sources, users and controls. A general product statement cannot establish suitability for your process. Assess relevant vendor evidence and document what your own assessment covers, including its limits.
Does human review make every Copilot use non-critical?+
No. The actual effect on decisions and records remains decisive. The reviewer must be able to detect errors and perform the review in practice. A confirmation without suitable references, competence and criteria cannot establish control. Assess critical uses separately.
Can Copilot surface information that was shared too broadly?+
The enterprise service described here relies on existing permissions. If they are too broad, Copilot can make the affected information easier to find. Review groups, libraries and guest access before use. Your organisation remains responsible for its access model.
Are enterprise data excluded from model training?+
Microsoft makes a specific commitment for the enterprise service described here. Verify the product, contract and enabled features. The same commitment does not automatically apply to consumer products, third-party agents or every extension. Also assess storage and other processing.
The 2025 consultation draft is not in force. It excludes generative AI and LLMs from its proposed model scope and does not envisage their use in critical GMP applications. For non-critical use, it proposes that suitably qualified and trained people ensure outputs are suitable for their intended purpose. This grants no approval for Copilot. Assess applicable requirements against the actual process independently of the draft.
Set criteria for source accuracy, completeness, error detection, access permissions and permitted use. Measure the actual effort, including review. Fast responses and high satisfaction alone cannot establish suitability. Use the findings and observed limits to decide whether to proceed.
Sources and review date
Sources were checked on 14 October 2026. The regulatory interpretation and product capabilities are supported separately. Adapt the examples, matrices and templates to the intended use. On 18 October 2026, the scope of the 2025 Annex 22 consultation draft concerning generative AI and LLMs was checked against its EudraLex status. The draft was not in force.
Microsoft, Data, Privacy, and Security for Microsoft CopilotMicrosoft documentation also uses the name Microsoft Copilot for Microsoft 365 Copilot. Distinguish the enterprise product from consumer products and extensions. The access model and vendor privacy commitments were checked on 14 October 2026.
European Commission, EudraLex Volume 4 official document indexOn 14 October 2026, EudraLex listed the January 2011 Annex 11 and did not list Annex 22 as an annex in force. Separate EU implementing regulations for veterinary medicinal products have applied since 16 July 2026.
Daniel Herrmann Consulting combines assessment of the process with work on the actual system. Tell us the intended use, the evidence you have and the decision you need to make.
Bring your AI system into GxP use with traceable evidence and keep it under control in operation. Once the system and intended GxP use are defined, we validate according to risk, addressing data, supplier, tests, release and change control.
VAT identification number pursuant to § 27a German VAT Act (UStG): DE328451232
Consumer dispute resolution (VSBG)
In accordance with § 36 VSBG: we are neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board.
Liability for content
We are responsible for our own content on these pages under the general laws. Under Articles 4 to 8 of Regulation (EU) 2022/2065 (Digital Services Act, DSA), as a service provider we are not obliged to monitor transmitted or stored third-party information or to investigate circumstances that indicate unlawful activity.
Note: The §§ 7–10 of the previous Telemedia Act (TMG) on the liability for digital services have not been transferred to the German Digital Services Act (DDG). Liability for digital services is now primarily regulated by Regulation (EU) 2022/2065 (DSA), in particular Articles 4–8 — referenced above. The §§ 7–10 DDG cover other subjects (limited responsibility under DSA Articles 4–8 + Wi-Fi access, blocking claims under copyright law, lists of audiovisual-media-service and video-sharing-platform providers, and information-request rights of the competent authorities under state law).
Copyright
The content and works on these pages created by the site operator are subject to German copyright law. Reproduction, processing, distribution and any kind of exploitation outside the limits of copyright require the written consent of the respective author.
Privacy Policy
1. At a glance
The following information gives a simple overview of what happens to your personal data when you visit this website. Personal data is any data that can be used to identify you personally.
2. Controller
The controller responsible for data processing on this website pursuant to Art. 4 (7) GDPR is:
Daniel Herrmann Consulting Daniel Herrmann (sole proprietor) Enzweilerweg 3a · 66709 Weiskirchen · Germany Phone: +49 170 7878065 Email: info@daniel-herrmann.io
A data protection officer has not been appointed; the controller is your point of contact for all data protection matters.
3. Server logs
Our website is hosted by Kinsta Inc., 8605 Santa Monica Blvd #92581, West Hollywood, CA 90069, USA. When you visit, Kinsta processes your IP address, the time of the request, the page requested, the referring page and browser information. This helps keep the site secure and diagnose faults (Article 6(1)(f) GDPR). The site is hosted in Frankfurt, Germany. Kinsta keeps server logs for up to four days. It also analyses access log data, including IP addresses, in the US to operate and secure its services. It keeps this analytics data for up to 30 days. Kinsta’s data processing addendum includes the EU standard contractual clauses.
3a. Cookie-free page request counts
We count page requests using a small image served by this website. Each request increments a counter for the UTC day and page path. The counter stores no IP addresses, user agents, referrers, query parameters or visitor identifiers, sets no cookies and reads no browser storage. Known automated requests and prefetches are filtered using request headers without storing those headers. Counts include repeated loads and requests without statistics consent; they cannot identify individual visitors or measure their time on the site. Aggregates are removed after 90 days. Technical hosting logs are separate, as described above. The purpose is to understand the use of our public pages; the legal basis for the technical request processing is our legitimate interest under Art. 6(1)(f) GDPR in a data-minimising usage overview.
4. Contact
If you contact us via form, email or phone, we store the information you provide (name, email, telephone number, company, message content) to process the enquiry and for follow-up questions. Legal basis: Art. 6 (1) (b) GDPR (pre-contractual measures) and Art. 6 (1) (f) GDPR (legitimate interest in answering enquiries). Retention: deletion as soon as the enquiry has been finally processed, at the latest after 12 months, unless statutory retention obligations apply.
Our English project enquiry form emails your details to our team. It asks about your role, company size, the support you need and your timeframe. We do not send these enquiries to Calendly.
5. Practical guides and worksheets
For our other practical guides (e.g. Strategy Guide, Compliance-Gap Analysis, Execution Playbook), we ask for your name and email address. Your company is optional. The data is stored solely to provide the requested material and for documentation of consent. Legal basis: Art. 6 (1) (a) GDPR (consent). Retention: until your withdrawal, at most 24 months. The newsletter subscription is offered as a separate, opt-in checkbox on the lead-magnet form (no coupling — you can request the material without subscribing). No marketing emails are sent without separate consent.
For the GAMP 5 practice package, name, company, business email address and telephone number are required. We use these details to process your business enquiry, make the short telephone call you requested and personally send the documents afterwards. There is no automatic download in this process. The information under Contact applies to handling this enquiry. A newsletter subscription remains separate and optional.
The same manual enquiry process applies to the German worksheet packages on Annex 22, CSV project planning, CSA/CSV, Annex 11 and ALCOA+. Name, company, business email and telephone number are required for the requested short call and personal delivery of the worksheets. The information under Contact applies. Submitting the form does not verify your affiliation with a company or your telephone number, does not provide an automatic PDF download and does not subscribe you to a newsletter. This worksheet notice was added on 26 October 2026.
5a. Newsletter (Double-Opt-In)
If you sign up for our newsletter, we use the double-opt-in procedure: after entering your email and name you receive a confirmation email with a verification link. Only after you click the link do we activate the subscription and document your consent. Data: email, name, consent timestamp, confirmation IP. Purpose: sending our monthly newsletter with practice insights, plus documentation of the consent process (Art. 7 (1) GDPR). Legal basis: Art. 6 (1) (a) GDPR (consent), § 7 (2) Nr. 2 UWG. Retention: for as long as your subscription is active; consent logs retained for 3 years after the end of the subscription as evidence in the event of complaints. Withdrawal: every newsletter contains a one-click unsubscribe link in the footer. Alternatively a short email to info@daniel-herrmann.io is sufficient. Processor: the newsletter is sent via our hosting provider's SMTP infrastructure; we currently do not use a third-party email-marketing tool. As soon as we transition to a dedicated newsletter-tool (e.g. Brevo), we will update this section and conclude an additional data-processing agreement.
5c. Link-click tracking in our emails
To understand which content in our lead-magnet emails and newsletter issues is actually useful, we route outbound links through an internal redirect endpoint (`/t/`). Each link in each send gets an aggregate click counter — but we do NOT store an identifier of the individual recipient, NO IP address and NO user agent. The data we keep is comparable to anonymous server logs (e.g.: ‘link X in send Y was clicked 42 times in total’). It does not allow us to infer who clicked. Therefore no separate consent or cookie banner is required (recital 26 GDPR — anonymous data, no personal-data processing per Art. 4 (1) GDPR). Legal basis for the redirect itself: Art. 6 (1) (f) GDPR (legitimate interest in measuring content effectiveness for our own communications). Legal pages (Impressum, Datenschutz) and the unsubscribe link are NEVER routed through the redirect, so the click behaviour on legally relevant links is never measured.
5b. Retention overview & justifications
A consolidated view of all retention periods with the rationale behind each one — the principle: minimal storage, clear purpose, documented basis.
Data categoryRetentionJustification
Server logsUp to 4 days for server logs and up to 30 days for analytics dataSite operation, security and troubleshooting. See section 3.
Contact enquiries12 monthsB2B sales cycle in pharma typically runs 6–9 months. 12 months covers follow-ups without unnecessary stockpiling. Statutory retention (e.g. § 257 HGB) only applies once a contract is concluded.
Lead magnetsup to 24 monthsUntil withdrawal of consent; 24-month cap covers documentation of consent (Art. 7 GDPR) and re-engagement cycle. Withdrawal at any time, deletion within 7 days of request.
Newsletter subscriptionactive subscription + 3 yrs consent logEmail + name only as long as the subscription is active. Consent log (timestamp + IP) retained 3 years to cover statutory limitation period (§ 195 BGB) for complaints under § 7 UWG.
Cookies (incl. analytics)30 min – 14 monthsPer-tool detailed in 6.9. GA4 capped at 14 months (the GA4 minimum, shorter possible only via property reset); all other tools below or equal to industry standard.
Cookiebot consent12 monthsMaximum window the EDPB considers reasonable for repeat-consent requests. After 12 months a fresh banner appears.
6. Cookies, analytics & tracking
This website uses analytics and tracking tools that go beyond pure reach measurement and create usage profiles. Personal data may be processed (in particular IP address, device and browser information, behaviour data) and transferred to third countries (including the USA). Legal basis is your consent pursuant to § 25 (1) TDDDG and Art. 6 (1) (a) GDPR. The consent is granted on first visit via our cookie banner and can be withdrawn at any time with effect for the future — see section 6.10 below. Withdrawal is as simple as granting consent (Art. 7 (3) GDPR); the lawfulness of processing carried out on the basis of consent prior to withdrawal remains unaffected.
6.0 Consent management (Cookiebot)
Provider: Cybot A/S, Havnegade 39, 1058 Copenhagen, Denmark (a Usercentrics company) — EU-based. Purpose: Cookiebot is the consent management platform (CMP) we use to document your consent in line with § 25 TDDDG and Art. 7 GDPR and to block analytics / tracking tools until you opt in. Data: Cookiebot stores a ‘CookieConsent’ cookie containing your consent state (categories, timestamp, anonymous identifier) and a server-side consent log. Retention: up to 12 months from the moment consent is given; renewed on each new visit after expiry. Legal basis: the processing of consent itself rests on Art. 6 (1) (c) GDPR (legal obligation to document consent). Third-country transfer: primary processing in the EU; sub-processors may include service providers outside the EEA under EU Standard Contractual Clauses. Data processing agreement: concluded with Cybot A/S. More info:Cookiebot Privacy Policy.
6.1 Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (parent company: Google LLC, USA). Purpose: Tracking tool that goes beyond pure reach measurement. Google uses the collected data for the operation of GA4 and partly for its own purposes (no commissioned processing in the narrow sense for these purposes). Data: pseudonymous identifiers (client ID), IP address (shortened on EU server, see below), page views, dwell time, scroll depth, click events, device and browser information, approximate location (country / region from IP). Retention: up to 14 months for event-level data, then automatic deletion. IP shortening: The IP address is shortened on an EU server before being forwarded to the USA (‘_anonymizeIp’ equivalent in GA4 is active by default). Third-country transfer: data is processed on servers in the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework (Adequacy Decision of 10 July 2023). Note that the supervisory authorities point out that the legal certainty gained may only be temporary; previous adequacy regimes (Safe Harbor, Privacy Shield) were invalidated by the CJEU. Data processing agreement: concluded with Google Ireland Ltd. More info:Google Privacy Policy, Browser opt-out.
6.2 Microsoft Clarity
Provider: Microsoft Ireland Operations Ltd., One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland (parent: Microsoft Corporation, USA). Purpose: Session recordings and heatmaps to improve usability. Note: session recordings are a particularly intensive form of processing — they can capture sensitive content even though input fields are masked by default. We have configured the strictest masking level (‘Strict’) for all form fields. Data: mouse movements, clicks, scroll behaviour, page views, device and browser information, shortened IP address, country. Retention: up to 12 months from the last recorded session. Third-country transfer: Microsoft is a US group; data may be processed on servers in the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework. The reservations noted above for GA4 apply analogously. Data processing agreement: Microsoft Online Services DPA concluded. More info:Microsoft Privacy Statement.
6.3 Leadfeeder (Dealfront)
Provider: Dealfront Germany GmbH (Leadfeeder), Markgrafenstraße 36, 10117 Berlin, Germany — EU-based provider. Purpose: B2B identification of visiting companies based on commercially licensed IP-address databases (e.g. RIPE, ARIN, public corporate IP ranges). We use this to inform our sales outreach. The aim is identification of the company, not of an individual user. Important note from a data protection perspective: IP addresses can constitute personal data, particularly when combined with other data. We therefore treat Leadfeeder processing as relevant under GDPR. Data: IP address, page views, timestamp, dwell time, referrer. Data sources: Dealfront enriches IP data with publicly available company information and licensed B2B databases. Retention: up to 12 months on visit level; aggregated reports may be retained longer. Third-country transfer: Dealfront operates primarily on EU infrastructure; sub-processors may include US service providers under EU Standard Contractual Clauses. Data processing agreement: concluded with Dealfront Germany GmbH. More info:Dealfront Privacy Policy.
6.4 Google Ads
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (parent: Google LLC, USA). Purpose: We use Google Ads conversion tracking and (where activated) remarketing to measure the success of advertising campaigns and to address visitors with relevant ads. Data: pseudonymous click ID (gclid), conversion event, conversion timestamp, device and browser information. Cookies used include `_gcl_au` (conversion linker) and `test_cookie` (doubleclick.net technical test cookie). Retention: `_gcl_au` up to 90 days, conversion logs in the Google Ads account according to Google retention settings. Third-country transfer: data is processed on Google servers including the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Data processing agreement: concluded with Google Ireland Ltd. More info:Google Privacy Policy, Ad personalisation settings.
6.5 LinkedIn Insight Tag
Provider: LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place, Dublin 2, Ireland (parent: LinkedIn Corporation, USA). Purpose: The LinkedIn Insight Tag enables campaign measurement, audience analytics and (where activated) retargeting for LinkedIn ad campaigns. Data: IP address (truncated), timestamp, page URL, device characteristics, LinkedIn member ID where the visitor has been logged in to LinkedIn. Cookies used include `bcookie`, `lidc`, `bscookie`. Retention: up to 6 months for direct identifiers; aggregated campaign reports may be retained longer. Third-country transfer: data is processed on LinkedIn servers including the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Data processing agreement: concluded with LinkedIn Ireland Unlimited Company. More info:LinkedIn Privacy Policy, LinkedIn opt-out.
6.5a Meta Pixel (Facebook Pixel)
Provider: Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, D04 X2K5, Ireland (parent: Meta Platforms, Inc., 1601 Willow Road, Menlo Park, CA 94025, USA). Purpose: The Meta Pixel (also ‘Facebook Pixel’) enables reach measurement, conversion tracking and (where activated) retargeting for advertising campaigns on Facebook and Instagram. It lets us measure the effectiveness of our ads and show relevant advertising to visitors. Data: pseudonymous identifiers, IP address, device and browser information, referrer URL, triggered events (e.g. page view). Cookies used include `_fbp` (first-party cookie used to recognise the browser) and `_fbc` (click identifier derived from the `fbclid` URL parameter). If the visitor was logged in to Facebook / Instagram at the time of the visit, Meta can attribute the visit to the respective account. Joint controllership: for the collection and transmission of the data to Meta there is joint controllership within the meaning of Art. 26 GDPR between us and Meta; we have concluded Meta’s controller addendum for this. Meta is solely responsible for any subsequent processing of the data for its own purposes. Retention: `_fbp` up to 90 days; on the event level according to the retention settings in the Meta Events Manager. Third-country transfer: data is processed on Meta servers including the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework (Adequacy Decision of 10 July 2023). The reservations noted above for GA4 apply analogously. Legal basis: your consent pursuant to § 25 (1) TDDDG and Art. 6 (1) (a) GDPR. The pixel is only loaded after you have given consent via our Cookiebot banner. More info:Meta Privacy Policy, Meta ad settings.
6.6 Google Tag Manager
Provider: Google Ireland Limited (see 6.1). Purpose: Google Tag Manager (GTM) is a tag-management system that loads other tracking tags (e.g. Google Analytics, Google Ads, LinkedIn Insight Tag) on this website. GTM itself does not set any cookies and does not collect personal data per se; it only orchestrates the tags loaded after consent. Data: technical request data (IP address, timestamp, user agent) is briefly seen by Google’s GTM-loader server. No persistent identifier is set by GTM itself. Third-country transfer: the GTM loader is hosted on Google infrastructure including the USA. Safeguards as in 6.1. Note: we have configured GTM so that no measurement tag fires before you have given consent via our Cookiebot banner. More info:Google Privacy Policy.
6.7 Cloudflare (CDN & bot management)
Provider: Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA, with EU representative Cloudflare Germany GmbH, Rosental 7, c/o Mindspace, 80331 Munich. Purpose: Cloudflare is used by our hosting provider as a Content Delivery Network (CDN) and security layer. The ‘__cf_bm’ cookie is set by Cloudflare’s bot-management to distinguish humans from automated traffic and to mitigate DDoS attacks and content scraping in real time. Why we consider this technically necessary: Without bot-mitigation our website would be vulnerable to credential-stuffing, scraping and DDoS attacks that compromise availability, integrity and the security of the personal data we process (e.g. lead-magnet form submissions, newsletter signups). Bot-mitigation is therefore a technical security measure within the meaning of Art. 32 GDPR (security of processing). Cloudflare itself classifies ‘__cf_bm’ as ‘strictly necessary’ (Cloudflare cookie documentation). Replacing Cloudflare bot-management would weaken the security of personal data on this site. Data: IP address, request headers, technical fingerprint of the request. No persistent identifier across sites. Retention: ‘__cf_bm’ cookie expires after at most 30 minutes of inactivity. Aggregated security logs at Cloudflare are retained briefly under Cloudflare’s standard retention. Legal basis: § 25 (2) Nr. 2 TDDDG (technically required to operate the requested service) and Art. 6 (1) (f) GDPR (overriding legitimate interest in a secure, available website). Third-country transfer: Cloudflare is a US group; data may be processed on servers in the USA. Safeguards: EU Standard Contractual Clauses and the EU-US Data Privacy Framework (Adequacy Decision of 10 July 2023). The EU General Court dismissed the challenge to the adequacy decision on 3 September 2025 (T-553/23). An appeal was filed (C-703/25 P). Data processing agreement: concluded as part of the hosting contract. More info:Cloudflare Privacy Policy.
6.8 Google Search Console
Provider: Google Ireland Limited (see 6.1). Purpose: Google Search Console (GSC) lets us monitor how the site performs in Google’s search results — indexing status, search queries that lead to the site, click-through rates, technical crawl errors. Cookies / tracking on visitors: GSC itself sets no cookies on visitors of this website and runs no client-side script. The site ownership is verified by a static HTML meta tag and / or a DNS TXT record. Data: aggregated search analytics from Google’s side (search queries, impressions, clicks); these are not directly linked to individual visitors. The data is made available to us only in aggregated form. Legal basis: Art. 6 (1) (f) GDPR — legitimate interest in monitoring the site’s search visibility. Third-country transfer: the aggregated reporting is generated on Google infrastructure including the USA. Safeguards as in 6.1. More info:Google Privacy Policy.
6.9 Cookie storage durations
Session cookies are deleted when the browser is closed. Permanent cookies have the following maximum lifetimes: Google Analytics 4 — up to 14 months (data retention shortened to 14 months in GA4 settings); Microsoft Clarity — up to 12 months; Google Ads (`_gcl_au`) — up to 90 days; Meta Pixel (`_fbp`) — up to 90 days; LinkedIn (`bcookie`) — up to 6 months; Cloudflare (`__cf_bm`) — at most 30 minutes of inactivity; Leadfeeder — typically session-based, not stored on the device; CookieConsent (Cookiebot) — up to 12 months from the moment consent is given.
6.10 Withdrawal of consent
You can withdraw your consent at any time with effect for the future — withdrawal is as easy as granting consent:
1. Open cookie settings: click the ‘Cookie settings’ link in the footer to re-open the banner and adjust your choice (this controls all of GA4, Clarity, Google Ads, LinkedIn, Meta Pixel and Leadfeeder). 2. By email: send a short message to info@daniel-herrmann.io — we will block the relevant tools for you. 3. Per tool: for Google Analytics the official browser opt-out is available; for Google Ads under Ad personalisation settings; for LinkedIn under LinkedIn opt-out; for the Meta Pixel under Meta ad settings. Microsoft Clarity and Leadfeeder are controlled exclusively via our cookie banner.
The lawfulness of processing carried out on the basis of consent prior to withdrawal remains unaffected (Art. 7 (3) GDPR).
6.11 Appointment booking with Calendly
We use Calendly LLC, 115 E Main St, Ste A1B, Buford, GA 30518, USA, for appointments on our German booking and compliance check pages. The embedded calendar loads when you explicitly allow preferences, statistics and marketing in our cookie banner. Your choice also applies when you return. You can change it at any time in Cookie settings. You can also arrange an appointment by email or follow the direct link to Calendly, where its own cookie settings apply.
When the calendar loads, Calendly and its service providers receive technical data such as your IP address and browser information. They may use cookies and other browser storage to run the calendar, protect it against abuse, analyse usage and support marketing. Your consent covers optional storage and the associated processing under section 25(1) TDDDG and Article 6(1)(a) GDPR. Under Calendly’s terms, we and Calendly each act as independent controllers for data collected through the embedded cookie technologies.
When you book, we process your name, email address, company, answers to the booking questions and chosen time. We use these details to prepare the meeting and send your Microsoft Teams invitation. The legal basis is Article 6(1)(b) GDPR for steps you request before entering into a contract, or Article 6(1)(f) GDPR for our legitimate interest in responding to a request on behalf of your company. We keep booking details for as long as needed to organise the meeting and handle follow-up correspondence. Statutory retention periods may also apply.
Calendly’s data processing addendum forms part of its customer terms. It covers the booking data Calendly processes on our behalf in the US. For EU-US transfers it provides for the EU-US Data Privacy Framework, with EU standard contractual clauses if that framework ceases to apply. See Calendly’s privacy notice for more information.
7. Web fonts
The fonts used on this website are served locally. Loading these fonts does not connect your browser to Google or any other font provider.
8. Technical and organisational measures (TOM)
To protect your data we implement appropriate technical and organisational measures pursuant to Art. 32 GDPR — among them: TLS encryption (HTTPS) for the entire site, encrypted database connections, server hosting in the EU (Kinsta / GCP Frankfurt), restricted admin access via individual accounts with strong passwords and 2FA, regular automatic backups, role-based access controls, a documented record of processing activities pursuant to Art. 30 GDPR, and data minimisation at the application level. We continuously review and update these measures.
9. Your rights
Under the GDPR you have the following rights:
Right of access (Art. 15 GDPR) — information about which of your personal data we process.
Right to rectification (Art. 16 GDPR) — correction of inaccurate data.
Right to erasure (Art. 17 GDPR) — deletion of your data where the legal conditions are met.
Right to restriction of processing (Art. 18 GDPR).
Right to data portability (Art. 20 GDPR) — receipt of your data in a structured, common, machine-readable format.
Right to object (Art. 21 GDPR) — to processing based on legitimate interest, including for direct marketing. See highlighted box below.
Right to withdraw consent (Art. 7 (3) GDPR) — at any time with effect for the future, see section 6.10.
Right to lodge a complaint (Art. 77 GDPR) — with a supervisory authority, in particular in the EU member state of your residence, your workplace or the location of the alleged infringement. Competent supervisory authority for our office location: Independent Data Protection Centre Saarland (Unabhängiges Datenschutzzentrum Saarland), Fritz-Dobisch-Straße 12, 66111 Saarbrücken.
Requests regarding these rights are to be directed to: info@daniel-herrmann.io. We will respond within the statutory period (usually one month).
10. Currency of this Privacy Policy
Last updated: 22 November 2026. We reserve the right to adapt this policy so that it always meets current legal requirements. The current version is always retrievable from this website.
Free material by email
Your material is on the way.
Enter your name and email, we send the material directly to your inbox, with a short personal note from Daniel.
Thanks, check your inbox.
We just sent the material to your email. If it doesn't arrive within a few minutes, please check your spam folder.
Once a month · CSV practice
CSV insights from real Pharma projects.
What you get next: the GAMP 5 2nd Edition impact, what the FDA CSA Final Guidance means for your validation strategy, and how the 8-week CSV sprint works. Unsubscribe anytime in one click.
Almost done.
Confirm your email via the link we just sent to your inbox. After confirmation we'll send the latest newsletter issue right away.
We use your data exclusively for the newsletter. No sharing with third parties. Privacy policy.