Every conversation about poultry processor visibility eventually turns on one question: what exactly does the processor get, and can the grower take it back? Growers are right to ask. A farm's records are its operating history, and handing that history to an integrator without clear boundaries is how growers end up with tools they cannot leave. Poultry Log's processor network answers the question in the open, with a consent disclosure shown before the link is created and a revocation path that works the same day the grower decides to use it.
How the Link Is Created
The grower initiates everything. A processor issues a join code, the grower enters it in Poultry Log Settings, sees the processor's name and region, and reads the consent disclosure before anything is shared. The disclosure is versioned, the confirmation is explicit, and the consent text version is stored with the link. One farm can hold one active processor link at a time. If the farm is already linked to a different processor, replacing that link requires acknowledging the current processor first.
What the Processor Sees
The consented share covers a specific list:
- Compliance checklists and completion history
- Flock mortality, culls, water use, feed use, and weights versus targets, by house and flock
- Farm name, house count, capacity, and region
What the Processor Never Sees
The exclusion list is equally specific. The processor cannot access grower login credentials, billing details, precise GPS location, farm street addresses, or another processor's checklists. Network membership never unlocks unrelated grower pages or APIs. The processor's console is read-only against grower records, apart from the processor's own threshold settings, alert acknowledgements, and findings workflow.
Revocation and the Audit Trail
The grower can remove the link at any time in Settings. Revoking stops new data sharing immediately; it does not erase the history. Records the processor already received while the link was active remain visible to the processor for audit purposes, and previously saved shared snapshots are retained the same way. That asymmetry is deliberate. A compliance record that vanishes the moment a relationship ends is not an audit record, it is a rumor. The grower controls the flow going forward; the evidence already produced stays where an auditor can find it.
Why This Model Works for Both Sides
For the grower, the boundary is legible: share the operational record, keep the credentials, the billing, and the address, and leave when the relationship changes. For the processor, the retained trail means a departed grower's history does not create a hole in the compliance file. For the compliance or legal team reviewing the arrangement, the versioned consent text and the explicit allowlist and exclusion list answer the questions that usually stall a data-sharing approval.
Where Poultry Log Fits
Poultry Log is the grower's system first, which is why the processor network is built as a scoped, revocable view rather than a data extraction. The grower-side controls live in Settings, next to the rest of the farm's account. The broader integrator relationship is covered in the poultry software for contract growers guide, and the records themselves in the poultry farm digital records guide. Start free at poultrylog.com.
Frequently Asked Questions
How do poultry growers share data with processors safely?
Through a consented, scoped link rather than an open data feed. In the Poultry Log processor network, the grower enters a processor code, reads a versioned consent disclosure, and chooses what to share; the processor sees only the listed compliance and performance fields, never credentials, billing, or precise location.
Can a grower disconnect from their poultry processor?
Yes. The grower can remove the processor link at any time in Poultry Log Settings, which stops new data sharing immediately. Records already shared while the link was active remain visible to the processor for audit purposes.
What data can a poultry integrator see from a grower's farm app?
Under a Poultry Log processor link: compliance checklists and completion history, flock mortality, culls, water and feed use, weights versus targets by house and flock, and farm name, house count, capacity, and region. Nothing else is shared without a separate arrangement.