Laboratory software validation for LIMS, CDS and ELN From Measurement Value to Report.
For laboratory information management systems, chromatography data systems and electronic laboratory notebooks. We trace the data flow with your team, plan testing and give QA the evidence needed for its release decision.
The scope follows the data path from the measurement value to the report.
Calculations, modifications, and audit trails are reviewed on a risk-based approach.
You decide on release in accordance with your quality process.
Daniel explains how the team can support an implementation with a fixed go-live date. You agree the scope, roles, milestones and release decisions. The team carries out the agreed validation work and reports progress through to handover.
Integrated Validation Execution. Project Leadership and Implementation End-to-End.
LIMS, CDS, ELN, and device software
Annex 11 and Part 11 depending on application
Fixed prices are possible once the scope is defined.
Contact us using the project enquiry form
At a glance
What does laboratory software validation involve?
Laboratory software validation documents whether a system is fit for its intended use in a regulated laboratory. Trace a result from the sample through measurement, calculation and assessment to the report. Include handovers between the instrument, processing software, LIMS and ERP. Use this path to define requirements, risk-based tests and the evidence needed for release.
The evaluation begins with the laboratory request and ends with the used, traceable result.
Software validation and method validation are distinct activities with common interfaces.
Device connectivity, calculation, and reporting require a common data reference.
Records and their change history must remain accessible and readable beyond the retention period.
Define laboratory procedures, data flows, and interfaces with laboratory, IT, and QA departments.
Clarify requirements and risks, assess supplier evidence
Develop a validation plan and implement the agreed test strategy, including calculations and interfaces
Prepare documentation in accordance with your SOPs and templates, transfer it, and train your responsible personnel.
Your team’s responsibilities
Labor knowledge, methods, and specifications
Project decisions
The formal release pursuant to your quality process
Labor data pathway
From Measurement Value to Report: What Should Be Included in the Scope?
In the laboratory, several systems contribute to a single result. Validation follows the data pathway, not the boundary of a single product.
Select an actually intended workflow, for example, the inspection of incoming material against a defined specification. Follow the sample collection, method assignment, entry or transfer of raw data, calculation, evaluation, and reporting. Also identify activities outside the LIMS.
For each transfer, it should be clearly defined which record is generated, which system is responsible for it, and who is authorized to use it. A device evaluation may originate in a different application and can only transmit a derived result. In such cases, both systems and their transfer mechanism must be considered.
The following overview serves as an internal reference guide. The specific stations within your laboratory that are relevant are determined by the established process.
Stations of a laboratory result and questions for defining boundaries
Stage
Typical System
Question to define the scope
Sample creation and work order
LIMS
How is a sample clearly assigned?
Measurement and Raw Data
Device software, Chromatography data system
Where is the original record created and who is authorized to modify it?
Analysis and Calculation
Chromatography data system, LIMS, spreadsheet software
Which formula, rounding rule, and method version applies?
Data transfer
Interface between device, analysis software, and LIMS
How are unit and sample reference maintained?
Evaluation and Release
LIMS
Who reviews and determines the acceptable result?
Report and Distribution
LIMS, ERP
Which version and status are issued?
Retention
Primary system or archive
Do data and correlations over the storage time remain legible?
The methodology is vendor-neutral; the inspection questions are not. Separate guidelines with product-specific test cases are available for the following systems.
In the laboratory, the software determines whether a batch release is approved based on the test result. Similarly rigorous evaluations are conducted for calculations, modifications, and access.
A properly functioning application can lead to an inappropriate decision if its set limits are incorrectly configured. Therefore, in addition to software functionalities, assess relevant method settings, units, rounding rules, specifications, and release workflows.
An appropriate test links requirements, input data, expected behavior, and actual results. The following overview serves as a standalone planning aid; the selection and depth of tests depend on the identified risks.
Test samples for LIMS, Chromatography Data System, and electronic laboratory notebook
Subject
What to establish
Possible evidence
Source data and specifications
Which method validation stages, units, and limits have been established and who authorizes them?
Compare the configuration with the approved requirements
Calculations
Which formula and rounding rule applies?
Justified reference results including edge cases
Raw data and reprocessing
How are original data retained when new analysis is performed?
Traceable result versions referenced to the original record
Changes and Audit Trail
Which changes are documented together with the rationale, and who regularly reviews them?
Recording of changes, person, date, and reason; controlled review
Roles and Permissions
Who is authorized to modify methods, correct results, or release batches?
Testing of authorized and unauthorized access using test accounts
Manual entries
Which critical values are manually entered?
Additional accuracy verification by a second person or validated electronic means
Device and System Interfaces
How are assignments, errors, and repeated transfers handled?
Comparison of defined source and target values, including in error cases
Electronic signature
Which dataset is signed and how is the reference maintained?
Review of authorization, data set reference, and date and time of signature
Archiving
Can data with its context be read again later?
Authenticated access to archived data, including after system modifications
Spreadsheets, device software, and on-premise solutions.
Not every laboratory system bears the name LIMS. Even small applications can perform calculations or generate results.
An Excel template that calculates a test result, or that interfaces with a weighing software or a laboratory instrument controller, can have the same impact on a quality decision as a large-scale system. The key factor is usage: is a record generated, is a calculation performed, or is a result transmitted?
Run these applications in the system inventory and evaluate them using the same criteria. The effort required is based on the risk of the process and on what the application actually does.
So our validation of your laboratory software works.
You know in advance the scope of work to be undertaken and the level of involvement required. Each week, you see what has been completed, where risks exist, and which decisions are pending.
IVE
Integrated Validation Execution
Project management and delivery from one team.
Project management01
Commission the project and agree the scope
You commission the project and we begin with scoping. We document system boundaries, deliverables, assumptions and the work expected from each side.
02
Involve the responsible people
Process owners, system owners, QA, IT and the supplier agree who is responsible for requirements, decisions and approvals.
03
Make progress visible
We maintain one agreed status for each system. The weekly report shows completed work, risks and upcoming decisions.
Delivery04
Qualify and validate
We prepare the agreed documents and evidence under your SOPs and templates, with testing and technical review as defined in the project.
05
Hand over the evidence and knowledge
We hand over the documentation, record open points and their owners and prepare your team to maintain the system in operation.
What should be clarified prior to validation of a laboratory system.
Twelve points at which offer, planning, and target date can be measured. An open response is initially acceptable, provided it remains visible as an assumption and is assigned to a subsequent clarification step.
How we work
Every project follows the same quality framework.
Reliable validation depends on who leads the work, which standards the team follows and how the results are checked before they reach QA. We establish the same controls on every project.
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.
We specialise in the life sciences: pharmaceuticals, biotech, medical devices and laboratories. Our focus on these sectors gives our team the GxP experience it brings to your project.
01
Technical oversight
Provided by Daniel Herrmann on every project.
02
Consistent procedures
The same procedures and templates across projects.
03
Quality checklists
Defined checks on every project.
04
Continuous improvement
We incorporate proven improvements into our procedures and checklists.
GxPsuite, our documentation system
Prepared automatically. Reviewed by experts. Approved by you.
For documentation for your laboratory software validation we use GxPsuite. It brings together your sources and automatically prepares a draft from your templates. Your team can review the draft and see which details still need to be supplied or checked.
Our experts begin their review with a draft prepared from your templates. This reduces manual preparation and helps us produce consistent documentation across projects.
The AI cites the source it used when answering a technical question. Our experts review the draft. Your team checks its relevance to the actual system and makes approval decisions under your quality procedures.
People make the technical decisions.
GxPsuite is a product of traqx GmbH, co-founded and managed by Daniel Herrmann.
What enables the validation of laboratory software.
Common assumption01
“The LIMS has been validated by the manufacturer. This is sufficient for our laboratory.”
Supplier certifications can serve as a important foundation. However, they must align with your actual system status and usage.
What matters in practice
Custom configurations, methods, roles, and interfaces are not automatically validated.
Common assumption02
“The method is validated. Therefore, the software is also.”
Method validation and software validation address different questions. The former demonstrates the technical suitability of the analytical method, while the latter confirms the software's suitability for the intended process flow.
What matters in practice
Both responsibilities are integrated within the project.
Common assumption03
“The audit trail is enabled. The data is therefore secure.”
An active audit trail logs changes. Whether a change was authorized is only determined through review by a responsible person.
What matters in practice
The audit trail is effective when the scope, reason, and authority of the review are clearly defined.
Frequently asked questions
Frequent Questions on the Validation of Laboratory Software.
Significant consideration is given to the use of systems that generate records, perform calculations, evaluate, or transmit results in GMP-controlled activities. This includes LIMS and chromatography data systems, as well as device software, electronic laboratory notebooks, and calculation spreadsheets. The scope and depth of validation are determined by a documented risk assessment.
Which regulatory frameworks apply to laboratory software?+
This depends on the intended use. For computerised systems in GMP activities, EU GMP Annex 11 is applicable; EU GMP Chapter 6 covers quality control, including laboratory records. When electronic records or signatures are used within the FDA's jurisdiction, 21 CFR Part 11 applies. GAMP 5 is a guidance document from ISPE and is not a regulation; we use it as a methodological reference.
Is software validation the same as method validation?+
No. The suitability of the software for the intended workflow and the technical validity of an analytical method are distinct responsibilities. There are interfaces, for example, in calculations and result evaluation. Both responsibility areas and their inputs should be integrated within the project.
Are the manufacturer's validation records sufficient?+
Supplier documentation can serve as a key foundation. However, it must align with your actual system status and usage. Custom configurations, methods, roles, and interfaces are not automatically fully validated. The request should explicitly include an evaluation of existing documentation and justified supplementation.
What does Annex 11 require regarding the Audit Trail?+
Annex 11 requires that, based on a risk assessment, all GMP-relevant changes and deletions be recorded in the system. The reason for any change or deletion must be documented. Audit trails must be available, be capable of being converted into a readily understandable format, and be regularly reviewed.
Must all historical data from a previous system be migrated during a system change?+
Not mandatory. What is essential are a justified data strategy and continued access to retained information, along with the necessary context. An alternate access or archive must genuinely fulfill this purpose. The decision should be made prior to migration and decommissioning.
Yes, if the table is used within a regulated process to calculate results or to record data. The following aspects are then assessed, among others: formulas, input limits and rounding, as well as the distinction between template and completed records. The scope is determined by the risk associated with the process.
What is the cost of validating a laboratory system?+
The effort depends on laboratory procedures, methods and master data, device interface specifications, migration requirements, and existing documentation. Fixed fees are possible once the scope is defined. A daily rate can be agreed for ad hoc consultations.
Sources and review date
Sources behind this guide
Source date: November 12, 2026. The regulatory reference framework covers computerized systems in human medicinal product manufacturing, particularly EU GMP Annex 11 and Chapter 6, as well as 21 CFR Part 11 where applicable. Overviews, test objects, and checklists are standalone work aids and do not constitute official regulatory requirements. Product-specific statements are detailed in the linked system guidelines.
Daniel HerrmannLife sciences compliance specialistSources checked: Updated:
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.
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.