General Counsel Briefing v0.1

HIFP · v3 reference · rendered from HIFP-general-counsel-briefing-v0.1.md

Reference · v3 vintage

HIFP — General Counsel Briefing v0.1

Purpose. Prepare Fatima to walk into a general-counsel conversation with a complete picture of what HIFP is, the regulatory landscape it operates in, the specific legal questions we need answered, and the sequence of legal deliverables we need in place. Structured so counsel can prioritize. Date. 2026-09-07 · shipped same day as trio alignment meeting Author. Brandon (with Fatima). For Fatima to carry into the Karen briefing (§3.24). Companion. [[HIFP-session-notes-2026-09-07-alignment]] · [[HIFP-life-insurance-judo-memo-v0.1]] · [[HIFP-ethical-framework-v0.1-skeleton]] · [[HIFP-compliance-foundation-v0.1]] · [[HIFP-insurance-liability-v0.1]] · [[HIFP-ip-assessment-v0.1]]. Status. Draft for counsel handoff. Written to be readable by a general-practice attorney; refers to specialized-counsel workstreams where appropriate.

§1 · What HIFP is (60-second frame for counsel)

HIFP is a consumer-facing planning platform that integrates a user's health signal (wearables + biomarkers + patient-portal records + self-reported medication + condition data) with their financial signal (accounts + insurance + real estate + long-term-care policies) to help them make better retirement-and-longevity planning decisions.

HIFP does not provide financial advice, provide medical advice, prescribe, diagnose, sell insurance products, or hold user funds. HIFP surfaces questions users should be asking their advisors + clinicians, provides plan-modeling outputs, and enables the user to share those outputs with their trusted advisors on their own terms.

Founder trio: Brandon Stauber (CPO/CTO through Series A · Salesforce GTP background · prior-startup operator), Dr. Sindhu Pandit (VP, Clinical Product Strategy at Hyro · CCO of HIFP as of 2026-09-07), Dr. Fatima Paruk (prospective CEO · Oracle → medical training + healthcare-tech leadership). Pre-SAFE.

Mission-level commitment (ratified 2026-09-07): User Primacy — every product decision filters through whether the individual user benefits, not the intermediaries around them. HIFP's fiduciary and ethical obligation is to the user, addressing the market failure of information asymmetry between consumers and their advisors + clinicians.

§2 · What we need from counsel — priority order

2.1 · Mutual NDA template (immediate blocker)

Standard mutual NDA we can execute with market-signal lunch participants, informal investor conversations, partner intros, and prospective founding-eng candidates.
Not sensitive-perpetual scope — mutual, 3-year term, standard carve-outs, HIFP-branded.
Blocking item. No external conversation happens without this in hand. See §7 sequencing.

2.2 · ToS + Privacy Policy framework (pre-external-tester distribution)

Consumer-facing terms for HIFP's app + web surface.
Load-bearing provisions we need explicit counsel guidance on:
Data-scope architecture (see §3.1 below) — architectural + contractual guarantee that HIFP produces only planning-scenario outputs, never carrier-consumable raw-data exports. Need language that binds HIFP + disclaims warranty for underwriting-adjacent use.
Per-event affirmative consent for any share event (with named recipient class + purpose).
User's right to delete (with the open R&D question about delete-forever vs pause + minimal legal-defense archive — see §4.4).
Advice-boundary language — HIFP does not provide financial or medical advice; every LLM-mediated response is classified + audited (see §3.3).
Geographic gating at MVP — Washington + Illinois excluded pending precedent maturity (see §3.4).

2.3 · Standard-of-care disclaimer for planning outputs

HIFP produces planning-scenario outputs. Users may share those outputs with their advisors + clinicians. Advisors may cite them.
We need language that disclaims warranty for planning outputs used in insurance underwriting decisions or as the sole basis of any material financial decision, while preserving HIFP's positive value proposition.
Distinct from: the third-party carrier data-use question (§3.1).

2.4 · BAA + MSA templates for partners

