NAWAMarketing scope only
Forms prohibit symptoms, medical history and patient details.
Trust center
Specific boundaries are more trustworthy than broad promises
This page separates website behaviour, engineering principles and still-unapproved legal or product assertions.
See how NAWA connectsIllustrative model; it does not represent live product data, and approved product captures are still pending.
Illustrative two-way data flowIllustrative two-way flow
NAWAOne connection
This website
Minimal data, no health-information forms, no analytics vendor by default
Locale and audience may be stored as first-party preferences. The vendor-neutral analytics seam sends no network request until an approved destination is connected. Contact submission fails safely when no lead destination exists.
Explore 3 pointsMarketing scope only · No fake success · No tracking destination
No fake success
Unavailable integrations show a configuration state.
No tracking destination
Events remain local unless an approved analytics sink is configured.
Product principles
Least-necessary access, accountability and human oversight
These are design and engineering principles, not claims of certification, residency, encryption scope, backup coverage or legal compliance.
Explore 3 pointsRoles and permissions · Human control · Approval gates
Roles and permissions
Access should be explicit, scoped and reviewable.
Human control
Assistive AI remains subordinate to professional review.
Approval gates
Hosting, subprocessors, data roles and legal claims require owner and counsel approval.
Need a specific trust answer?
Use the organization contact path once a real lead destination is configured. Do not send patient or health information.