Privacy
This page is a privacy summary, not the binding legal Privacy Policy — the full Policy will be published prior to general availability. It distinguishes what the public prototype actually collects today (marketing site signups, contact form, basic analytics — never PHI) from the privacy posture engineered for the production stack once design-partner relationships are in force.
What this site collects today
Verifiable in codeOne row per surface that touches user input. The codebase is public at github.com/hucmaggie/pause-health.ai — a privacy reviewer can verify each claim against the referenced code path.
What we collect: Email address only.
Where it goes: Forwarded to a configured provider (Formspree / Resend / Mailchimp / Buttondown / ConvertKit) via /api/subscribe. If no provider is configured the server logs the email and drops it. Anti-bot check via Cloudflare Turnstile.
What we collect: Name, email, subject, message. Pre-filled subject/message from URL params on inquiry-deep-links.
Where it goes: Forwarded to /api/contact -> configured provider (log / Formspree / Resend) and reaches the human inbox you'd expect (partners@ / invest@ / press@ / hello@). Anti-bot check via Cloudflare Turnstile.
What we collect: Basic page-view + referrer telemetry via Vercel Analytics (if enabled in the deployment). No third-party advertising cookies. No cross-site tracking.
Where it goes: Aggregated dashboards in Vercel. Individual visitors are not identified.
What we collect: Hosted by Salesforce, not by Pause-Health.ai. Messages typed into the chat go to the Salesforce-hosted Messaging Channel, governed by Salesforce's privacy terms.
Where it goes: Salesforce SCRT2 conversation infrastructure. The demo personas above the chat are synthetic; do NOT enter real personal health information into the prototype chat.
What we collect: Nothing about the visitor. The personas are seeded synthetic data baked into the codebase (lib/demo-cohort.ts).
Where it goes: Nowhere — the cohort is in-process state. Identity resolution against the Salesforce sandbox uses synthetic seed data only.
What we collect: Standard request logs (path, status, timing) on Vercel. Client IP is read for rate-limiting on the form endpoints (lib/anti-bot.ts) but not persisted to a first-party store.
Where it goes: Vercel platform logs, retained per Vercel defaults.
What the production stack is designed to handle
Pre-GA postureThe privacy framework engineered for the production deployment, once design-partner provider organizations are onboarded under BAA. Mapped against HIPAA Privacy Rule and state privacy laws (CCPA / CPRA). See /hipaa for the HIPAA-specific view and /security for the technical controls.
PHI accessed only under BAA, only for the workflows the Covered Entity contracts for, and never used for marketing, sale, or fundraising.
Analytics and model evaluation use de-identified data sets following the HIPAA Safe Harbor + Expert Determination methods. Re-identification is contractually prohibited.
Pause-Health.ai supports the Covered Entity in fulfilling patient rights requests via documented APIs and runbooks; requests are routed through the patient's own provider organization.
PHI handled under HIPAA is largely outside CCPA / CPRA scope, but the platform's marketing-site data (newsletter, contact) is treated under CCPA / CPRA rules for opt-out, correction, and deletion.
No third-party advertising or cross-site tracking cookies on the marketing site, today or planned. Authentication cookies in the production product are first-party and session-scoped.
Aligned with HIPAA Privacy Rule records-retention requirements (6 years) for PHI handled under BAA; marketing-site data retained only as long as the related operational purpose requires.
For privacy questions or requests
Email privacy@pause-health.ai. To unsubscribe from the newsletter, use the unsubscribe link in the email itself (the configured provider handles it) or email the inbox above. To delete a contact-form submission, email the same inbox referencing the date / subject and we'll purge it from the configured provider on our end.
