Swift Ops logoSwift OpsVideo to Intelligence
Legal

Privacy Policy

Last updated: July 15, 2026

This policy explains how Swift Ops processes, stores, and protects customer information used to generate standard work and related documentation.

Legal page for Swift Ops public site

Legal record

Status
Public
Updated
July 15, 2026
Access
Website
Support
Email

This Privacy Policy explains how Swift Ops collects, uses, and protects information processed through our manufacturing documentation service.

1. Information We Process

  • Account information (name, email, company name).
  • Uploaded video and audio content, including tool usage and operational steps.
  • Customer-created templates and template inputs.
  • Derived data, including frames, transcripts, generated standard work outputs, digital work instruction content, translations, and changeover outputs.
  • Usage and operational metadata (job IDs, timestamps, processing logs).

2. How We Use Information

We use information to provide the service, generate outputs requested by customers, secure the platform, maintain reliability, manage accounts and billing, enforce usage limits, and provide customer-authorized support. We do not sell customer data. Swift Ops does not use customer videos, transcripts, images, customer-created templates, or generated outputs to train its own AI models.

3. Data Sharing

We share data only with subprocessors necessary to operate Swift Ops, such as cloud infrastructure, model providers, storage providers, payment providers, analytics providers, and support tools used to deliver the service. We do not share customer content with third parties for advertising. Model providers process content under their applicable API terms and account settings; Swift Ops does not knowingly opt customer content into model training. Swift Ops personnel may review customer content only when the customer explicitly authorizes support access for a specific request, access is reasonably necessary to investigate security, abuse, billing, or reliability issues, or we are legally required to do so. Subprocessor access is governed by the applicable provider terms and controls.

4. Data Retention

Source videos are scheduled for deletion 24 hours after processing completes or fails unless the customer selected source retention and the account has the required active subscription and active module or storage access. Uploaded files that never start processing are scheduled for deletion 24 hours after the job is created, and empty upload reservations expire after one hour.

Generated outputs for free accounts are retained for 30 days. When subscription access lapses without storage access, retained source videos and generated outputs are scheduled for deletion after 45 days. Generated outputs remain available while an active module or storage subscription provides storage access.

Customers can also request deletion where product controls make deletion available. A completed deletion workflow removes covered content from active application records. Cloud-provider soft-deleted recovery copies may remain for up to seven additional days, and limited operational, security, fraud-prevention, billing, or legally required records may remain as permitted by law. Swift Ops does not claim a separate customer-content backup-retention schedule beyond this provider-managed recovery window. Before applying the updated policy to eligible existing company data, Swift Ops provides a separate seven-day notice so authorized users can review or export records.

5. Security

We use encryption in transit and at rest, access controls, audit events, and company-scoped authorization in the application. Infrastructure and provider controls are reviewed separately. No system can guarantee absolute security.

6. Your Responsibilities

You are responsible for ensuring you have the right to upload and process any content. Avoid uploading unnecessary personal identifiers, faces, badges, customer paperwork, regulated data, or confidential labels when they are not needed for the instruction.

7. International Transfers

Swift Ops currently uses U.S.-based primary application storage and compute for customer process data and generated documentation workflows. Model-provider and other subprocessor processing, support, billing, security, or operational records may occur wherever the relevant provider infrastructure or personnel operate. We apply contractual and technical protections appropriate to those data paths.

8. Updates

We may update this Privacy Policy. Continued use after changes become effective indicates acceptance.

9. Contact

Questions can be sent to security@tryswift.net.