Data Retention Policy

Overview

This document explains how long data and versions are retained in the Service.

Document Storage

• Documents are stored until deleted by the user or removed by the system
• Storage may be limited based on system constraints

Version Retention

To maintain performance and storage efficiency:

• Version history may be automatically pruned
• Retention may depend on document size and activity
• Older versions may be removed without notice

Example retention behavior:

• Smaller documents may retain more versions
• Larger documents may retain fewer versions

Autosave Behavior

• Autosave is best-effort
• Rapid edits may be merged into a single version
• Not every change is guaranteed to produce a version

Deletion

• Deleting a document may remove associated versions
• Some data may persist temporarily in backups or caches

Important Note

The Service is not a backup system. Users should maintain their own backups for critical data.