Access and identity
Use IRONKEEP MFA or your identity provider through SAML or OIDC, with SCIM for user lifecycle control.
Healthcare & HIPAA
IRONKEEP gives business associates and healthcare teams one place for mail, files, docs, chat, and meetings, with BAA-scoped onboarding where required.
Workspace flow
Each product covers one part of the workflow while identity, audit, retention, legal hold, and recovery stay shared.
Keep ePHI in email, calendar, and contacts without moving between vendors.
Store and share healthcare files with scoped access and recoverable history.
Co-edit policies, reports, spreadsheets, and presentations inside the workspace.
Keep operational conversations and attachments inside the same governed scope.
Run invite-only calls and screen sharing without opening another collaboration boundary.
Security for ePHI
IRONKEEP keeps access, audit, retention, recovery, and organization separation consistent across the suite. Your organization still owns its HIPAA policies, risk analysis, training, and configuration.
Use IRONKEEP MFA or your identity provider through SAML or OIDC, with SCIM for user lifecycle control.
Sanitized events across mail, files, docs, chat, and meetings support review and scoped export.
Apply retention settings and legal holds, then recover earlier versions when records change.
Organization data stays tenant-isolated with scoped keys, and IRONKEEP staff cannot read decrypted tenant content.
Implementation path
Scope ePHI workflows.
Decide which teams, mailboxes, folders, docs, chat channels, and meetings may contain ePHI.
Import email and files.
Execute the BAA where required, then bring the agreed domain, users, mailboxes, files, and protected work into IRONKEEP.
Set controls and evidence.
Use identity, audit logs, retention settings, legal holds, and exports to support your compliance workflow.
Who it's for
Business associates with shared evidence needs.
A billing, analytics, consulting, IT, or operations vendor needs BAA-scoped collaboration without scattering records across disconnected tools.
Covered entities coordinating outside the EHR.
A clinic, provider group, or health plan needs secure mail, files, docs, chat, and meetings for work that may contain ePHI.
Healthcare teams cleaning up tool sprawl.
Email in one place, files in another, chat somewhere else. IRONKEEP brings the workflow into one governed suite.
FAQ
Yes. If IRONKEEP creates, receives, maintains, or transmits ePHI for your organization, we sign a BAA during onboarding.
No. Your organization owns HIPAA compliance, policies, training, risk analysis, record schedules, and legal review. IRONKEEP provides secure collaboration, access control, audit, retention, legal hold, and export tooling to support those workflows.
Customer data is hosted in the United States. Tenant-scoped encryption keys and tenant isolation keep organizations separate and prevent routine operator access to tenant content.
No. HHS says the HIPAA Privacy Rule does not set a medical-record retention period. State law and organization policy usually drive medical-record schedules, while HIPAA does require certain required documentation to be retained for six years.
IRONKEEP supports configurable retention, matter-based legal holds, deletion blocks for held records, audit trails, and scoped exports for compliance or legal review.
No. Zero operator access to tenant content is enforced by explicit deny rules on decrypt operations. IRONKEEP staff cannot read decrypted tenant content, run tenant decrypt operations, create product users, or generate tenant search tokens.
Healthcare & HIPAA
Tell us where to follow up about your ePHI workflow, BAA needs, retention requirements, and deployment fit.
Private beta
Choose the regulated workflow you want to scope.
Enter your email to start scoping the healthcare workflow.
Enter your email to request a defense pilot and open the CMMC readiness checklist.