Trust · Transparency Report
Government requests. Breaches. Uptime. AI overrides.
Once a quarter we publish, in plain language, every government data request received, every notifiable breach disclosed, every clinical AI model override, every content-moderation action taken on social.conceptualhealth, and the platform-wide uptime number. The cadence is non-negotiable: 30 days post-quarter-end, SHA-256 hashed, Ed25519-signed by the Privacy Officer, anchored to chain.conceptualhealth.com. Published quarters are never re-written; corrections are appended with a separate hash.
Phase 1 honesty banner
Pre-launch. Zero events. That's the entire report.
We are pre-launch. The first four sections of this report — government requests, breaches, uptime, AI overrides — are intentionally zero because there has been nothing to report. We could have waited until after launch to publish the page; we chose to publish the zero-state so the format, the cadence, the signatures, and the archive procedure are all locked in before there's ever a non-zero number to disclose. Section §05 (Bug Mining) is the first production surface and is non-zero today.
§01 · Government requests
Subpoenas, court orders, warrants, NSLs.
Forward-looking commitment: when this surface is non-zero, we publish the count, the jurisdiction (without case identifier), the data category requested, and whether the user was notified — subject only to a court-ordered gag where one exists, in which case the row will indicate "notification gagged" rather than the user count.
§02 · Breach log
HIPAA-notifiable. Non-notifiable. All-time.
HIPAA-notifiable breaches involving 500 or more individuals are also reported to HHS Office for Civil Rights and listed in the public OCR breach portal. We publish here regardless of OCR posting timeline. Non-notifiable incidents (≤ 500 individuals, contained scope) are still logged on this page with a brief description and the mitigation taken.
§03 · Platform uptime
Per-system, calendar quarter, 99.95% target.
Pre-launch: N/A. The uptime measurement begins the day the first paying clinic comes online. Per-system uptime is published live at status.conceptualhealth.com and aggregated quarterly here. The corporate SLA target is 99.95% across the patient surface, with clinical-critical surfaces (EHR, prescribing, lab orders) held to a separate 99.99% target.
§04 · AI overrides
Clinical AI suggestions overridden by a licensed clinician.
The clinical AI stack (GuardianOrb + BGE-large embeddings + Qwen2.5-7B local model) is in pre-launch validation with a physician-reviewer queue. Every clinical suggestion is logged with the model version, the input context (PHI-redacted), the suggestion, the clinician action (accept / modify / override), and the rationale on override. The override rate is published here quarterly; a high override rate on any model version flags it for retraining or rollback.
§05 · Bug Mining Program — Q2 2026
First non-zero surface. Treasury, payouts, lifecycle.
The Bug Mining Program shipped 2026-05-16 with a 5,000,000 HCC pre-funded treasury under 3-of-5 board-signed multi-sig (see the program page for governance detail). Q2 2026 metrics: 1 critical, 3 high, 3 medium, 2 informational finds paid out — totaling 16,850 HCC (0.34% of the seed treasury). Median triage time was 41 hours against a 72-hour SLA. 7 issues are currently in lifecycle. 0 payouts forfeited to OFAC sanctions. 0 KYC failures. 0 severity disputes escalated. 6 issues from Q1 2026 passed the 90-day disclosure window and are now public on the program page.
How we publish
Cadence, signatures, archive.
Cadence. 30 days post-quarter-end. Q1 in late April, Q2 in late July, Q3 in late October, Q4 in late January.
Signature. Each quarter's snapshot is SHA-256 hashed and Ed25519-signed by the Privacy Officer. The hash is anchored as a transparency-event entry on chain.conceptualhealth.com. The Privacy Officer's Ed25519 public key is published on this page and fingerprinted on the bug-bounty PGP page.
Archive. Past quarters live at /trust/transparency-report/archive/. We do not re-write published quarters; corrections are appended with a separate hash and a brief note describing what changed and why.