This document dictates the operational handling of data ("we," "us," or "our") when subjects utilize our web applications, hardware sensing modules ("Sensors"), and other digital systems (collectively, the "Services"). By interfacing with our systems, you conform to the data ingestion protocols detailed herein.

AirCal operates a radially transparent public data lattice. By configuring a Sensor, you authorize the telemetry of environmental data to the public record.

Telemetry Payload entails:

• Atmos: PM1.0, PM2.5, PM10, Temp, Humidity.
• Geo: Lat/Lng coordinates (obfuscated).

Privacy Protocol: Absolute node locations are obfuscated via radial fuzzing. Pinpoint residential locations are never exposed to the public API endpoint, maintaining scientific validity while protecting the perimeter.

A. Subject Input

Account Auth: Alias, email vector, and cryptographically hashed keys. Restricted to system ops.

B. Hardware Telemetry

• Sensors: High-frequency PM, temp, and humidity polling.
• Network: SSID strings, dynamic IPs, machine ID, calibration errors.

C. Passive Monitoring

Session Data: Cookie strings, access logs, UI interaction paths.

Data payload is utilized strictly for system functions:

• To construct the global verification map.
• To train onboard algorithmic compensation networks.
• To transmit mission-critical diagnostic alerts.

Identity data persists during active account status. Upon termination, identity vectors are wiped. However, historical atmospheric telemetry, scrubbed of origin markers, is permanently integrated into the global dataset.

For legal and privacy inquiries, route communications to:privacy@aircal.com