Skip to content
Security / By architecture

Patient data stays behind a trusted server boundary.

Recall is designed around practice-owned controls, trusted/server-authoritative access, minimum-necessary browser data, private storage, and auditable actions.

The public preview uses synthetic sample data only. No PHI appears on public pages, and no production security control is implied by this presentation.

Chapter 01 / The boundary
Controls belong to the practice

Security is a set of responsible boundaries.

The public explanation stays at the level the canonical implementation can support. It describes the shape of the system without exposing internal access details.

01

Practice-owned controls

The practice owns the outreach direction, review decisions, and the controls required for its future production path.

02

Trusted/server-authoritative access

Sensitive access and actions are designed to be checked behind a trusted server boundary rather than granted by browser state alone.

03

Minimum-necessary browser data

The browser should receive only the information needed for the current view and interaction—not an unrestricted record.

04

Private storage

Product data belongs in private storage with access governed by the canonical Recall application boundary.

05

Auditable actions

Authorized actions are designed to leave an auditable record so the practice can understand what happened and why.

Public preview / Qualified language

The preview makes its limits visible.

The public pages are a synthetic preview. They do not establish an authorized account, enable PHI, or stand in for the controls required before any production path is opened.

HIPAA-ready production path

The public preview uses synthetic sample data only. Production access for PHI requires a signed BAA and verified privacy and security safeguards.

Chapter 02 / What this page does not claim
Plain boundaries are useful

Read the boundary before the promise.

No PHI on public pages

This public site uses synthetic preview language and does not ask visitors to provide patient information.

No badge in place of evidence

HIPAA-ready describes a gated production path. It does not authorize PHI use or establish production readiness.

No hidden product state

The public presentation does not represent live access, messaging activity, or patient state.

Responsible recall / Practice control

Explore the product boundary in context.

Open the synthetic preview to see the public presentation. Any future production path remains gated by the applicable account, privacy, security, and agreement controls.

Open Recall