Chain partner (concierge medicine practice) MSA — includes indemnification, liability limitation, physician-partner APS-hygiene protocol (see §5.4).
BAA for any covered-entity partner (concierge practice with HIPAA obligations, or downstream health-data channels).
Standard SaaS MSA for employer buyers (self-funded employers with long-term-equity plans is the primary segment — see §6).

2.5 · Corporate formation + IP-assignment infrastructure

IP-assignment agreements for all current founders + engineers + contractors + advisors. Retroactive review required for pre-existing arrangements.
Delaware C-corp formation timing — pre-SAFE or at-SAFE-close?
Founder equity split + vesting schedules (4-year with 1-year cliff, standard).
Advisor equity ranges (targeting 0.25–0.5% per advisor per §6.8–6.13 of the Open Items Ledger).

2.6 · IP counsel referral (distinct specialty)

HIFP has 4 utility-patent-candidate inventions requiring provisional filings before external POC distribution (see [[HIFP-ip-assessment-v0.1]]).
Karen may not do patents; recommend specialty IP counsel referral. Shortlist: Wilson Sonsini, Cooley, Fenwick, Fish & Richardson.
Publication-sequencing constraint: no external distribution of technical-architecture detail on the 4 inventions until provisional filings land.

§3 · The regulatory landscape — what applies

3.1 · Insurance-carrier data-use — GINA scope + Florida precedent + judo memo

The core concern. Life / disability-income (DI) / long-term-care (LTC) insurance carriers are not covered by GINA — GINA (2008) prohibits genetic-information use in health insurance and employment but does not extend to life/DI/LTC. Carriers in those three lines can lawfully use genetic and health data as an underwriting input in most states. If HIFP produces a nicely-packaged aggregated-health record, carriers could require applicants to disclose it — and HIFP users would be systematically worse off than non-users.

Precedent to know. Florida HB 1189 (2020) — first state to extend genetic-information protections to life + LTC + DI insurers. Applies to policies entered into or renewed on or after January 1, 2021. Prohibits carriers from canceling, limiting, or denying coverage or establishing rate differentials based on genetic information. Important carve-out preserved: does not prevent access to medical records or consideration of a diagnosis in the record even if made based on genetic testing. No other state has extended GINA-style protection to life/DI/LTC as of Monday's meeting date.

HIFP mitigation posture (ratified 2026-09-07): - Mitigation A — Data-scope architecture. HIFP stores high-fidelity longitudinal data internally; every user-invokable export produces only planning-scenario outputs (numbers, projections, tradeoffs), never raw biomarker/claim rows. Technically enforced, not just contractually promised. - Mitigation B — Contractual + consent firewall. ToS prohibits programmatic (API/webhook) integration by any life/DI/LTC carrier as a HIFP-provided export destination. Per-event affirmative user consent for any manual export. - Mitigation C — Category reshape. HIFP does not name "insurance" as a partner category. HIFP is a Coverage Navigator / Benefits Navigator — user-side advocacy, never a carrier BD channel. - Public posture statement by MVP: "HIFP does not build underwriting-usable exports of your data, and does not partner with life/DI/LTC carriers in any capacity that routes your data toward underwriting decisions. Ever."

Questions for counsel: 1. Does the Florida HB 1189 medical-records carve-out create a residual risk pathway if HIFP outputs are cited in a physician's notes and the carrier obtains the notes through an Attending Physician Statement (APS) request? What contractual protection can we build at the chain-partner (physician) level to mitigate? 2. Are any other states (beyond Florida) close to enacting similar life/DI/LTC genetic-info protections? Any pending legislation we should be tracking? 3. What is counsel's read on the NAIC Model Bulletin on Use of AI Systems by Insurers (2023, adopted by 25 states as of July 2026 including California, Colorado, New York, Texas operating under state-specific frameworks) — does it constrain carriers from using HIFP-shape aggregated data in AI-assisted underwriting even in the 25 non-Florida states that have not extended GINA? 4. How do we structure the standard-of-care disclaimer so HIFP-authored planning outputs cannot be misused as evidence in an underwriting decision, without disclaiming HIFP's positive value?

