Privacy

Privacy stays narrow by design

The launch version of ScopeUp is intentionally limited to professional workflow support. It is built to avoid patient-specific storage and to keep account and review data within a small, operational scope.

What ScopeUp collects now

ScopeUp public beta is built for pharmacist workflow support, not patient recordkeeping. Account setup is limited to professional profile details such as role, region, availability, and workspace preferences.

Operational submissions such as corrections, source suggestions, shift requests, and job interest may include your professional contact details so the team can review or reply.

ScopeUp measures site usage anonymously and without cookies: a random per-visit identifier records which pages were opened, for how long, and which tools were used (for example that a dose check or an assessment printout happened — never its contents). It is not linked to your identity, IP address, or device, and it disappears when you close your browser.

What ScopeUp does not accept or store

  • Patient names, health card numbers, prescription numbers, case notes, or medication histories.
  • Claim payloads, adjudication data, or uploaded payer documents for processing.
  • Patient-specific AI prompts or charting content.

How public workflow feedback is handled

Suggestion and correction messages are screened for obvious PHI patterns before they enter review. Do not include patient names, health card numbers, prescription numbers, or other identifying information.

Submitted content is treated as operational review material, not as a private messaging channel.

Security and retention approach

ScopeUp keeps launch scope narrow to reduce privacy risk. The beta is intended to store only the minimum account and review data required to operate the service, and reviewed reference content remains the primary product surface.

If privacy expectations or data scope change, ScopeUp should update this page before expanding product capabilities.

Next steps

Return to public workflows, move into workspace setup, or review the related launch documents from the same trust boundary.