How DocPilot handles project workspace data.

DocPilot stores the information needed to provide your project documentation workspace, including account details, project names and descriptions, chat messages, uploaded knowledge sources, generated documents, missing information answers, task progress, export metadata, and workspace settings.

If you upload client files, briefs, spreadsheets, brand notes, or other project materials, those files and extracted summaries may be used to help generate and improve project documentation inside your workspace.

We use project data to create and maintain workspaces, generate documents, detect missing requirements, answer project-aware questions, render diagrams, support exports, and keep task state consistent across the product.

Backend database state is treated as the source of truth for critical workspace flows such as document inventory, generation status, sources, and saved documents.

Project context may be sent to the configured AI provider when you ask the assistant to analyze requirements, generate documentation, regenerate selected sections, create diagrams, or prepare AI-ready exports.

Do not enter production secrets, private keys, API tokens, passwords, payment credentials, or other sensitive credentials into prompts, project descriptions, uploaded files, or generated documents.

Project data is protected by authentication and database access controls. User workspaces are intended to be private unless a share or export flow is explicitly used.

No system can be guaranteed perfectly secure. You are responsible for deciding what client or business information is appropriate to upload to an AI-assisted workspace.

You can edit generated documents, manage project sources, delete projects where supported, choose what to export, and control whether a public share link is created.

If you need help with privacy-related requests, contact the project owner or support channel listed for this deployment.

DocPilot is built for project planning, requirements, and implementation documentation. It is not designed to collect medical records, financial account credentials, government identity numbers, or regulated production secrets.

Keep prompts and uploads focused on project context, product requirements, technical planning, UX flows, and implementation notes.