TOL Scribe Website and Extension Privacy Policy

Scope

This policy applies to the current TOL Scribe web application and the TOL Scribe EMR Filler browser extension used to move clinician-authored prescription drafts into supported EMR prescription forms.

What the website stores

• The website stores local session state in the browser so the user can stay signed in during a pilot session.
• The website stores local workflow preferences such as the selected EMR output format and recently used options.
• The website does not send prescription drafts, patient context, or clipboard content to a remote server in the current pilot build.
• The website does not run third-party analytics, advertising scripts, or tracking pixels in the current pilot build.

What the browser extension does

• The extension reads clipboard text only after the user explicitly chooses the Read Clipboard action.
• The extension fills EMR prescription fields only after the user explicitly chooses the Fill Fields action.
• The extension stores the selected target EMR locally in browser extension storage.
• The extension does not auto-sign prescriptions.
• The extension does not auto-send prescriptions.
• The extension does not transmit prescription payloads, patient information, or browsing activity to an external server in the current pilot build.

Current host permissions

In the current pilot release, the extension is scoped to Juno OSCAR Rx pages matching:

https://*.junoemr.com/juno/oscarRx/*

User control

• The clinician remains responsible for reviewing all filled fields before saving, signing, or issuing a prescription.
• The user can remove the browser extension at any time through the browser’s extension settings.
• The website session and locally stored preferences can be cleared through normal browser storage controls.

Data sharing

In the current pilot release, TOL Scribe does not intentionally transmit prescription payloads, clipboard contents, or patient context to external services for processing.

Support

For product support information, troubleshooting steps, and current extension scope, see the Support page.