3.2 · Consumer health data — WA MHMDA + IL GIPA + emerging state statutes

Washington My Health My Data Act (MHMDA) — RCW 19.373. Effective March 31, 2024. Regulates any "regulated entity" that collects "consumer health data" — extremely broad definition covering biometrics, wearable data, health-condition information, mental-health data, precise geolocation to health facilities, and inferences drawn from same. Key requirements: - Consent required for collection beyond what is strictly necessary to provide requested product/service. - Separate and distinct consent required for sharing. - Consumers have right to confirm, access, delete, and appeal. - Private right of action under the Washington Consumer Protection Act (RCW 19.86.090) — statutory damages per violation, class-action mechanics available. - Full 10-section statute: definitions · consumer health data privacy policy · collection or sharing · consumer rights + appeal · data security · processors · valid authorization to sell · geofence restrictions · CPA application · exemptions.

Illinois Genetic Information Privacy Act (GIPA) — 410 ILCS 513. Enacted 1998, amended 2008. Restricts collection, use, and disclosure of genetic information. Key exposure: private right of action with statutory damages of $2,500 (negligent) or $15,000 (intentional/reckless) per violation. Deluge of GIPA class-action litigation against employers and insurers in 2023-2024.

HIFP MVP posture (Red Team T1 mitigation): - Geo-gate WA + IL residents at MVP. No HIFP account creation or Planning-Agent-mediated experience for WA + IL residents at MVP launch. Ship in H1 after 6 months of ex-WA/IL production data proving classifier holds. ~4% TAM reduction; ~85% legal-exposure reduction.

Questions for counsel: 1. Confirm the geo-gating approach as sufficient to avoid MHMDA + GIPA exposure at MVP. Any residual risk from browsing (not account creation) by WA/IL residents? 2. Are other states enacting similar statutes we should be pre-tracking (California + Nevada in particular)? 3. What is the practical enforcement posture in WA + IL through 2026-2027 — is the AG office actively pursuing? 4. Advise on the "consent to collect" vs "separate consent to share" framework — HIFP's onboarding + per-event share-flow design should be counsel-reviewed.

3.3 · HIPAA + Business Associate framework — 45 CFR 164.502(e)

If HIFP integrates with a covered entity (concierge practice, EHR patient-portal via SMART-on-FHIR, individual-access aggregator like b.well), HIFP becomes a business associate.
45 CFR 164.502(e) requires: business associate may use/disclose PHI only as permitted by BAA or as required by law; must not use/disclose in a manner that would violate HIPAA if done by the covered entity.
HIFP's operational HIPAA obligations include: safeguards for e-PHI, incident response, breach notification within 60 days, downstream subcontractor BAAs, restrictions on use/disclosure.

Questions for counsel: 1. BAA template that HIFP can offer standardized to concierge-medicine chain partners + individual-access aggregators (b.well is the current in-flight example). 2. Incident-response + breach-notification workflow that satisfies HIPAA + WA MHMDA + IL GIPA + state breach-notification statutes. 3. How does the coverage-navigator posture (§7.15 ratification) affect HIPAA scope? HIFP is not itself a covered entity, but is a business associate when integrated with one.

3.4 · State-by-state — three-tier regulatory frame (federal / state / zip)

Ratified 2026-09-07: HIFP operates on three regulatory tiers.

Federal: GINA (health insurance + employment) · HIPAA + BAA (§3.3) · SEC advice-boundary posture (see §3.5) · NAIC AI Bulletin (guidance, not federal law).
State: MHMDA (WA) · GIPA (IL) · genetic-info life/LTC/DI (FL) · state insurance-regulatory requirements per line of business · state-specific mandatory-reporter obligations · state-specific privacy statutes (California CCPA/CPRA · Nevada · New York SHIELD).
Zip-code: climate insurability (Gulf Coast + wildfire zones) · Medicaid state-specific rules (if HIFP scales to that market) · property-insurance variance · child-support obligations state-specific.

