Trust, Security & Compliance

One World Lingo is designed for privacy-first transcription and translation with clear operating modes, conservative public claims, contract-ready buyer posture, and deployment choices that support both managed SaaS use and higher-control self-hosted evaluation paths.

No adsMinimal dataEU-designated strict modeContract-ready
Hosted modes
EU-only (Strict) and Global
Core privacy posture
No ads • minimal data • no public-model training on customer content
Deployment paths
Managed SaaS and BYOK / self-hosted evaluation path
Buyer readiness
MSA, DPA, procurement-aware trust posture
Clear operating modes

Choose between EU-only (Strict) and Global based on your handling, routing, and operational requirements.

Privacy-first design

We do not run ads, do not sell personal data, and do not use customer content to train public models.

Flexible deployment

Use the managed SaaS platform or evaluate BYOK / self-hosted deployment options where appropriate.

1) Hosted operating modes

EU-only (Strict)

Designed for customers who want stricter regional handling in the hosted product. For transcription, OWL uses its EU-designated Azure Speech route in West Europe. For translation, OWL uses its EU-designated translation operating path.

Global

Designed for customers who want a separate global operating path for core processing and broader operational flexibility in the hosted service.

These descriptions reflect current hosted routing behavior and product configuration and should be read together with our Privacy & Terms page and deployment model distinctions.

2) Privacy posture

  • No advertising network integration.
  • No sale of personal data.
  • Minimal account and operational data collection.
  • Customer-submitted content is processed to perform requested tasks.
  • Customer content is not used by One World Lingo to train public models.
  • Retention is limited to what is reasonably required to operate the service and support the selected product mode.
  • Where third-party processing is involved, provider-side handling may include the limited retention needed to perform the requested task under the applicable service terms.
  • Self-hosted BYOK environments remain under customer operational control.

3) Security controls

  • Encryption in transit.
  • Encryption at rest for managed platform data stores where applicable.
  • Scoped service access and least-privilege operational patterns.
  • Access logging and operational visibility where reasonably required.
  • Documented issue handling and remediation prioritisation.
  • Environment-based separation of protected integrations and deployment modes.

4) Operational guardrails

  • Clear plan-based usage limits.
  • Operational caps designed to protect service reliability.
  • Top-up support for additional usage where offered.
  • Retention and access controls aligned to the selected product mode.
  • Abuse prevention and service-protection limits where required.

Public plan pages may describe operational guardrails such as file, throughput, and retention limits. Enterprise or custom deployments may be scoped separately.

5) Legal & contracting

One World Lingo supports buyer evaluation with public legal surfaces and additional documentation where appropriate.

  • MSA available.
  • DPA available.
  • Sub-processor and provider information available on request.
  • Commercial and deployment discussions available for enterprise buyers.

6) Deployment models

Managed SaaS

Best for teams that want fast deployment, clear pricing, managed billing, and hosted processing with selectable operating modes.

BYOK / Self-Hosted

Suitable for customers who want greater deployment control, local operational ownership, and a licensing model aligned to self-hosted use cases.

Responsibilities differ between managed SaaS and self-hosted deployments. In self-hosted environments, customers are responsible for their own infrastructure, storage, secret management, and internal compliance controls.

7) What we claim carefully

  • We describe current controls and deployment options conservatively.
  • We do not advertise certifications, audits, or assurances that are not evidenced.
  • We distinguish between hosted SaaS posture and self-hosted deployment posture.
  • We do not present current hosted SaaS as privately network-isolated or fully European-owned where that is not evidenced.
  • Where a capability is deployment-specific, that distinction should be read literally.

Questions from security, legal, or procurement?

We can provide a clear starting point for buyer diligence, deployment evaluation, and contract discussion based on your operating model.

Start with legal surfaces

Review the public privacy page, MSA, and DPA first.

Privacy & Terms
Need deployment context?

Use the company and trust pages for hosted vs BYOK positioning.

View company page
Comparing plans?

Use the subscriptions page for pricing, usage guardrails, and purchase paths.

View plans