Privacy policy.
AXIS BLUE is designed to minimize data collection, limit retention, and scope access strictly to operational intent.
What AXIS Collects
- Operator identity data (name, employee/operator ID, role) when provided or required by the client workflow.
- Visit/day context (date, route deck selection, store identifiers, operator-entered notes, workload inputs like deliveries/cases/pallets).
- Evidence and media (photos, documents, generated PDFs, and metadata such as timestamps).
- Scan data (barcodes/UPCs/QR codes and related scan results). Scanning is designed to process frames locally when possible.
- Approximate location signals (GPS/location may be used to confirm a start/stop or associate a visit to a site; manual confirmation remains supported).
- Device and technical data (IP address, browser type, basic diagnostics, and limited device identifiers needed for security and integrity).
How AXIS Uses Data
- To create operator records, visit logs, and client-facing reports.
- To improve reliability (debugging, performance monitoring, error logs).
- To enforce workflow integrity (sequence, timestamps, and anti-tamper signals where applicable).
- To support evidence retention rules required by clients.
Where Data Is Stored
In the current stage, non-foundation usage is local-only by default. Data stays on the device unless a user explicitly exports it. Foundation-level usage may store structured records and related outputs beyond the local device when configured.
Third-Party Processors
- Rendering: AXIS may use third-party services to generate documents from operator data and templates.
- Scanning: AXIS may use third-party services to enable barcode/QR scanning within supported environments.
Third-party services are used as infrastructure components and are not intended to be visible in the operator experience. They may process data strictly to provide the requested functionality.
Sharing
Data is shared primarily with the client organization operating AXIS and its authorized users (e.g., leadership, supervisors, relief operators), based on permissions. AXIS does not sell personal data.
Security
AXIS uses standard security controls appropriate for field systems (access control, authentication, transport security, and least-privilege storage where configured). No system is perfectly secure, and operational security depends on correct deployment and permissioning.
Retention
Non-foundation usage is local-only and is cleared by the user. Foundation-level retention follows configured policies and may vary by tenant or program.
Your Choices
- Operators may be required to provide certain information to complete a workflow.
- Where location is used, operators may be prompted to confirm or manually input a site when automatic detection fails.
Contact
For privacy and data requests, contact foundation@axisblue.io.
Last updated: 2026-04-10