LocalDocu

Privacy by design

Privacy by design: document contents are processed on your device. No document-upload backend and no account required in the current release.

What stays local

  • Document contents you select
  • Document processing and local previews
  • Operation execution in the browser session

What the current application does not do

  • No document-upload backend for processing
  • No cloud document-processing pipeline
  • No account requirement
  • Cloud processing: Off · LocalDocu AI: Off

Data flow (current release)

  1. You select files on your device
  2. LocalDocu reads them in the browser
  3. A local document engine runs the operation
  4. Output is saved or downloaded on your device

What may change later

  • LocalDocu desktop app for heavier local workloads
  • LocalDocu AI in the desktop app: open-weight on-device model that uses document metadata and user intent to drive LocalDocu document-management commands (document contents stay on device)
  • Optional telemetry only if clearly disclosed — Phase 1 has no product analytics pipeline

We do not claim “100% private,” “completely secure,” or “zero data collection” as absolute guarantees. Claims match the current implementation.