SAP S/4HANA validation · Pharmaceuticals · Biotech · Medical devices
SAP S/4HANA validation for pharmaceutical and medical device companies.
Plan validation around your SAP rollout.
Whether you are implementing a new system, converting an existing one or migrating selected data, we define the GxP-relevant processes with your team, plan risk-based tests and give QA the evidence it needs for release.
We base the amount of testing on the processes in scope and the risks they carry.
Who can help with GxP validation of an SAP S/4HANA migration?
Daniel Herrmann Consulting (DH-Consulting) specialises in computer system validation and IT GxP compliance for pharmaceutical, biotech and medical device companies and laboratories. We establish the status of systems, validate them and help client teams maintain the validated state. For SAP S/4HANA migrations, we plan validation, assess the implementation partner’s evidence and carry out agreed tests with your team. GxP-relevant processes define the scope.
From 2023 to 2026, DH-Consulting advised a top-ten pharmaceutical company on a large SAP S/4HANA implementation covering ERP and Extended Warehouse Management (EWM). The work also included local validation and test management and support for cutover tasks.
60+ systems validated · No critical findings in audits or inspections of those systems after validation
What we do
Define GxP-relevant processes, system boundaries and interfaces with the business, IT and QA
Establish requirements and risks and assess implementation partner evidence
Prepare the test plan and implement the agreed strategy, including data migration
Document the work using your SOPs and templates, hand over the records and train their owners
What your implementation partner does
Explain configuration, custom development, extensions and their dependencies
Provide technical tests and documents
Investigate and resolve technical causes of test deviations
Provide the approved system baseline for testing and operation
Where you retain responsibility
Operational knowledge and requirements
Process decisions during the project
Formal approval under your quality procedures
Contractual responsibilities may vary. We document them before implementation starts.
01 · Who we work with
When do you need SAP S/4HANA validation?
This is a good fit if …
you are implementing S/4HANA in pharmaceuticals, biotech or medical devices, moving from SAP ECC or rolling out an existing template to more sites.
SAP controls GxP-relevant activities such as batch status, inventory holds, release or traceability.
the go-live date is set and the business, IT and QA need to agree what validation requires.
the person who held the validation expertise has left your organisation.
you need validation that fits a small or medium-sized business. We have worked with both smaller companies and global enterprises.
Consider another starting point if …
you primarily need extra staff. Staff augmentation is rarely the right fit for our service.
you only want a set of documents for a deadline. We work towards a validated state your team can maintain.
SAP only supports commercial activities with no effect on product quality, patient safety or data integrity. We document the rationale for excluding those functions and check for dependencies on GxP processes.
02 · Scope
Let your business processes determine the testing.
What is SAP validation?
SAP validation documents whether S/4HANA or SAP ERP is fit for intended use in GxP-regulated processes. It examines workflows in which SAP influences product quality, patient safety or data integrity, such as batch status, inventory holds and traceability.
Typical areas include Quality Management (QM), Materials Management (MM), Production Planning and Process Industries (PP/PP-PI), warehouse management (EWM/WM), Sales and Distribution (SD) and Plant Maintenance (PM). Their relevance depends on how you use them. We document excluded functions and identify their dependencies on relevant processes.
We use GAMP 5 to guide our approach and assess which requirements apply, including EU GMP Annex 11 or 21 CFR Part 11 where relevant. We identify the records, audit trails and electronic signatures that matter to your process.
An S/4HANA migration changes more than the technical release. Migration, configuration and interfaces directly affect quality-relevant data and decisions, so we plan for all three from the outset.
01 · Data migration
A migration needs functional verification that the target system interprets the data correctly. EU GMP Annex 11 addresses preservation of value and meaning. Comparing record counts alone cannot show that units, status mappings or object relationships survived transfer.
Value and meaning · Reconciliation · Legacy records
02 · Configuration, custom code and extensions
An impact assessment identifies which workflows, data models, custom developments and extensions change during conversion. The documented change determines additional tests. Even a small code change can affect a critical status, so assess the functional consequence.
Impact assessment · Configuration · Extensions
03 · Interfaces
S/4HANA may exchange data with warehouse, manufacturing, laboratory and quality systems. Validation follows relevant data across that landscape, including middleware such as SAP PI/PO or Integration Suite on SAP BTP where used. We test successful transfers, rejected and missing messages and duplicate messages.
MES · LIMS · Warehouse management
04 · Implementation approaches
New implementation, system conversion and selective transition: what each means for validation.
SAP distinguishes several transition approaches, commonly called greenfield, brownfield and bluefield. Each raises a different evidence question: which existing processes and records remain suitable, and which configuration or migration decisions need new evidence?
New implementation (greenfield)
Target processes and configurations are designed afresh. Requirements, configuration and migration of the required data take priority. Assess which legacy evidence remains relevant. Which processes are being introduced and which data will move?
System conversion (brownfield)
An existing system baseline is converted to a new environment. Assess changes to processes, data models, custom code, extensions and interfaces. Prior validation needs review against the documented change, which determines additional tests. Which existing processes and extensions have changed?
Selective data transition (bluefield)
Selected configurations and data move while others are intentionally excluded. Document selection, transformation and continued use of historical records. Which configurations and records will move or stay behind?
Rollout of the same template at additional sites
Compare central evidence with local use. A site-specific rule or interface may need its own testing. A global test might establish the main workflow without covering local access roles. Reuse or repeat each test according to its applicability.
The system context determines the approach. For each option, establish how staff will access historical records after go-live.
Daniel Herrmann supported validation across several SAP rollouts. His role included responsibility for individual project workstreams and coordination with other validation managers.
“Daniel brings tremendous value through his expertise and commitment to validation and compliance.”
Jens Fuellbier · Head of GBS Governance, Enablement & Strategy · Boehringer Ingelheim · Translated from German
This recommendation concerns Daniel Herrmann’s own project work.
SAP rollouts · Validation management · Pharmaceuticals
An SAP implementation needs clear responsibilities across the business, IT, QA and the implementation partner. We make that coordination part of the project plan.
Four steps to a validated SAP system in operation.
Our Integrated Validation Execution approach combines project coordination and validation. We align both with your implementation partner’s plan, starting with the overall scope and then the detail.
01 · Scoping and project planning
We define the GxP-relevant processes, data and interfaces with the business, IT and QA during scoping, then develop a detailed project plan. Deliverable: agreed scope and project plan
02 · Specification
We document user and functional requirements and assess risks. Requirements follow the business process and the decisions it supports. Deliverable: specification and risk assessment
03 · Implementation and testing
The implementation partner configures SAP. We plan the tests and perform them with your team. Risk determines test depth, and we assess whether partner tests are suitable evidence. Deliverable: documented tests and assessed deviations
04 · Go-live
Cutover brings S/4HANA into operation. Beforehand, we agree which findings would prevent go-live and the latest point at which a controlled fallback remains feasible. We provide close support during hypercare. Deliverable: a validated system in operation
Depending on scope and preparation, the first two weeks establish scope and an outline plan. We then refine it, allocate resources and responsibilities and hold the kick-off.
At completion
A validated system with testing proportionate to risk and operating procedures that maintain its validated state.
Estimated effort
We estimate effort after scoping. Key drivers are the processes involved, transition approach, custom developments and extensions, interfaces and migration.
The SAP implementation is underway and the go-live date is fixed. The business, IT and QA need to agree what validation requires, or the person who held that knowledge has left.
We start by defining scope with the process owners. Where does SAP support a quality decision, such as batch status or an inventory hold? QA identifies how the project fits existing procedures. IT and the implementation partner explain configuration, extensions, custom developments and interfaces. Management decides priorities and resources.
Reusing earlier screenshots after moving to S/4HANA is insufficient if workflows or risks have changed. Review the relevance of existing documents, then reassess processes, risks and tests.
Process owners know the expected rules and can judge whether SAP processes data correctly. The implementation partner investigates and resolves technical causes of deviations. We assess their impact with QA.
After go-live, your team maintains the validated state. Where useful, training videos and self-study materials remain available to staff and future role holders.
Sustaining validated operation reduces the cost of repeated work.
08 · Quality framework
Every project follows the same quality framework.
Daniel Herrmann provides technical oversight on every project. The team uses consistent procedures, templates and quality checklists so that quality does not depend on one individual.
Once scope is agreed, we assign roles across our team, your organisation and the implementation partner.
Daniel Herrmann has over 17 years’ experience validating computerised systems, from work in medium-sized businesses and at Boehringer Ingelheim to leading validation projects. Our work draws on more than 60 systems validated in pharmaceuticals, biotech, contract manufacturing and laboratories. None of those systems subsequently received a critical finding in an audit or inspection.
Daniel Herrmann has led project management and validation management in global SAP programmes involving teams across multiple countries.
Our clients include Boehringer Ingelheim, Johnson & Johnson and many small and medium-sized companies. We introduce proportionate compliance frameworks smaller businesses can run and defend in an audit.
For documentation, we use GxPsuite. It brings together your sources and prepares drafts from your templates. Our experts review the drafts. Your designated owners confirm applicability to the system and approve them under your quality procedures. GxPsuite is a product of traqx GmbH, co-founded and managed by Daniel Herrmann.
The same procedures and templates across projects.
Quality checklists
Defined checks on every project.
Continuous improvement
We incorporate proven improvements into our procedures and checklists.
09 · Common questions
Questions about SAP S/4HANA validation.
Do we need to revalidate everything when moving to S/4HANA?
The documented change determines what needs retesting. For a brownfield conversion, assess the impact on processes, data models, custom code, extensions and connected applications. Existing validation evidence must be reassessed against those changes. For a greenfield implementation, the focus is requirements, configuration and migration. Existing documents can help, but processes, risks and tests need to be reviewed.
After scoping, we estimate effort and duration and align both with the implementation partner’s schedule. The main drivers are in-scope processes, implementation approach, custom code and extensions, interfaces and migration. We then plan testing, approvals and milestones through go-live.
How much does SAP validation cost?
We estimate effort after scoping. The processes in scope have more influence than the number of modules. We can offer a fixed price for a defined scope or a day rate for targeted advice. Our cost guide describes the main effort drivers. Send us your project details for advice specific to your situation.
What does the systems integrator do, and what do you handle?
The systems integrator configures SAP and understands the technical setup. Your process owners explain its business implications. We plan validation, assess whether the partner’s tests and records are suitable evidence and perform agreed tests with your team. Your organisation retains approval. We record the division of responsibilities in the project plan.
How soon can you join our SAP project, and what can we expect after two weeks?
Include your SAP rollout date in your enquiry so we can confirm when we can start. Ideally, scoping begins before configuration and migration. If the project is underway, we assess its actual state and existing records. Depending on scope and preparation, the first two weeks establish scope and an outline plan.
How much staff time should we plan, and which records do you need?
Process owners, IT and QA are needed at the outset to establish scope. We then schedule your contribution explicitly. Process owners supply expected business rules, reference data and decisions. QA aligns validation with your procedures. IT explains the technical setup. Information on edition, deployment, transition approach, affected processes, existing validation records and your implementation partner’s proposal helps us get started.
Do you validate SAP cloud deployments, including RISE and BTP?
Yes. Our scope includes RISE with SAP and SAP Business Technology Platform (BTP). Validation covers the intended business process, configuration, extensions and integration. We establish which services SAP delivers under your edition and contract and what evidence is available. We assess release impact and affected functions. Your organisation decides whether the system is suitable for regulated use.
EU GMP Annex 11 says validation should check that transfer preserves the value and meaning of the data. Record counts alone cannot establish that. We connect the source, transformation rule, target and verification method and plan separately for access to historical data.
We test permitted and prohibited activities for each role. Effective access to objects, organisational units and critical status changes matters more than which apps are visible. Tests cover assigned roles, prohibited actions, alternative access routes and role combinations. A successful authorised transaction alone does not establish that access is restricted correctly.
How do you handle transports, releases and changes after go-live?
Change assessment and periodic evaluation help maintain the validated state. Each transport is linked to an approved change. Check contents, dependencies, import order and target system. The effect of the change determines testing. Apply the same approach to role changes and new releases. We agree procedures before go-live so your team can operate them independently.
What will we have after go-live, and what can our team do independently?
A validated SAP system in operation, with specifications, a risk assessment, documented tests, assessed deviations and a recorded release decision. Your team has operating procedures to assess transports, changes to roles and releases and to evaluate the system periodically. Where appropriate, training videos and self-study materials remain available to current and future role holders.
Sources
Sources and review dates
Author: Daniel Herrmann, founder and managing director of DH-Consulting. · German source text dated
The regulatory references concern computerised systems used in GMP activities under EU GMP Annex 11 and, where applicable, 21 CFR Part 11 and medical device manufacturers’ quality management systems. Our checklists and workflows are practical tools. SAP describes the transition approaches. The validation implications are our interpretation. Technical details depend on the edition and documentation version.
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.