Data Retention & Deletion
Default operational retention periods are configurable by Languvia administrators and subject to legal holds.
This Policy explains how Languvia retains and deletes information associated with its translation platform, plugins, publishing tools and support services. Read it alongside our Privacy Policy, Terms of Service and applicable Data Processing Addendum.
1. How long we retain information
We retain information only for as long as reasonably necessary to provide the requested services, maintain security, resolve disputes and meet applicable legal obligations. Retention depends on the information’s purpose, sensitivity and any required recordkeeping period.
Account information, translation records, support conversations, diagnostics and billing records may have different retention periods. The category-specific operational periods and scheduled deletion, anonymisation or archiving actions are described in our Privacy Policy. Archiving does not mean that information has been deleted.
2. Cancellation and content exports
Cancelling a subscription or uninstalling the plugin does not automatically delete all cloud information.
For ordinary account closure, you may request an export of eligible cloud-held content in supported formats within 30 days after termination. This is an export-request window—not a promise that all records will be deleted on day 30. It does not limit statutory access rights.
Deleting information from Languvia does not automatically remove translations stored on your WordPress website, hosting backups or independently controlled third-party systems. Website owners must manage those copies separately.
3. Requesting deletion
Contact privacy@languvia.com or submit a support request identifying the relevant account, website and information concerned. Do not include passwords or unnecessary identity documents. We may request proportionate verification of your identity or authority.
We will respond without undue delay and within the applicable legal deadline. Where the EU GDPR applies, this is generally one month after receiving the request, with any permitted extension explained within that period. We will explain any lawful refusal and available complaint rights.
4. Deletion, backups and service providers
When deletion is required, we will remove the relevant information from active systems and address copies held by service providers as required by law and our processing agreements.
Where immediate removal from protected backups is not technically possible, the information will be kept beyond ordinary use until scheduled deletion or overwrite. Restoring a backup must not undo an applicable deletion request. We will explain relevant backup limitations when handling your request.
5. Information that must remain
Limited information may remain where necessary to meet legal recordkeeping duties or establish, exercise or defend legal claims. We will restrict its use, explain the applicable reason and retain it only while that lawful need continues.
A default retention period or internal archive does not override a valid right to earlier deletion. This Policy does not restrict your mandatory privacy rights.
| Data type | Default period | Action | Notes |
|---|---|---|---|
| analytics events | 730 days | Operational analytics events. | |
| assist action log | 730 days | archive | Audited Assist actions. |
| assist commands | 90 days | delete | Short-lived audited WordPress support commands. |
| assist messages | 365 days | delete | Languvia Assist support history. Raw article/translation content is excluded from safe context by design. |
| audit logs | 2,555 days | archive | Commercial administration audit trail. |
| auth otps | 1 days | delete | Expired or consumed OTP records. |
| compatibility scans | 365 days | delete | WordPress compatibility metadata. |
| consent events | 730 days | anonymize | Consent evidence. |
| contact requests | 365 days | delete | Sales enquiries not converted to customer records. |
| delivery events | 365 days | anonymize | Bounce/complaint/delivery evidence. |
| email logs | 365 days | anonymize | Delivery evidence without indefinite recipient retention. |
| integrity scans | 365 days | delete | Translation Integrity aggregate scan history. |
| login events | 365 days | delete | Authentication history retained for security review. |
| migration scans | 180 days | delete | Guided migration dry-run metadata; no imported content payload. |
| provider logs | 180 days | delete | Provider execution diagnostics. |
| security events | 730 days | archive | Security/audit evidence. |
| sessions | 90 days | delete | Expired and revoked sessions. |
| translation jobs | 365 days | delete | Cloud job payloads should not be retained indefinitely after sync. |