Skip to main content

LingoHub data retention periods

LingoHub provides detailed activity logs to help you monitor workspace events, track operational changes, and audit system activities. Data retention periods are standardized across all plans to ensure optimal performance, predictability, and privacy-friendly data handling.

Overview of available logs

  • Resource imports & exports: Logs of all manual or automated file import and export actions across your projects.

  • API logs: Detailed record of API events and requests for your workspace.

  • Integration logs: Activity history for connected integrations (e.g., GitHub, GitLab, Figma, Storyblok).

  • LINA executions (text processing): Logs covering automated AI translation and review activity (LINA).

  • Audit logs: Security and compliance tracking for workspace actions as well as user-level events.

  • Segment & translation history: Version history for individual text segments, key changes, and translation revisions.

Retention periods by subscription plan

Retention durations, version depth, and specific ceilings depend on your active subscription plan:

Data type

Free / Starter / Team (Legacy)

Trial / Sponsored

Pro

Enterprise

Additional limits & behavior

Resource imports

30 days

30 days

90 days

90 days

Retains the newest 1,000 entries per project (90 days max.)

Resource exports

30 days

30 days

90 days

90 days

Retains the newest 1,000 entries per project (90 days max.)

API logs

30 days

30 days

90 days

90 days

/

Integration logs

30 days

30 days

90 days

90 days

Effective retention is bounded by corresponding import/export logs.

LINA executions (text processing)

30 days

30 days

90 days

90 days

/

Audit logs (workspace)

30 days

30 days

365 days (1 year)

1095 days (3 years)

Tracks workspace-level actions and events performed by members.

Audit logs (user)

3 years

3 years

3 years

3 years

User-scoped logs (erased automatically if a user account is deleted per GDPR).

Segment key events & key-change history

Last 5 entries / segment

Last 5 entries / segment

Last 10 entries / segment

Last 20 entries / segment

Never trimmed within 90 days.

Translation versions

Last 5 entries / segment-language

Last 5 entries / segment-language

Last 10 entries / segment-language

Last 20 entries / segment-language

Never trimmed within 90 days.

Version-based translation history

Rather than using calendar windows that erase older revisions automatically, LingoHub shapes translation and segment history around version count:

  • Content-centric preservation: Every text segment keeps its most recent translation versions (5 on Free/Starter/Team, 10 on Pro, and 20 on Enterprise) regardless of how long ago the edits occurred.

  • Changelog guarantee: Entries inside your segment and key history are never trimmed within a 90-day window, ensuring your import changelog stays complete and reliable.

  • Long-term stability: A segment last updated two years ago retains its version history, while frequently updated strings remain clean and manageable.

Plan upgrades and downgrades

Understanding how tier changes affect your stored activity data is essential for managing your workspace history:

Upgrading your plan

Upgrading your subscription plan immediately expands your retention windows and version limits across your workspace from that point onward.

Downgrading your plan

When a plan downgrade occurs, LingoHub immediately enforces the lower tier's retention limits. This happens automatically:

  • Immediate deletion: Logs and version entries that exceed the lower tier's retention window or version limit are permanently deleted from our servers.

  • Unrecoverable data: If you downgrade from a higher tier (e.g., from a 90-day retention window down to 30 days) and later upgrade back to your original plan, the purged historical logs cannot be restored. Once pruned during a downgrade, the data is permanently removed.

Need more help?

Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.

Did this answer your question?