DocNimble is being written to avoid exaggerated privacy promises. The policy is intentionally simple: explain where files flow, who can access downloads, and what the current build actually deletes or retains.
Files are uploaded through the private workspace for live tools. Some heavier or worker-based tools may depend on remote processing when that path is configured. Public landing pages do not imply that every route is active.
Completed outputs are exposed through tokenized links rather than raw storage paths. This reduces guessing risk and gives the app a clean place to handle expiry, missing files, and deleted results.
Generated files and uploads should be removed according to short retention rules and cleanup jobs. The site avoids wording like “deleted instantly” unless that is truly what the current implementation does.
DocNimble may keep limited operational logs for error tracking, abuse prevention, diagnostics, and plan enforcement. Those logs are separate from the main document payload wherever possible.