Security and data handling

Clinical chart traffic stays local. Licensing stays separate.

PerioMaxer is designed as two distinct planes so the cloud account service is not designed to accept or store voice audio, patient names, or periodontal chart values.

Local data plane

Phone ↔ office desktop

  • Voice recognition uses the selected mobile speech backend and platform.
  • SmileMaxer’s cloud does not receive or store voice audio.
  • Pairing uses WSS with certificate-fingerprint pinning.
  • Chart entries travel over the practice LAN.
  • Windows keeps entries in session memory long enough to place them in the PMS.
  • Mac supports pairing, session preview, and dry-run without PMS writes.
Cloud configuration plane

Account ↔ licensing service

  • Practice account, plan, and one location.
  • Registered mobile-device and computer IDs, names, platform/app versions, pairing metadata, last-seen times, and revocation or license status.
  • Selected computer, session timestamps, heartbeat status, public IP, and trusted coarse country/region when available.
  • Not designed to accept or store patient identities, chart values, or voice audio.

IP addresses are never the license key.

Office networks change. PerioMaxer accepts routine IP rotation when the enrolled device and office account still match. A public IP may help identify repeated, clearly simultaneous geographic anomalies for human review; it is not used as an automatic clinical-session block.

Administrative controls

  • One-time enrollment links
  • Fresh pairing token for each operatory connection
  • Registered-device list and device revocation
  • Session heartbeat expiry releases an inactive seat

This overview describes product architecture and is not legal advice or a certification. Contractual terms are in the Terms, Privacy Policy, and applicable BAA.