Data policy.
AXIS BLUE is designed to minimize data exposure, control storage cost, prevent misuse, and keep operational evidence scoped to its intended purpose.
What we collect
AXIS BLUE may collect operational context such as visit metadata, user-provided inputs, structured event logs, and evidence uploaded or captured during controlled usage windows.
Evidence may include photos, documents, and supporting notes. Collection is intended to be operator-initiated and purpose-limited, not continuous monitoring.
How data is processed
Operational inputs may be processed to generate structured outputs (for example: summaries, counts, classifications, or other derived records) to support reporting and workflow continuity.
Where supported, AXIS BLUE is designed to prefer retaining derived operational records over retaining raw evidence. Processing methods and outputs may evolve over time as the platform develops.
Retention and storage limits
Evidence windows and retention rules may be enforced. Storage limits may apply per user, per visit, per organization, or per time period to control cost, reduce exposure, and prevent misuse.
Raw evidence may be retained only as long as operationally necessary, and may be reduced, transformed, exported, or discarded based on configuration, workflow requirements, and administrative policy.
AXIS BLUE does not guarantee long-term preservation of raw evidence or derived records. Users and organizations are responsible for exporting or retaining records as required by their internal policy or applicable law.
Access and sharing
Access may be limited by role, configuration, time windows, keyholder mechanisms, or explicit approval. Sharing is intended to be controlled and temporary.
Administrators and deploying organizations are responsible for assigning access, distributing keys or pins, and ensuring access aligns with internal requirements.
Organizational boundaries
Where supported, AXIS BLUE separates data by organization, program, or operational context. No system is immune to misconfiguration, and administrators are responsible for validating access controls and retention settings in their environment.
What AXIS BLUE is not
AXIS BLUE is not intended to serve as a forensic evidence platform, a legal system of record, or a tool for behavioral surveillance. It provides operational capture and visibility, not determinations or enforcement.
Policy updates
This policy may be updated as AXIS BLUE evolves. Material changes will be reflected on this page.