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.
Ironhold is designed to operate in high-trust, compliance-driven environments. Security, access control, and data integrity are foundational - not afterthoughts.
Operational proof is only useful if the system behind it enforces clear boundaries, traceability, and disciplined handling of evidence data.
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.
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.
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.
Application infrastructure is hosted in the United States. All operational data remains within US-based data centers.
Access is constrained by role, organization, and facility scope so the system reflects the separation of duties required in contractor and government workflows.
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.
Users can only access data within their assigned organization and facility. Cross-organization data access is architecturally prevented, not just policy-restricted.
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.
Ironhold is structured to support audit review, performance disputes, and routine compliance oversight without forcing teams to reconstruct proof after the fact.
All significant actions - task completions, status changes, evidence uploads, excuse submissions, and administrative changes - are logged with timestamps and user attribution.
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.
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.
We're actively working toward these milestones as we scale.