Question for counsel: Given this three-tier operating reality, what is the minimum state-registration + state-tax posture HIFP must maintain to serve users across all 50 states? Any state where HIFP's model requires state-specific registration (e.g., as a health-information exchange, as a consumer-reporting agency, as a data broker per Vermont / CA / TX registration requirements)?

3.5 · Advice-boundary posture — SEC + state RIA rules

HIFP does not register as an investment advisor (RIA). HIFP does not hold user funds, provide personalized investment advice, or recommend specific securities.
HIFP's Planning Assistant is architecturally constrained to a question-asking posture with a boundary classifier + safety-check + full audit log (see [[HIFP-advice-boundary-spec-v0.1]]).
Adversarial test set (500+ prompts at MVP, target 5K) validates classifier failures.
Full user-facing audit log of every AI response for user transparency + regulatory-inquiry response.

Questions for counsel: 1. Confirm HIFP's Planning Assistant + Plan-Delta + question-asking posture stays outside RIA-registration scope. Any state where the line is drawn differently (Nevada, California)? 2. Confirm HIFP's "share-with-incumbent" model (user shares planning outputs with their advisor; advisor cites in their advice) stays outside RIA scope on the advisor side. 3. SEC precedent on LLM-mediated consumer financial products — thin case law. HIFP wants to avoid becoming the enforcement test case. Advise on posture that stays clearly out-of-scope.

3.6 · Actuarial + longevity modeling

HIFP builds an actuarial model for personalized life-expectancy + care-cost + care-timing projections (see [[HIFP-actuarial-model-spec-v0.1]]).
Uses Society of Actuaries Pri-2012 base mortality tables + MP-2021 improvement scale (with SECURE 2.0 0.78% cap) — current SOA standard for private-employer DB plans.
Health-signal-adjusted mortality/morbidity is a novel-adjacent modeling approach; the specific combination is IP-candidate #2 in the IP assessment.

Question for counsel: HIFP's actuarial outputs are used by users in their planning conversations; not sold as insurance underwriting inputs. Confirm no state actuarial-practice-registration requirement applies. Advise on standard-of-care disclaimer for actuarial-projection outputs.

§4 · Open design questions requiring counsel input

4.1 · Delete-forever vs pause + minimal legal-defense archive

The tension: Fatima leans toward true hard-delete as the trust-brand posture ("if you say deleted, mean it"). Brandon flagged the engineering + legal concern: cannot prove the negative in a post-deletion user claim without some archive.
Ratified 2026-09-07 as open R&D item; decision post-counsel-briefing.
Facebook-style pause + hard-delete option is a candidate middle ground.
Apple privacy policy has been named as the consent-and-control design reference (see §4.4).

Counsel question: What is the minimum legally-defensible archive HIFP must maintain post-user-deletion to respond to litigation or regulatory inquiry — and can that minimum be architected as hashed / anonymized / cryptographically-restricted so it does not undermine the trust-brand promise of deletion?

Users can grant access to spouses, adult children, or designated family members ("household mode" — MVP tile stub + H1 full per §7.6, with standing option to pull into MVP given family-attach is a first-class Employer commercial mechanic).
Question: how do we handle scope of consent when user cannot legally consent (dementia, incapacity), where a designated proxy or POA-holder is exercising rights on behalf of the user.

Users can share planning outputs with their advisor (financial planner, physician, estate planner, CPA) via a share-preview link.
We produce role-aware share views (Estate Planner sees estate view; CPA sees tax view; RIA sees investment view — Ledger §4.14 pending).

Counsel question: Does HIFP incur any professional-obligation exposure by facilitating this share (data-processor obligations, subject-access-request pass-through, or advisor-liability implications)?

Ratified 2026-09-07: Apple's privacy policy is the standard-of-craft consent-and-control reference HIFP designs against. Per-app granularity, device-level control, on-device-key posture.

