Your files, your business.
A plain-language description of how this version handles your data. Updated 16 November 2026.
What is processed
When you submit a document, a temporary copy is uploaded to this application’s server. Document conversion uses pdf2docx, LibreOffice, and local text extraction; image conversion uses Pillow. Media tasks send the supplied link to the source platform through yt-dlp and download its public media. Temporary page previews are generated locally for the conversion panel. Files are not sent to a generative AI service.
Where files are kept
This installation uses private Vercel Blob storage and a shared Turso job database. Processing runs in isolated Vercel Sandbox environments. File downloads require the same anonymous browser session that created the task. A random HttpOnly cookie identifies that session; we do not require an account, email address, or social login.
When files are deleted
Downloadable outputs and video metadata expire after one hour. A daily cleanup and one-day storage expiry remove temporary files; abandoned uploads cannot be used after their token or task expires. Delete files revokes new access immediately and triggers removal, including cancellation of ongoing work. An already transferred download cannot be recalled from your device.
Operational records
Minimal job records, such as task type, status, byte count, and error code, are kept for up to seven days. Temporary source links are stored privately for video resolution and deleted when they expire. The application does not intentionally log document text, filenames, complete submitted URLs, signed links, or file contents.
Your choices
Use Delete files to remove a task, or wait for automatic expiry. Clearing the session cookie loses access to earlier tasks but does not make a permanent server copy; automatic cleanup still applies. We use first-party usage analytics for an owner-only dashboard. A random browser identifier lasts up to one year and estimates unique browsers, not identifiable people. We keep country-level location supplied by the hosting edge, general device type, daily activity, successful conversions, and download-start counts. We do not store IP addresses, precise locations, document contents, filenames, or submitted links in analytics. Aggregated usage records remain after temporary files are deleted. Clearing the visitor cookie starts a new anonymous browser identity. There are no advertising or marketing trackers.