Compliance at SaidText
SaidText is an operational data infrastructure designed to support industrial safety, compliance, and operational processes. Responsibility for regulatory compliance, workplace safety, and operational decisions remains with the employer.
GDPR Posture for EU Operators
SaidText processes operator voice data as a data processor on behalf of the customer (data controller). For EU-based deployments, all processing activities are governed by a Data Processing Agreement (DPA) that outlines lawful bases, data categories, retention periods, and sub-processor disclosures in accordance with GDPR Articles 28 and 30.
Voice recordings are processed solely for the purpose of generating structured operational tickets. Personal data is minimized by design: operator names are associated with tickets only when the customer's configuration requires attribution for safety or compliance purposes.
Data subject access requests (DSARs) and deletion requests are supported through the platform's administrative interface. Enterprise customers can configure data residency preferences where supported by the underlying cloud infrastructure.
OSHA 300/301 Record-Keeping Support
SaidText supports U.S. manufacturing facilities in maintaining structured records that align with OSHA Form 300 (Log of Work-Related Injuries and Illnesses) and Form 301 (Injury and Illness Incident Report) requirements. The platform captures timestamped, attributed operational data that can serve as source documentation for these records.
Structured tickets generated from voice reports include fields for incident type, location, personnel involved, and corrective actions taken. These records are retained for a minimum of five years in accordance with OSHA's record-keeping mandate under 29 CFR 1904.
SaidText does not replace the employer's obligation to complete and submit OSHA forms. It provides the underlying data infrastructure to make that process faster, more accurate, and fully traceable.
HIPAA Posture for Healthcare Manufacturing
SaidText is not currently marketed as a HIPAA-compliant platform. In healthcare manufacturing scenarios where Protected Health Information (PHI) may be present in operational voice data, customers should evaluate whether a Business Associate Agreement (BAA) is required based on the nature of the data captured.
For organizations operating in FDA-regulated or healthcare-adjacent manufacturing environments, SaidText can be configured to minimize the capture of PHI through custom vocabulary filters and field-level access restrictions. HIPAA compliance readiness is planned as part of our enterprise roadmap. Please contact us through our contact form for current status.
Industry Certifications
SOC 2 (framework in progress). This audit evaluates the platform's controls for security, availability, and confidentiality. Upon completion, the report will be available to enterprise customers and prospects under NDA.
ISO 27001 certification is planned as a subsequent milestone in our security program. The information security management system (ISMS) framework is being developed in parallel to ensure alignment across both standards.
SaidText does not currently hold FDA, FSMA, or API certifications. For customers in food manufacturing, oil and gas, or other sector-specific regulatory environments, the platform is designed to support compliance workflows without itself being a certified system of record. Customers retain full responsibility for regulatory submissions.
Sub-Processors and Third-Party Services
SaidText relies on a limited set of third-party sub-processors to deliver platform functionality. Each sub-processor is evaluated for security posture and bound by contractual data protection obligations.
- Amazon Web Services (AWS) - Cloud infrastructure, compute, and encrypted storage services.
- Stripe - Payment processing for subscription billing. Stripe is PCI DSS Level 1 certified.
A complete and current sub-processor list is maintained and made available to customers as part of the Data Processing Agreement. Changes to the sub-processor list are communicated to customers with reasonable advance notice. For questions, contact us through our contact form.
Latest Insights
Expert perspectives on industrial AI and operational intelligence

Line-Side Material Calls: Why the Call Button Wastes Forklift Trips
A call button tells the forklift driver that a station needs something, not what. Here is what a useful material call contains, and five steps to fix it without a big project.

Downtime Report Form: A Free Template and How to Get It Filled In
A downtime report form should capture which asset stopped, when, what the operator saw, what was tried, the likely cause and what the next shift needs to know. Here is a free template.

Tools for Automated OSHA Reporting: What to Look For
Automated OSHA reporting tools help most at the first report and in keeping a complete record trail. Here is what to look for, and why no tool makes a plant compliant on its own.
