Windows 11 Voice Access processes speech on the device and does not send voice recordings to the cloud, but Voice Access itself cannot be described as “HIPAA certified”; your organization must approve the complete workflow used to handle protected health information (PHI).
Microsoft specifically states that all Voice Access speech processing happens on the device and that voice data is never sent to the cloud. For Voice Isolation, its downloaded model also runs locally, creates a locally stored voice signature, and does not upload the recording.^1^
Avoid confusing Voice Access with Voice Typing
These are different Windows features:
- Voice Access: The accessibility feature for controlling Windows and entering text by voice. Its speech processing is on-device.
- Voice Typing: Opened with Windows key + H. It uses online speech recognition, so voice data is sent to Microsoft to provide speech-to-text transcription.^2^
To reduce the chance of accidentally using the cloud-based feature:
- Open Start > Settings > Privacy & security > Speech.
- Set Online speech recognition to Off.
- Start and use Voice Access, rather than pressing Windows key + H.
- Ask your organization’s privacy or security administrator to document this configuration in its HIPAA risk assessment.
Turning off online speech recognition restricts Windows to device-based speech features; Microsoft states that device-based recognition processes voice locally and sends no voice data to Microsoft.^2^
HIPAA boundary
There is no U.S. Department of Health and Human Services certification standard that declares an individual product or feature “HIPAA compliant.” Microsoft supports customers’ HIPAA obligations for specified enterprise services, but using a Microsoft product does not by itself make an organization compliant.^3^
Your organization therefore needs to evaluate more than speech processing, including:
- Where the recognized text is entered and stored.
- Whether the destination application synchronizes PHI to a cloud service.
- Access controls, screen privacy, audit logging, retention, encryption, and device security.
- Whether any cloud service receiving PHI is covered by the organization’s applicable Business Associate Agreement (BAA).
- The risk of other people’s speech being captured in a shared office.
The practical conclusion is: Voice Access audio processing is local, but the HIPAA acceptability of using it with patient information must be approved as part of your employer’s complete PHI workflow. Provide the Microsoft Voice Access privacy documentation to your HIPAA privacy/security officer rather than treating local processing alone as proof of compliance.
References
- Improve speech recognition with Voice access | Microsoft Support
- [Windows 11](https://support.microsoft.com/windows/privacy/speech-voice-activation-inking-typing-and-privacy#summary)
- Health Insurance Portability and Accountability Act (HIPAA) & Health Information Technology for Economic and Clinical Health (HITECH) Act