Privacy Policy
Effective upon publication. This operational draft should receive final legal review before commercial launch.
What Languvia processes
Languvia processes account and workspace information, connected WordPress site metadata, translation content submitted for processing, provider and usage metadata, billing records, support communications, security logs and consent records.
Why we process it
We use this information to provide translation, synchronize WordPress content, administer accounts and billing, secure the service, provide support, meet legal obligations and improve reliability.
Translation providers
When a workspace uses Google, DeepL or OpenAI, relevant source content and language instructions may be transmitted to the selected provider. Customers should avoid submitting data they are not authorized to process.
Retention
Languvia applies defined retention schedules to cloud translation payloads, security records, delivery logs and other operational data. See the Data Retention & Deletion page for current defaults.
Your requests
Workspace users can request exports, recovery or deletion through their Languvia account. Legal holds and statutory obligations may delay deletion where permitted by law.
Security
Credentials are encrypted at rest, connector traffic is signed, customer and administrator sessions are separated, and tenant identity is derived server-side for customer APIs.
Contact
Privacy requests should be submitted through the support or data-request workflow. Final controller/contact details must be inserted before commercial publication.