← Trust / HIPAA

HIPAA — protected health information stays on your box.

RailCall's execution model is 127.0.0.1 — the runtime that reads, transforms, and signs PHI runs on the customer's own perimeter. In most deployments RailCall is not a business associate at all under 45 CFR § 160.103 because we never receive PHI. When we do (Enterprise tier with hosted receipt vault), we sign a BAA.

The one-sentence answer

RailCall's local-first + cryptographic-receipt model is the answer to the two things a Covered Entity's legal team actually worries about — data disclosure to a third-party processor and proving what an AI agent did with a patient record. We don't hold the data; we cryptographically prove the actions.

Is RailCall a Business Associate for your deployment?

Q — Default deployment (Studio on 127.0.0.1, receipts stored locally)?
A — No. RailCall receives no PHI. The workflow that touches a patient record runs on your machine, calls your EHR/CRM's endpoint directly, and writes a signed receipt to your local disk. No BAA needed because you never disclosed anything to us.
Q — Team tier with the enterprise-hosted receipt vault?
A — Yes, and we sign a BAA. If you stream Ed25519-signed receipts up to our hosted vault for centralized audit, RailCall becomes a business associate under 45 CFR § 160.103. We sign a BAA aligned to § 164.504(e)(2)(ii) at contract time.
Q — AI Studio / MCP tools that RailCall bundles?
A — Not by us. Third-party LLM providers (Anthropic, OpenAI) are their own business associates; you'd sign a BAA directly with them. Our Studio integrates via BYOK — the key is yours, the traffic goes straight from your box to your model provider, we're not in the middle.

§164.312 Technical Safeguards — how they map to what RailCall actually does

§164.312(a) Access control
Loopback-only Studio (127.0.0.1) + per-user session token + role-based admin on any org surface. No PHI ever routes through RailCall infrastructure by default.
§164.312(b) Audit controls
Every action against protected data emits an Ed25519-signed receipt: command, inputs hash, output hash, actor pubkey, timestamp. Receipts hash-chain per install so tampering is detectable. Verifiable offline forever.
§164.312(c) Integrity
All governed workflows + modules are signed by their publisher; loader refuses any bundle whose bytes don't match the signature. Receipts cover both the request AND the response body hash — a modified response after the fact fails verify.
§164.312(d) Person or entity authentication
Multi-factor authentication supported on the marketplace side; per-install cryptographic identity (Ed25519 pubkey) on the local station. Airlock actions require an out-of-band approval token distinct from the browser session — a compromised browser cannot approve its own sends.
§164.312(e) Transmission security
Zero required outbound to RailCall infrastructure — the station operates fully offline. When a workflow reaches an external provider, credentials come from the local vault (0600) and the transport is TLS to the provider's own endpoint. RailCall never intermediates.

Evidence + documentation

  • Security Risk Analysis — adopted 2026-07-21; refreshed on any material change. Reviewed on request under NDA.
  • 66-page compliance evidence package — controls matrix, incident-response plan, data-flow diagrams, subprocessor list. NDA-gated. See the Trust page for the request path.
  • Sample signed receipt — see the docs for the receipt shape; every action against PHI in a real deployment emits one of these. Verifiable offline with railcall verify.
  • BAA template — aligned to 45 CFR § 164.504(e)(2)(ii). Sent on request under NDA.

Incident + breach notification

When RailCall is a business associate (Enterprise tier), our breach-notification path meets § 164.410: notice to the Covered Entity without unreasonable delay and no later than 60 days after discovery, with the information § 164.410(c) requires. Because our attack surface is the receipt vault (not PHI itself), most incidents would be metadata-level; PHI stays in the customer's perimeter across every plausible incident class.

Request the BAA + compliance bundle

NDA-gated; sales replies with the mutual NDA + the full documentation set. Reviews from healthcare security teams get priority routing.

Request BAA + evidence bundle