Trust & Governance

Your Data. Your Environment. Your Intelligence.

AIREZ exists to help organizations better understand their own environments.

Customer information belongs to the customer.

Our responsibility is to help that information work for you — securely, responsibly, and transparently.

Talk to our team Read the Privacy Policy

Version 1.0 · Effective January 1, 2026 · Last updated January 1, 2026

Our commitment

Four principles that govern how we handle customer information

These are not aspirations. They are constraints on how the platform is designed, how our agreements are written, and how our business model works.

Customer ownership

Customer operational data remains the property of the customer. AIREZ processes it on the customer's behalf, under the customer's agreement, for the customer's purposes.

No data sales

AIREZ never sells customer operational data. Customer information is not a product, and our commercial model does not depend on it becoming one.

Security by design

Enterprise security and privacy considerations are built into the platform architecture from the beginning — not layered on after deployment.

Responsible AI

Artificial intelligence should improve customer operations while protecting privacy and confidentiality. Autonomy is bounded, and a person remains accountable for consequential decisions.

How customer data is used

Customer information is processed solely to deliver platform functionality

Every use below exists to improve the customer's own operations. There is no secondary purpose, no external audience, and no downstream commercial use of customer operational data.

Sensor fusion

Combining signals from the systems a customer already owns into one situation.

Operational awareness

Maintaining an accurate, current picture of the customer's own environment.

Event detection

Identifying conditions that matter to the customer's operations and safety.

AI reasoning

Interpreting observations in context to reach a conclusion an operator can act on.

Notifications

Delivering the right context to the right person at the right moment.

Automation

Driving bounded, policy-governed responses through connected systems.

Reporting

Producing the operational and compliance records the customer requires.

Customer dashboards

Presenting the customer's own intelligence back to the customer.

Improving the platform responsibly

Better reasoning, without exposing anyone's environment

To improve contextual understanding and platform performance, AIREZ may analyze anonymized and de-identified operational patterns that cannot reasonably identify a specific customer, facility, individual, or location.

Any information used for research or model improvement is stripped of customer-identifying details before analysis.

Operational identities, customer names, facility names, addresses, personnel, and proprietary information are never disclosed through this process.

The objective is to improve pattern recognition and contextual reasoning — not to expose customer information.

Safeguards

Identifying fields are removed before any pattern reaches a research process.
Patterns are evaluated in aggregate rather than as individual customer records.
Media and raw sensor content are not required for pattern-level improvement.
Customer agreements govern the scope of any analysis, and enterprise terms may restrict it further.

What we do not do

The commitments that are easiest to verify are the ones stated plainly

AIREZ does not sell customer data
AIREZ does not share customer operational information for advertising
AIREZ does not reveal customer identities
AIREZ does not reveal facility locations
AIREZ does not publicly disclose customer operational events
AIREZ does not use customer environments for marketing without permission

Data retention

Retention is a customer decision, not a platform default

Organizations determine how long operational information should be retained. AIREZ configures retention to your policy rather than imposing one.

Future platform versions will allow administrators to configure retention schedules directly for individual categories of operational data — media, events, sensor telemetry, audit records and reports — from the AIREZ Admin Panel.

Retention periods may vary based on

Regulatory requirements
Customer policy
Industry standards
Operational needs

Enterprise security

Designed to support the controls enterprise security teams expect

Where a control is operating today we say so. Where we are still building toward a formal attestation, we say that instead.

Encryption

In place

Data is encrypted in transit, and platform storage is designed to support encryption at rest across managed services.

Role-based access control

In place

Access is scoped by role and by deployment so that users see only the environments and functions their role requires.

Authentication

In place

Administrative access requires strong authentication, and the platform is designed to support enterprise SSO and multi-factor requirements.

Audit logging

In place

Administrative and access events are logged so customers can reconstruct who did what, and when.

Secure cloud infrastructure

In place

Deployments run on established cloud and edge infrastructure with hardened baselines and separated environments.

Security monitoring

In place

Platform telemetry is monitored for anomalous access and service behaviour, with defined escalation paths.

SOC 2 readiness

Building toward

AIREZ is building toward SOC 2 Type II by aligning controls, evidence collection and policy documentation to the Trust Services Criteria. No certification is claimed at this time.

Administrative controls

Building toward

Customer administrators are gaining progressively more direct control over retention, access, integration and automation policy through the Admin Panel.

Security questionnaires, architecture reviews and diligence requests are welcome. Contact security@airez.com.

Responsible artificial intelligence

AI recommendations support human decision-making

The platform's role is to assemble understanding and present it with its evidence. The authority to act — and the accountability for acting — stays with the organization.

Transparency

Customers should understand what the platform observed, which systems contributed, and why a conclusion was reached.

Context

A signal is never evaluated alone. Conclusions are drawn from the relationship between signals, schedules, conditions and system state.

Human oversight

AI recommendations support human decision-making. Consequential actions remain subject to human authority and customer policy.

Continuous improvement

Confirmed and dismissed outcomes refine thresholds and confidence, so the platform becomes more accurate in the customer's own environment.

Privacy protection

Privacy considerations are treated as design constraints on what the platform observes, retains and surfaces.

Explainability

Every conclusion carries its contributing evidence and a confidence value, so operators can evaluate it rather than simply obey it.

Responsible automation

Autonomy is bounded by policy. The platform escalates rather than exceeds the authority a customer has granted it.

Frequently asked questions

The questions procurement, legal and security teams ask first

Who owns my data?: You do. Customer operational data remains the property of the customer. AIREZ processes it on your behalf as a processor under your agreement, for the purposes of delivering the platform to you.
Does AIREZ sell customer information?: No. AIREZ does not sell customer operational data and does not share it for advertising purposes. Our business model is based on helping you gain value from your own operational data — not on monetizing it.
Can AIREZ employees access customer environments?: Access is limited to authorized personnel, scoped by role, and permitted only for support, troubleshooting, or work you have requested. Access is logged, and enterprise agreements can add approval requirements and further restrictions.
Does AIREZ train AI using customer data?: AIREZ may analyze anonymized and de-identified operational patterns to improve contextual understanding and platform performance. Identifying details are stripped before analysis, and customer identities, facilities, locations and proprietary information are never disclosed through this process. Enterprise agreements may restrict this further.
How is data anonymized?: Customer-identifying details — names, facility identifiers, addresses, personnel references and location precision — are removed before any pattern reaches a research process. Patterns are then evaluated in aggregate rather than as individual customer records.
How long is information retained?: Retention depends on the category of information, your regulatory obligations, your internal policy and your operational needs. Retention terms are defined in your agreement rather than fixed by AIREZ.
Can customers control retention policies?: Yes, and increasingly directly. Retention is configured with your organization today, and future platform versions will allow administrators to configure retention schedules per category of operational data from the Admin Panel.
What happens if our organization leaves the platform?: Your data remains yours. On termination, AIREZ supports export of customer operational data in an agreed format and deletes or returns remaining data according to the terms of your agreement and any regulatory obligations that apply.

Closing

Trust is the foundation of Physical Intelligence.

Organizations trust AIREZ with information about some of their most important environments. We take that responsibility seriously by protecting customer privacy, securing operational data, and continuously improving the platform through responsible and privacy-preserving practices.

Questions about privacy, data handling or AI governance can be directed to privacy@airez.com.

Contact sales Terms of Use