Security and data handling

Clinical chart traffic stays local. Licensing stays separate.

Office Link sends chart entries directly between your devices. Cloud services handle accounts, connection diagnostics, and voluntary feedback; they do not relay live charting or speech.

Local data plane

Phone ↔ office desktop

  • Voice recognition uses the selected mobile speech backend and platform.
  • Speech recognition runs locally and does not upload audio.
  • Pairing uses WSS with certificate-fingerprint pinning.
  • Chart entries travel over the practice LAN.
  • The Windows companion keeps entries in session memory long enough to place them in the PMS.
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.
  • Account and licensing interfaces do not accept clinical chart traffic. Optional connection diagnostics contain fixed codes, counts, and timings.
  • Support receives the feedback and files you select, including non-patient test recordings. Do not include patient information. See our Privacy Policy.

An IP address never licenses a computer.

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

  • Fresh pairing token for each operatory connection
  • Registered-device list and device revocation
  • Session heartbeat expiry releases an inactive charting session

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