Built for consented deployments.
acoAR uses acoustic echoes and radio signals to create spatial awareness — without cameras, visual identity capture, or intelligible audio recording.
This page documents our privacy principles, technical controls, the boundaries of what acoAR is designed to support, and our regulatory posture.
How acoAR processes signals.
Signal capture
The SDK accesses the device microphone and speaker to emit and receive near-inaudible acoustic chirps. Raw audio is processed locally — it is never transmitted to a server in default configuration.
Feature extraction
Acoustic echoes are converted on-device into geometric features: distances, angles, and reflection signatures. The output is numerical geometry data — not audio recordings. No speech, voice, or ambient sound is retained.
Spatial events
The acoAR engine produces a structured event stream: position coordinates, room identifiers, presence flags, confidence scores, and uncertainty radii. No audio. No images. No visual identity data.
Default settings and configurability.
| Control | Default | Configurable |
|---|---|---|
| Raw audio retention | Off | No |
| Feature data retention | Session only | Yes |
| Spatial map storage | Session only | Yes |
| Sensing zones | All | Yes — admin-defined |
| Consent disclosure | Required | Not configurable |
| Through-wall sensing | Off | Yes — policy-gated |
| Data export | API available | Enterprise tier |
What acoAR will not support.
These are not just guidelines — they are design constraints. Some of these capabilities are technically possible but are explicitly excluded from the product, API, and permitted use policy.
- 01Covert monitoring without user disclosure
- 02Surveillance of public spaces without consent infrastructure
- 03Collection of raw audio for analytics, training, or any secondary purpose
- 04Identification or re-identification of individuals from acoustic signatures
- 05Workplace monitoring of employees without disclosed, policy-bound configuration
- 06Deployment in children's environments without guardian/operator consent
- 07Law enforcement or government surveillance use without strict legal basis
- 08Hidden through-wall sensing of adjacent occupants without their knowledge
GDPR, CCPA, and healthcare.
acoAR processes derived spatial features, not personal audio. Spatial coordinates may constitute personal data in certain jurisdictions. We are preparing Data Processing Agreement templates for enterprise deployments. Contact us for GDPR readiness questions.
No personal audio is collected. Spatial coordinate data is handled according to our data retention controls, which are configurable per deployment. We do not sell spatial data to third parties.
acoAR is not a medical device. Healthcare and eldercare deployments require operator-level consent infrastructure, appropriate clinical governance, and are discussed case-by-case. We do not make clinical claims.
Enterprise security controls.
Security questionnaire & DPA.
An enterprise security questionnaire is available on request. Data Processing Agreement (GDPR) templates are in preparation.