Security at DC-Air Watchdog
Last updated: April 25, 2026
Summary
DC-Air Watchdog is built with privacy and security as defaults. We monitor wireless intraoral sensors using read-only access to existing log files and do not store, transmit, or process any patient health information (PHI). Every practice is fully isolated from every other practice at the database layer. All connections are encrypted in transit. Bearer tokens and user passwords are never stored in plaintext.
Latest scan results
Captured 2026-04-25. Click any thumbnail for the full page. Or run a live re-scan via the link below each card.
What we collect (and what we don't)
| We collect | We do not collect |
|---|---|
Sensor serial numbers (e.g. S0001993) |
Patient names or any PHI |
| Docking-station serial numbers | Dental images or X-ray pixel data |
Operatory PC name (e.g. OP1-DESKTOP) |
Patient appointment data, schedules, or notes |
| Event timestamps (dock, undock, image-captured, BT) | Insurance, billing, or payment data |
| Sensor health (battery %, signal dB, temperature) | Browsing history or other behavioral telemetry |
| Image quality stats (median energy of each X-ray) | Practice financial records (beyond the per-X-ray price you optionally enter) |
The agent on each operatory PC reads the existing Athlos SDK log file, filters out everything except the events listed above, and discards the rest before transmitting.
How we protect your data
practice_id at the database layer. There is no path by which one practice can see another's data. Verified at every query.Hosting
DC-Air Watchdog runs on Amazon Web Services in US East (Ohio). The application server runs FastAPI on Amazon Linux 2023 behind nginx. Persistent data lives in PostgreSQL 16. SSH access is restricted to a private key held only by DentalTI; the security group permits only ports 22, 80, and 443 from the public internet.
Reporting a security issue
If you believe you've found a security issue, please email david@dentalti.com with details. We will acknowledge receipt within 2 business days and work with you to verify and address the issue. We do not currently run a paid bug bounty program, but we publicly thank researchers who report valid issues responsibly.
See also our machine-readable security contact at /.well-known/security.txt.
Roadmap
In flight or planned:
- Code-signed Windows installer (signing certificate ordered)
- Encrypted off-site backups in a separate AWS account
- Third-party penetration test (planned for Q3 2026)
- SOC 2 Type 1 (planned for Q4 2026, depending on customer demand)
- Business Associate Agreement (BAA) availability for practices that request one