Security
Understand how your clinical data is handled and the controls available to you and your workspace.
Last updated: September 6, 2026
Data in transit
All traffic runs over HTTPS, and the live transcription stream runs over a secure WebSocket. The browser reaches the transcription service using short-lived, scoped tokens minted server-side, so the durable API keys never reach the client.
Data at rest
GO stores transcripts, notes, patient records and assistant chat history in your workspace. Temporary audio, cached template and patient options, finalized text, local drafts and queued changes are encrypted per account on this device. Audio is removed after confirmed session and transcript save, discard or sign-out. Other pending changes stay until sync or discard; signing out clears local data. Servers check clinical record access against your user and workspace.
Authentication and access control
Workspace roles separate owners, clinicians, and viewers. Patient records and templates are shared within a workspace; encounters are scoped to their clinician. Viewers cannot record sessions, generate notes, or change clinical content.
Two-factor authentication and devices
Protect your account with an authenticator app and recovery codes. Review your signed-in devices and revoke one session or all sessions. Workspace owners can require members to enroll in two-factor authentication.
Export, deletion, and workspace policies
Download your account data, export patient records, and save notes as PDFs. Deleted sessions stay in trash until restored or permanently removed. Owners can set a retention period for trashed clinical records, restrict public template sharing, and control calendar connections and appointment writing.
Minimal logging
We never log transcript text, note content, audio, prompts, or model completions. Operational logs carry identifiers and error codes only. Owners can review workspace activity and export the audit log.
Secrets handling
Service credentials stay on the server. Connected calendar tokens, authenticator secrets, and integration secrets saved in the application are encrypted at rest.
Subprocessors and BAAs
Transcription (Deepgram) and note generation (via OpenRouter) receive session content. A HIPAA-compliant deployment requires Business Associate Agreements with these providers and a configuration that disables data retention and model training.
Reporting an issue
If you believe you have found a security vulnerability, please contact security@nextvisit.ai rather than filing a public issue.