Pickrook deployments handle your facility's operational data and WMS API credentials. Here's how we approach data handling, network segmentation, access controls, and physical safety design.
WMS API credentials are stored encrypted on the Pickrook edge controller hardware, not in cloud systems. Credentials are scoped to read wave releases and write pick confirmations only — no broader WMS administrative access. Credentials are rotatable at any time and revocable from the WMS side.
Order line data (SKU IDs, quantities, bin locations, pick confirmations) is processed on the edge controller and transmitted to your WMS. Pickrook retains pick cycle logs for operational analytics with a 90-day retention window. No customer PII is transmitted or stored. Client account data is segregated at the data layer — cross-client data access is architecturally blocked.
Images captured by the Pickrook vision system are processed locally on the edge controller for real-time SKU identification. Images are not transmitted to Pickrook cloud systems during standard operations. Diagnostic image captures (requested by Pickrook engineering for model improvement) require explicit operator consent and are subject to data handling agreements.
Pick cycle times, per-SKU accuracy rates, exception frequency, and wave completion data are transmitted to Pickrook's monitoring system over encrypted TLS connections. This data is used for system health monitoring and deployment optimization. Aggregated (non-SKU-specific) analytics may be used to improve Pickrook's platform models across deployments.
Pick execution logic runs entirely on the Pickrook edge controller hardware. The robot cell continues operating during cloud connectivity interruptions. Cloud connectivity is used for monitoring and OTA updates only — not for real-time pick execution. This design avoids the operational risk of cloud dependency in a live pick environment.
Pickrook recommends (and assists with configuring) network segmentation that places the Pickrook cell hardware on a dedicated VLAN with controlled access to your WMS API endpoint. The cell hardware requires outbound access to your WMS API (intranet) and Pickrook monitoring (internet). No inbound internet access is required or recommended.
All data transmission between the Pickrook controller and your WMS, and between the controller and Pickrook monitoring, uses TLS 1.2+ encryption. WMS API credentials are transmitted exclusively over HTTPS. Local edge controller storage uses encrypted volumes for sensitive configuration data.
Physical access to the Pickrook edge controller requires operator credentials. Remote access by Pickrook engineering (for diagnostics or updates) uses role-based access controls with session logging. Remote diagnostic sessions require operator authorization. All access events are logged and available to the operator.
Pickrook is an early-stage company founded in 2024. Our platform is designed with SOC 2 controls in mind — including access management, change management, availability monitoring, and data handling practices consistent with SOC 2 Trust Service Criteria. We are building toward a formal SOC 2 Type I audit as part of our growth roadmap. We do not currently hold a SOC 2 certification.
Pickrook cells are designed with OSHA standards in mind for robotic work cells with human coexistence zones. This section describes our safety design approach — it does not constitute a formal OSHA compliance certification.
Each Pickrook cell includes a safety-rated light curtain perimeter system that halts robot motion when breached. Hard-wired e-stop buttons are located at each cell corner and at the exception station. E-stop activation requires manual re-authorization to resume operation — there is no automatic restart after an e-stop event.
Pickrook's cell safety architecture aligns with OSHA 29 CFR 1910.217 (mechanical power presses as reference) and ANSI/RIA R15.06 (robotic safety standards) design principles. Floor perimeter markings, warning signage, and operator training materials are provided as part of every deployment. This is a design alignment — Pickrook does not certify individual installations as OSHA compliant (that determination is the operator's responsibility).
The exception station and cell monitoring position are designated co-existence zones where human operators work adjacent to the robot cell. These zones are outside the robot's reach envelope and are separated by the safety perimeter. Co-existence zone design is documented in the deployment scope document provided to each customer.
Robot firmware and vision model updates are delivered over-the-air (OTA) and require operator authorization before installation. Updates install during scheduled maintenance windows — not during active pick operations. Each update includes a rollback path that can be activated by the operator if operational issues are observed post-update.
If you're a 3PL operator or fulfillment center evaluating Pickrook and have specific security requirements — network architecture documentation, data handling agreements, or safety certification questions — contact us directly. We'll provide the documentation your procurement or IT team needs.
Contact Security Team