Counsel question: Any specific Apple-privacy-policy language patterns worth adopting verbatim (with attribution / adaptation)? Or is Apple's language too specific to their device-plus-cloud model to translate?

§5 · Specific contractual instruments HIFP will need

5.1 · Consumer-facing (users)

Terms of Service (ToS)
Privacy Policy
Consent flow language (per-source integration + per-event share)
Delete + export flows (subject-access-request compliance)
Cookie policy (GDPR-adjacent even though US-only at MVP)

5.2 · Investor-facing

Mutual NDA (already surfaced in §2.1 as the immediate blocker)
SAFE agreement (standard YC-form post-money valuation cap with MFN) — need counsel review of the specific instrument HIFP uses
Cap-table + option-pool documentation
Investor-DD data-room framework

5.3 · Employer-buyer contracts

SaaS Master Services Agreement (MSA) template for self-funded employer buyers (Salesforce-shape primary segment)
Per-employee data-processing terms
Breach-notification + audit-cooperation provisions
Broker/consultant channel terms (Mercer / WTW / AON / Alliant / Gallagher)

5.4 · Chain-partner contracts (concierge practices — currently watch-list per §7.14 reshape)

Practice-partner MSA + BAA
Physician-partner APS-hygiene protocol — physicians receiving HIFP outputs into clinical notes must be contractually restricted from citing HIFP data in APS responses to life/DI/LTC carriers
Practice-branded appearance license (POC demonstrated 2026-09-04)

5.5 · Data-source-partner contracts (aggregators + wearables + clinical channels)

Kubera (in flight per [[hifp-partner-pipeline]] as H1)
Empower (H2)
Oura + Whoop + Dexcom + Apple Health + Google Fit (POC-live)
b.well (in flight; individual-access aggregator)
Standard: HIFP consumes; no re-sale of HIFP data downstream

5.6 · Employee + contractor

IP-assignment agreements (retroactive audit required for existing arrangements)
Non-solicit + confidentiality
Founding-eng offer letter with equity terms

§6 · Commercial context counsel should know

Primary buyer segment: Self-funded employers with long-term-equity plans (Salesforce-shape). Employer variant exploration open (self-funded without pension, mid-market self-funded, government self-insurers, union benefit trusts, PEOs as channel).
Partner categories (parallel tracks under consent-first umbrella): Financial data aggregators · Wearable/device providers · Diagnostic + longevity data providers · Clinical data channels (SMART-on-FHIR + individual-access aggregators) · Consumer-Wellness Partnerships (Function + Superpower + Prenuvo + Neko + Levels + Aura — the concierge segment reshape). Insurance carriers explicitly not a partner category — HIFP is Coverage Navigator on user-side.
Direct-to-consumer: parallel-for-MVP as trust and viral surface; not the near-term revenue engine.

§7 · Sequencing counsel should understand

Nothing external happens until this sequence:

NDA template in hand (§2.1) — from Karen, this week.
v4 canonical set produced — Brandon owns, ~1 week.
IP counsel engaged + provisional filings in flight (§2.6) — begins this week.
Karen legal briefing + written summary — the risk register we walk out of the Karen conversation with becomes the punch-list for v0.1 → v0.2 of the Ethical Framework + ToS + Privacy Policy + all the templates in §5.
Market-signal lunches begin (Peter first, NDA-covered).
v4 kit + provisional filings + Kristen Valdes consent-model consultation land in parallel.
Funding conversations open.

§8 · Verified factual context (for counsel reference)

Numbers cited in the trio's materials that have been verified against public sources as of 2026-09-07:

