Security and trust
SeaShell documents what the product controls, what your team controls, and what has not been independently attested. Every claim on this page is scoped to a named operating mode.
Evidence reviewed 2026-08-03
Verified product controls
When SeaShell runs with seashell --offline or SEASHELL_OFFLINE=1, it blocks network traffic except the configured model endpoint and local services.
The boundary is covered by egress, session-wire, and choke-point tests in the SeaShell product repository.
Review documentationseashell models --local probes Ollama on port 11434 and LM Studio on port 1234, then registers discovered chat models.
Local provider construction and discovery behavior have automated repository tests.
Review documentationSeaShell supports allow, ask, and deny decisions for tool actions. Teams remain responsible for selecting rules that match each repository and workflow.
Permission configuration and review behavior are documented in the product documentation.
Review documentationSeaShell telemetry events use a fixed field allowlist that excludes prompts, code, file paths, file names, repository names, and error messages.
Producer-side schema tests reject disallowed fields before an event can be emitted.
Review documentationDeployment boundaries
Local model endpoint and local services
Use a local runtime with SeaShell offline mode when the workflow must prevent other outbound SeaShell network traffic.
Customer-approved network endpoint
Point SeaShell at an approved OpenAI-compatible model service and apply the organization's network, identity, logging, and retention controls.
Selected third-party provider
Provider calls cross that provider's boundary. Review the provider contract, retention behavior, region, and data policy before using sensitive repositories.
Assurance posture
Independent SOC 2 work is deferred while the company establishes budget and operational readiness.
HHS does not issue a HIPAA compliance certificate for software products. Deployment, access to PHI, contracts, and customer safeguards determine the applicable obligations.
SeaShell has not published a blanket PHI-handling commitment. Buyers should confirm the exact data flow and whether Syntora-operated services receive, maintain, or transmit PHI.
Integration support and vendor recognition are tracked separately. Test-backed does not mean certified, endorsed, or listed by a vendor.
Reviewer packet
Security FAQ
No. SeaShell does not currently claim a SOC 2 report. The security program is documenting controls and evidence first, with independent assurance deferred until budget and readiness support it.
No such claim is made. HHS does not issue a HIPAA compliance certificate for products. A customer must evaluate its deployment, data flow, safeguards, contracts, and legal role.
Not by itself. Run SeaShell in offline mode and verify every configured model endpoint, MCP server, plugin, provider key, and local service against the intended boundary.
Email contact@seashell.sh with a clear description, affected version, reproduction steps, and impact. Do not include live credentials, PHI, or customer secrets.