Privacy Policy

This policy describes Docomium’s current privacy practices for the public website and local browser tools. It is written to match actual product behavior.

Summary

Current document tools process files and text in your browser. Docomium does not provide upload APIs for those tools and does not send your file contents or typed text to Docomium servers to perform the tool operation.

Visiting the website still creates ordinary web requests (for example loading pages and static assets). Optional analytics, advertising, accounts, and AI features are not enabled in the current release.

1. Browser-local tool processing

The following tools currently process content locally in your browser:

  • Merge PDF (/pdf/merge-pdf)
  • Split PDF (/pdf/split-pdf)
  • JPG to PDF (/pdf/jpg-to-pdf)
  • Remove PDF Pages (/pdf/remove-pages)
  • Rotate PDF Pages (/pdf/rotate-pdf)
  • PDF to JPG (/pdf/pdf-to-jpg)
  • Add Page Numbers (/pdf/add-page-numbers)
  • Compress Image (/images/compress-image)
  • Resize Image (/images/resize-image)
  • PNG to JPG (/images/png-to-jpg)
  • JPG to PNG (/images/jpg-to-png)
  • Word Counter (/text/word-counter)

For these tools, selected files and entered text remain on your device for processing. Object URLs and temporary browser memory are used during the session and are cleaned up by the tool UI where implemented.

Re-encoding images in the browser may strip metadata (for example EXIF). That is a consequence of canvas/image encoding, not server-side inspection.

2. Basic website and server request logs

When you load Docomium pages, your browser contacts the web server or CDN hosting the site. Hosting providers may record standard request metadata such as IP address, user agent, request path, and timestamps. Docomium does not claim zero server logging.

The `/health` endpoint is for operational checks and is not intended for document processing.

3. Analytics

Production analytics are not enabled in the current release. The codebase includes an analytics abstraction that is a no-op by default. Optional Google Analytics may be configured later via environment variables, but scripts load only after analytics consent is granted through the consent integration boundary.

If analytics are enabled later, this policy will be updated. Analytics must not receive document contents, Word Counter text, or sensitive filenames.

4. Advertising

Production advertising (for example Google AdSense) is not enabled. Ad slots currently render nothing unless advertising is configured, running in production, and advertising consent is granted. Live AdSense scripts are not loaded in the current release.

If ads are enabled later, cookies or similar technologies used by ad partners will be described here and in the Cookie Policy, and a certified consent solution may be required for some traffic.

5. Future account functionality

Accounts, saved history, and usage records are not implemented yet. If accounts are added, Docomium will collect the account information required to operate those features and update this policy before launch of that functionality.

6. Future AI or external-provider processing

AI and other external providers are not part of the current public tools. If a future tool sends document content to an external provider, Docomium will disclose that transmission before you proceed and will not claim on-device-only processing for that tool.

What we do not claim

This policy does not claim absolute anonymity, end-to-end encryption of local tools, zero residual browser artifacts, or certifications such as GDPR/CCPA/ISO/SOC unless and until those are independently implemented and verified.

Changes

Docomium may update this policy as features change. Material changes for new processing modes will be reflected here before those features are offered as production behavior.