Trust Center
One World Lingo is designed for privacy-first transcription and translation with a buyer-ready trust posture, clear hosted operating modes, and a primary BYOK / self-host licensing path for teams that need stronger deployment control.
OWL separates managed SaaS from BYOK / self-host so teams can choose the operating model that matches their control, review, and deployment requirements.
No ads, minimal account and operational data, and customer content is not used by One World Lingo to train public models.
We describe current controls, routing, and deployment options carefully and avoid overstating certifications, isolation claims, or enterprise maturity beyond what is supportable now.
1) Hosted operating modes
EU-only (Strict)
Designed for customers who want a stricter hosted operating path. 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 hosted path with broader operational flexibility and a different routing posture than EU-only (Strict).
These descriptions reflect current hosted routing behavior and product configuration. They should be read together with the Privacy & Terms page and with the distinction between managed SaaS and self-hosted deployment.
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 limited retention needed to perform the requested task under the applicable service terms.
- In BYOK / self-host deployments, customers remain responsible for their own infrastructure, storage, secret handling, and internal compliance controls.
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) Deployment models
BYOK / Self-Host Licensing
The primary higher-control path for organizations that want stronger deployment control, customer-managed provider configuration, and a licensing model aligned to self-hosted operation.
Managed SaaS
A secondary hosted option for teams that want simpler onboarding, managed billing, and hosted processing with selectable operating modes.
Responsibilities differ between managed SaaS and self-hosted deployments. BYOK / self-host should be treated as the stronger-control path, while hosted SaaS should be treated as the lighter operational path.
5) Legal and buyer review
One World Lingo supports buyer evaluation with public legal surfaces and additional diligence discussion where appropriate.
- MSA available.
- DPA available.
- Privacy and terms page available publicly.
- Sub-processor and provider information available on request.
- Commercial and deployment discussions available for serious buyers.
6) 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.
7) What we state carefully
- We describe current controls, routing, and deployment options conservatively.
- We do not advertise certifications, audits, or assurances that are not evidenced.
- We distinguish clearly between hosted SaaS posture and self-host deployment posture.
- We do not present the current hosted SaaS offer as privately isolated, fully sovereign, or fully European-owned where that is not evidenced.
- Where a capability is deployment-specific, environment-specific, or package-specific, that distinction should be read literally.
Questions from security, legal, procurement, or deployment review?
We can provide a clear starting point for buyer diligence, deployment-path review, and contract discussion based on your operating model and control requirements.
Use the deployment and company pages for hosted versus self-host positioning.
Choose pathUse the subscriptions page for hosted pricing and the licensing path for higher-control deployment.
View plans