Every poultry processor operating in the European Union eventually has the same conversation with growers, works councils, and legal advisers: what data leaves the farm, on what basis, and what control does the grower keep. Those questions do not have a software answer alone, but software either supports good answers or undermines them. Poultry Log's processor network is built around consent, data minimization, and revocability, which is what the conversation needs underneath it.
Consent as the Legal and Technical Base
The processor link in Poultry Log is created only when the grower initiates it: the grower enters the processor's code, sees the processor's name and region, and reads a versioned consent disclosure before anything is shared. The consent text version and timestamp are stored with the link itself, so the question "what exactly did this grower agree to" has a document answer rather than a recollection. A farm can hold one active processor link at a time, and replacing a link requires acknowledging the current processor first.
Data Minimization in Practice
The disclosure names an allowlist rather than promising broad access: compliance checklists and completion history; flock mortality, culls, water and feed use, and weights versus targets by house and flock; farm name, house count, capacity, and region. The exclusion list is equally explicit: login credentials, billing details, precise GPS location, farm street addresses, and other processors' checklists. The processor console is read-only against grower records, apart from the processor's own thresholds and alert acknowledgements. This is data minimization built into the access model rather than promised in a policy document.
Revocation and Retained History
The grower can remove the link at any time in Settings, which stops new data sharing immediately. Records already shared while the link was active remain visible to the processor for audit purposes, and previously saved shared snapshots are retained the same way. That boundary is deliberate: future sharing stops on the grower's word, while the evidence already produced stays where an auditor can find it.
What This Framework Is Not
Poultry Log's consent model is a technical and contractual foundation, not a legal certification. It does not replace a data protection impact assessment, a named data protection officer, or advice under the GDPR and national implementations. Processors deploying a network in the EU should confirm their lawful basis and documentation obligations with their own counsel; the grower-side checklists are operational records, not certifications of legal compliance under the broiler welfare directive either.
Where Poultry Log Fits
Poultry Log is the grower's system first, which is why the processor link is scoped, disclosed, and revocable rather than open-ended. The full allowlist and exclusion list are covered in the grower data sharing consent guide, the EU welfare record layer in the EU poultry processor software guide, and the audit-trail implications in the compliance audit trails guide. Start free at poultrylog.com.
Frequently Asked Questions
How does Poultry Log handle grower data sharing with EU processors?
Through a consented, revocable link: the grower initiates with a processor code, reads a versioned disclosure, and shares only the listed compliance and performance fields. Credentials, billing, precise location, and street addresses are never shared, and the grower can remove the link at any time.
Does the Poultry Log processor network comply with the GDPR?
Poultry Log provides the consent record, the scoped data allowlist, revocation, and retained history that a GDPR-aligned data sharing arrangement needs. It does not replace the processor's own legal obligations, including lawful basis, documentation, and any data protection impact assessment required for the deployment.
Can an EU processor see a farm's exact location through Poultry Log?
No. Precise GPS location and farm street addresses are on the exclusion list for processor network sharing. The processor sees farm name, house count, capacity, and region, plus the consented compliance and performance records.