SECURITY & TRUST

Built for environments where accountability matters

Ironhold is designed to operate in high-trust, compliance-driven environments. Security, access control, and data integrity are foundational - not afterthoughts.

Designed to preserve separation, evidence, and control

Operational proof is only useful if the system behind it enforces clear boundaries, traceability, and disciplined handling of evidence data.

Multi-Tenant Isolation

Every organization's data is scoped and isolated at the database level. Facility records, task completions, evidence, and user data are never co-mingled across organizations.

Evidence Integrity

Cleaning events are captured with immutable timestamps, GPS coordinates, and photo evidence. Once submitted, records cannot be altered or deleted by users - creating a tamper-resistant audit trail.

Encryption

Data is encrypted in transit (TLS 1.2+) and at rest. Evidence files and operational data are stored in encrypted cloud storage with access controlled by application-layer permissions.

Data Residency

Application infrastructure is hosted in the United States. All operational data remains within US-based data centers.

Permissions aligned to operational responsibility

Access is constrained by role, organization, and facility scope so the system reflects the separation of duties required in contractor and government workflows.

Role-Based Permissions

Every user is assigned a role - Worker, Supervisor, Administrator, or Government Viewer - with permissions scoped to their responsibilities. Workers see their shift tasks. Supervisors see facility operations. Government viewers get read-only compliance access.

Organization-Scoped Access

Users can only access data within their assigned organization and facility. Cross-organization data access is architecturally prevented, not just policy-restricted.

Government Viewer Separation

COR and contracting officer accounts are read-only by design. They can view compliance dashboards, evidence records, and audit exports without the ability to modify contractor operational data.

Evidence that stands up to external review

Ironhold is structured to support audit review, performance disputes, and routine compliance oversight without forcing teams to reconstruct proof after the fact.

Audit Logging

All significant actions - task completions, status changes, evidence uploads, excuse submissions, and administrative changes - are logged with timestamps and user attribution.

Exportable Records

Compliance reports, cleaning event histories, evidence packages, and incident logs can be exported as CSV or PDF for external audit, CPARS documentation, or legal review.

QASP Alignment

Ironhold's evidence model - timestamped completions, photo documentation, GPS verification, and observation scoring - is designed to align with Quality Assurance Surveillance Plan requirements for performance-based service contracts.

Security milestones on the roadmap

We're actively working toward these milestones as we scale.

SOC 2 Type II certification

Planned

FedRAMP readiness assessment

Evaluating

SSO / SAML integration

In development

On-premise / air-gapped deployment option

Planned

CAC / PIV authentication support

Evaluating

If you're evaluating Ironhold for use in a controlled environment, we're happy to discuss our architecture, data handling, and compliance posture in detail.