Function Health: $2.5B post-money valuation, $298M Series B led by Redpoint (Nov 2025); ~350K members; annual pricing dropped $499 → $365; launched 2023.
MDVIP: ~450K members; 1,300–1,400 affiliated physicians; PE-owned; expanding into specialty care.
Forward Health: SHUT DOWN November 2024 after burning ~$657M. No longer a live comp or chain-anchor candidate.
One Medical (Amazon acquisition): $99/yr Amazon Prime membership tier; up to 6 memberships per Prime account. No separate "Premium" concierge tier at the Amazon-Prime-benefit level.
Neko Health: $700M Series C (Lightspeed + O.G. Ventures led, July 2026); NYC-first US launch; 2,000+ high-resolution skin images per scan (correcting Sindhu's "~400" verbal memory); ~60-min visit with clinician consultation.
Aura / Oura: Filed S-1 September 3, 2026 (confidential filing May 21); listing on Nasdaq under OURA; ~$11–16B valuation range; ~5M members; ~$1.4B TTM revenue. IPO led by Goldman + Morgan Stanley + JPMorgan.
Fidelity 2026 Retiree Healthcare Estimate: $185,500 per 65-year-old individual; $371,000 per married couple. Up 7.5% YoY.
Genworth / CareScout 2025 Cost of Care Survey: Assisted living $6,200/mo ($74.4K/yr) · Nursing home $9,581/mo semi-private / $10,798/mo private · Non-medical home care $35/hr ($80K/yr at 44 hr/wk).
Boldin (retirement-planning comp): PlannerPlus $144/yr (new-subscriber price, up from $120); Advisors tier $2,800/yr.
John Hancock Vitality (wearable-tied life insurance): Active 10+ years. GO tier included with policies; PLUS tier eligible for up to 25% premium savings tied to wellness engagement.
Galleri (Grail multi-cancer early detection): Nancy Gardner Sewell Medicare MCED Coverage Act enacted February 3, 2026; reimbursement begins 2028. Priority Health MA plan covers with copay January 2026 (earliest MA adoption).
Lumiant / HALO wealth platform: ~12 employees May 2026; $2.4M revenue; Sydney HQ; $9M total funding across 4 rounds. Distressed (consistent with prior HIFP memory as tuck-in target rather than competitor).
SOA Pri-2012 mortality table: Still current standard for US private-employer DB plans; combined with MP-2021 mortality improvement scale (SECURE 2.0 0.78%-cap applied).
Current Anthropic production models: Claude Fable 5.1 (Sept 1, 2026) · Opus 5 · Sonnet 5 · Haiku 4.5. Available via Claude API.

Not yet verified — human web-access pass owed: - Maxwell v. Amazon (2:25-cv-261) — WA MHMDA test case status via PACER - OpenAI + Google Gemini AUP explicit approval of health-decision-support use case - Executive Health Group current patient count - HRS-Medicare Data Use Agreement current cost + timeline - SOC 2 Trust Service Criteria current version

§9 · What Karen (or counsel) should walk out with clarity on

Adopt HIFP's mission-level User Primacy commitment as the interpretive lens for every downstream question.
Confirm the underwriting-firewall posture (§3.1 + judo memo) is legally defensible + operationally implementable.
Draft or refer standard mutual NDA template — this week.
Scope ToS + Privacy Policy drafting engagement — 4–6 week timeline.
Referral to IP counsel (Wilson Sonsini / Cooley / Fenwick / Fish & Richardson) — this week.
Referral to specialty insurance broker for E&O + D&O + cyber binding — pre-SAFE-close.
Draft standard-of-care disclaimer framework for planning outputs — 2-week turnaround.
Confirm HIFP stays out of RIA-registration scope in current design; flag any state-specific exceptions.
Confirm geo-gating (WA + IL exclusion at MVP) is sufficient posture.
Design opinion on delete-forever vs pause+archive (§4.1) — informs product design decisions.

End of briefing. Companion artifacts: [[HIFP-life-insurance-judo-memo-v0.1]] for the deep-dive on the underwriting-firewall analysis; [[HIFP-ethical-framework-v0.1-skeleton]] for the mission-level commitments this briefing operationalizes; [[HIFP-session-notes-2026-09-07-alignment]] for the founder-team decisions this briefing depends on.