Security Built for Manufacturing

Understand how your quality information is accessed and processed

Your PPAP submissions, engineering drawings, and process data represent critical intellectual property. QualityEngineer.ai combines organization workspaces, role-based access and document workflows. Use the details below to review those features against your data and customer requirements.

  • Organization Workspaces
  • Role-Based Access
  • AI Data Handling
  • Security Review

Review Your Security Requirements

Start with the workflow, the information it will process and the people who need access. A review can then identify the applicable application controls, provider terms and evidence your organization needs before using the service for that scope.

  • Define permitted document types, data classifications and sharing boundaries
  • Identify users, administrators, service access and supplier or customer portal access
  • Trace application, file-storage and AI processing paths, including regions and retention
  • Verify the relevant access settings and recovery procedures for the proposed workflow
  • Review provider agreements, responsibilities and any required incident-notification terms
  • Confirm the exact reports or other evidence required by your customer

Use synthetic or public examples while the permitted data and handling requirements are being agreed.

Data Protection and Encryption

Encryption at Rest

Cloud file uploads support private object access and AES-256 server-side encryption. Storage and encryption requirements are part of the deployment review.

Encryption in Transit

HTTPS protects browser and API traffic in transit, including requests to the commercial AI processing provider.

Organization-Scoped Isolation

Organization identifiers scope application records and queries, with membership and roles used to authorize workflows.

Authentication and Access Control

Short-lived tokens, role-based permissions and TOTP multi-factor enrollment and recovery support user access. Organization settings and service-access policies determine MFA requirements.

Secure File Storage

File workflows support private objects, authenticated delivery and signed links. Portal access uses links scoped to the relevant workflow and records.

Team and Portal Access

Team roles and scoped portal links support collaboration with employees, customers and suppliers without giving every participant the same access.

AI Data Handling

We understand that sending quality documents to an AI system raises legitimate concerns. Training, provider retention and model tenancy are separate questions. The following describes Claude-based features and the provider policies that apply to direct Anthropic API use.

  • Claude-based evaluation and generation send selected document content and context through a configured commercial API. The data sent depends on the feature you choose.
  • Anthropic states that commercial inputs and outputs are not used for model training by default. Opt-in and feedback exceptions apply. Read its commercial training policy.
  • Anthropic's standard API policy deletes inputs and outputs within 30 days, with exceptions for certain features and models, agreed terms, policy enforcement and law. Read its retention policy.
  • Organization scoping controls application access. Dedicated model tenancy, dedicated hosting and account-specific retention are separate arrangements to review with the relevant providers.
  • AI-generated outputs are saved in the application for your team to review. Application retention is described in our privacy policy.

How AI processing works

  1. 1You upload a document
  2. 2Document is sent via encrypted API call
  3. 3Review the result; provider retention terms still apply

AI Transparency and Human Review

Decision support. QualityEngineer.ai uses AI to assist quality work. Your organization determines the applicable program requirements and approval process.

What our AI does. Depending on the feature you are using, our AI can read engineering drawings and documents and extract characteristics, dimensions, and requirements for your review; draft and help structure quality work such as PPAP and PSW packages, CAPA and root-cause analysis, APQP planning, supplier reviews, and inspection and study summaries; coach you through a method such as a root-cause investigation by asking questions and checking your work against the standard; answer questions about using QualityEngineer.ai; and check a package for completeness so you can fix gaps before you submit.

A human is accountable for every output. Our AI drafts, analyzes, checks, and suggests. Review its output before using it in a quality record, approval or customer submission. A qualified person on your team remains responsible for the accuracy and suitability of the work and for your organization's approval decisions.

How we identify AI content. AI features and saved outputs can include AI labels and model or generation metadata. Review the available source information alongside the output for the workflow you are using.

Data handling. The selected feature determines the content sent for processing. Provider training policy, retention, application access and model tenancy are different controls. See the AI Data Handling section on this page.

A control for data-sensitive work. Agree which features may process your material and which work should remain manual before starting a data-sensitive workflow.

Questions. Questions about AI features and their data handling can be sent to dan@qualityengineer.ai.

Infrastructure Security

Cloud Hosting

The application uses cloud infrastructure with organization workspaces. Hosting requirements can be reviewed alongside application, file-storage and AI processing paths.

Container Isolation

The application, background workers and supporting services are packaged as separate Docker containers.

Automated Backups

Deployment procedures cover database backups, retention cleanup and restoration. Recovery objectives and validation belong in the agreed service scope.

Security Updates

Dependency update checks and code review support the release and maintenance workflow.

Application Rate Limits

Application request limits help control automated abuse and protect service resources.

Monitoring and Alerting

Service health checks and error reporting provide operational visibility. Escalation owners and response responsibilities are part of the service review.

Privacy and Compliance

Privacy Requests

  • Review the data collected and processed in our privacy policy
  • Request access, corrections or deletion through the privacy contact
  • Export supported records using the formats available in the relevant workflow
  • Confirm application, provider and backup retention separately
  • Agree any program-specific processing requirements before use

Assurance Evidence

  • Request any applicable independent reports and their exact scope, date and offering
  • Distinguish provider infrastructure evidence from QE application evidence
  • Review actual provider terms and any proposed data processing agreement
  • Confirm required controls against the intended workflow and deployment
  • Agree customer, QE and provider responsibilities before relying on them

For SOC 2, ISO 27001, TISAX or other assurance requirements, request applicable reports and confirm the covered offering, scope and date.

Industry-Specific Security

We built QualityEngineer.ai for manufacturing industries with strict data security requirements. That means we understand the unique needs that come with handling engineering drawings, PPAP submissions, process data, and supplier communications across automotive, aerospace, medical device, and general manufacturing.

Engineering Drawing Protection

Drawing workflows associate files and extracted information with organization records. AI analysis sends selected content to the processing provider. Review the file-delivery, sharing and AI paths together for your intended use.

PPAP Document Confidentiality

PPAP submissions contain proprietary process parameters, capability data, and supplier information. Organization records, team roles and sharing settings help manage the workflow. Confirm the permitted data and delivery path before distributing a package.

Supplier Portal Security

The supplier portal uses secure, time-limited access tokens for document uploads. Suppliers do not need to create accounts or share credentials. Each portal link is scoped to a specific PPAP request with controlled access.

Audit Trail for Compliance

Workflow history can record document changes, evaluation results and status updates with timestamps and user attribution. Coverage varies by action; verify the required events and retention for your audit scope.

Questions About Security?

We welcome security reviews and are happy to provide additional documentation, data processing agreements, or arrange a call to discuss your organization's specific requirements.

Request a security whitepaper, data processing agreement, or schedule a security review by emailing security@qualityengineer.ai