Free • Fast • 100% Private

Transparency Report

Complete transparency about how ModiFile processes and deletes your files. See our technology stack and zero-data architecture.

All
Start Converting

Transparency Report

Complete transparency about how ModiFile works.

How Files Are Handled

1. Upload — File arrives via HTTPS and is saved to a temporary directory with a random UUID filename. No original filename is stored in logs.
2. Process — Conversion runs server-side using open-source tools (FFmpeg, Pillow, LibreOffice). No file content is ever logged or inspected.
3. Download — Converted file is served back. A 90-second countdown begins.
4. Delete — After 90 seconds, both input and output files are permanently deleted from disk.

Technology Stack

  • Backend: Python Flask (single-file, ~2500 lines)
  • Video/Audio: FFmpeg (industry standard)
  • Images: Pillow + OpenCV
  • PDF: PyPDF2, pdfplumber, PyMuPDF, pikepdf
  • AI: rembg (ONNX Runtime)
  • Documents: LibreOffice (headless)

What We Don't Have

  • ❌ No database
  • ❌ No user accounts
  • ❌ No logging framework
  • ❌ No analytics
  • ❌ No CDN tracking
  • ❌ No third-party scripts
  • ❌ No advertising trackers

Server Location

Our servers process files and immediately delete them. No data crosses borders because no data persists.

Open Source

Our entire codebase is transparent. The single-file Flask application is approximately 2,500 lines of Python, making it auditable and verifiable.

Reading this report critically

A transparency report is only as good as its methodology, so here is ours in plain language. Traffic figures count anonymised request logs that contain no user identifiers; these logs live for 14 days for abuse prevention, then expire automatically. Conversion counts come from aggregate counters incremented locally in your browser session — no file names, no contents, no account linkage.

We also publish what we do NOT measure. We do not use analytics that fingerprint devices, we do not sell or share any statistics with advertising networks, and we do not run A/B tests that require tracking individuals across visits. When a number on this page cannot be produced without collecting personal data, we say so rather than collect it.

This page is updated whenever architecture changes affect the privacy statements above. The last structural change was reviewed with the release of the current conversion engine; the date of that review appears in the version footer below. If any statement here ever conflicts with observed behaviour, the discrepancy is treated as a top-priority bug — report it and it will be answered within 24 hours.