Practice-owned controls
The practice owns the outreach direction, review decisions, and the controls required for its future production path.
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.
The public explanation stays at the level the canonical implementation can support. It describes the shape of the system without exposing internal access details.
The practice owns the outreach direction, review decisions, and the controls required for its future production path.
Sensitive access and actions are designed to be checked behind a trusted server boundary rather than granted by browser state alone.
The browser should receive only the information needed for the current view and interaction—not an unrestricted record.
Product data belongs in private storage with access governed by the canonical Recall application boundary.
Authorized actions are designed to leave an auditable record so the practice can understand what happened and why.
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.
The public preview uses synthetic sample data only. Production access for PHI requires a signed BAA and verified privacy and security safeguards.
This public site uses synthetic preview language and does not ask visitors to provide patient information.
HIPAA-ready describes a gated production path. It does not authorize PHI use or establish production readiness.
The public presentation does not represent live access, messaging activity, or patient state.
Open the synthetic preview to see the public presentation. Any future production path remains gated by the applicable account, privacy, security, and agreement controls.