Data Retention and Deletion

Last updated: April 18, 2026

This document explains what data DocMind AI stores, how long it is retained, and how deletion is handled.

1. Retention Principles

• Retain only what is needed to operate, secure, and improve the Service.
• Allow user-initiated document deletion in product workflows.
• Keep legally required accounting/compliance records as required by law.

2. Retention by Data Category

Data Category	Examples	Retention Basis	Deletion Trigger
Uploaded document files	PDF objects in private storage	Service operation	Document deletion or account closure request
Vector indexes	Pinecone namespace vectors	Semantic retrieval	Document deletion or re-ingestion replacement
Extracted chunks	document_chunks rows	BM25/hybrid retrieval	Document deletion or re-ingestion replacement
Conversation history	Document-scoped chat messages	User experience continuity	Document deletion or account closure request
Usage logs	Upload/query counters, analytics events	Plan enforcement, abuse prevention, analytics	Lifecycle review and operational cleanup
Billing records	Payments, tax metadata, invoices	Legal/accounting compliance	Statutory retention expiry

3. Document Deletion Behavior

When a document is deleted in-app, the system is intended to remove:

• Stored document object (private storage)
• Associated vector namespace in Pinecone
• Stored extracted text chunks
• Document-scoped conversation history
• Document metadata record

4. Account Deletion Requests

If self-service account deletion is not yet available in your UI, users can request account-level deletion via support email. Billing records may still be retained where required by law.

5. Security and Backups

Some data may exist in short-lived operational backups according to provider backup/restore policies. Backup data is protected and removed through backup lifecycle rotation.

6. Contact

Data deletion and retention requests: adityagupta20042003@gmail.com
Legal index: /legal/index.html