Retention, purge controls, and storage expectations
The canonical version always lives at https://tavina.ai/docs/friendly/files-knowledge/retention-purge-storage
Retention, purge controls, and storage expectations
Tavina’s Knowledge Library is designed to avoid storing every artifact forever by accident. A Source may have an original binary file, extracted text or Markdown derivatives, chunk records, and retrieval indexes. Those artifacts can have different retention needs.
Tavina also uses subscription-plan entitlements to decide which usage categories are available, how much storage is included, when quota warnings appear, and how long conversation logs are retained. The app’s Activity and Settings surfaces are the best place to check the current values for your account. Support remains the source for account-specific billing, pricing, refund, or legal-policy questions.
Original files are not always kept forever
For files such as PDFs and EPUBs, Tavina may not need to retain the original binary forever after successful extraction. Retention should be explicit, safe, user-controllable where the product exposes controls, and compatible with storage metering.
This handbook does not promise that every original uploaded file is retained permanently.
When originals should not be purged silently
Tavina should not silently purge an original when doing so would make the Source unreliable or unrecoverable. Originals should be protected when extraction:
- failed;
- was partial;
- needs OCR;
- is encrypted or blocked;
- lacks enough provenance or metadata to preserve user expectations;
- has not produced durable extracted content and chunks.
Purging is confirmed and restorable
Purging an original or purging extracted derivatives is never a silent, one-way operation (tavina/tavina#1952, tavina/tavina#1953):
- You confirm first. A purge asks for your explicit confirmation, whether it comes from the panel or through your agent.
- Originals are captured byte-for-byte. Before an original is purged, Tavina stores an exact, checksum-verified copy and can restore it byte-for-byte from the recoveries list later. The capture has an operator-configurable size cap โ 256 MiB by default (
KL_ORIGINAL_PURGE_CAPTURE_MAX_BYTES). If the safety capture cannot be completed, the purge fails closed and nothing is purged. - Derivatives can be regenerated. Purging extracted derivatives is also confirmed; recovery regenerates them from the retained or restored original with the same pinned settings, and the panel offers a regenerate action for exactly this.
Extracted artifacts and chunks
When extraction succeeds, Tavina may keep extracted text, Markdown derivatives, chunk metadata, indexes, and provenance. Those derived artifacts support retrieval, citations, and traversal.
If an original is purged but extracted artifacts remain, Tavina should still be clear about what it can cite and what it can no longer inspect from the original file.
Plan-based storage and retention
Plan defaults can include a storage ceiling, voice availability, daily quota categories, and a conversation-log retention window. The current development defaults are:
| Plan | Voice | Storage ceiling | Conversation-log retention | Older conversation logs |
|---|---|---|---|---|
| Temp (trial) | Included | 100 MB | 60 days | Deleted after the Temp retention window; not archived. |
| Medium (base plan) | Included | 750 MB | Indefinite โ kept for the life of the subscription | Archived after about 90 days and kept while the subscription is active. |
| Legacy Light Duty (grandfathered) | Included | 500 MB | Indefinite โ kept for the life of the subscription | Archived after about 90 days and kept while the subscription is active. |
| Legacy Heavy Duty (grandfathered) | Included | 1 GB | Indefinite โ kept for the life of the subscription | Archived after about 90 days and kept while the subscription is active. |
| Legacy Max Duty (grandfathered) | Included | 2 GB | No automatic age-based cutoff in the current plan rules | Archived after about 90 days and kept while the account remains eligible for that plan. |
Legacy plan rows describe retired tiers that are no longer available for purchase; they apply only to accounts already grandfathered into them. If your account is on a legacy plan, the app shows that plan’s own values.
These values describe product behavior for the current development release. They are not a pricing table, refund policy, legal retention commitment, or guarantee that an account-specific exception cannot apply.
What counts toward storage
Where metering is available, Tavina may count several storage categories together:
- uploaded or retained files and extracted file artifacts;
- hot conversation logs;
- archived conversation logs;
- memory-store data used for personalization and recall.
The Activity view may show a total plus a category breakdown. A breakdown is an operational meter, not a complete legal data inventory. Some values may update after background measurement work finishes.
Are there exact file limits?
Exact Source count, storage, and file-size limits can depend on plan, deployment channel, and current account policy. The Handbook should not invent a number when Tavina has not shown one in your account.
Use the app-visible plan, usage, storage, and quota states as the source of truth. If you are near a limit, Tavina should warn you before silently losing data. If a file is too large or unsupported, Tavina should report the problem instead of pretending it was fully processed.
Quota warning notifications
Tavina can warn you as usage approaches a quota:
- around 80% of a daily limit, Tavina may show an informational warning;
- around 90%, Tavina may show a stronger warning;
- at 100%, Tavina may show an over-limit notice and block the quota-counted action until the relevant reset or plan change.
Quota notices are deduplicated so the same account should not receive repeated copies of the same warning level for the same category on the same day.
If you bring your own provider key, eligible provider usage may be marked as BYOK and may not count against Tavina-hosted inference quotas. BYOK does not remove storage, retention, connected-app, or other non-provider limits.
Archive is not the same as active chat context
Archived conversation logs are kept outside the hot conversation-log area. When supported, Tavina may still search, replay, or cite archived messages, but archived content may not behave exactly like recent chat context.
Memory summaries and distilled memories are separate from raw conversation logs. A raw conversation row expiring or moving to archive does not automatically mean every derived memory disappears at the same time.
Storage and billing expectations
This handbook can explain the kinds of limits Tavina exposes and the current development defaults for plan behavior. It does not define prices, refund terms, cancellation terms, tax treatment, legal privacy commitments, or account-specific billing exceptions.
Until formal policy pages cover those topics, contact support for current account or billing questions.