Temporary processing
Local when possible. Temporary when necessary. Never permanently stored by us.
Tasks that stay on your device
Every tool available today — merging, splitting, organizing, rotating, extracting and deleting pages, images to PDF and PDF to images — runs entirely in your browser. Those files are never transferred to us.
Tasks that may need temporary processing
Some future tasks, such as text recognition or complex conversion, cannot be completed on a typical device. For those, your file is transferred over an encrypted connection to temporary processing storage, processed, and returned to you.
You are always told before this happens, and you can decline. Nothing is transferred without your explicit confirmation. The current temporary processing size limit is 25 MB.
No permanent document storage
We do not keep a document library. There is no "My Documents" area, no permanent uploads, no permanent generated outputs, and no permanent thumbnails. We process documents; we do not become your document repository.
Deletion
After your result is delivered, the platform explicitly deletes the input, any intermediate artifacts and the temporary output, then verifies with the storage provider that the objects are gone. Only after that verification does your receipt say deletion is confirmed. If verification has not completed yet, the receipt says deletion is being completed — we do not report deletion before it is real.
If you abandon a task
If you close the tab, lose connection or never collect a result, an automated cleanup removes the temporary objects. The application aims to remove abandoned objects within one hour. A storage-provider expiry rule acts only as a secondary safety net, not as the primary deletion mechanism.
What we keep
We keep processing metadata without document content: job identifier, account, processing mode, status, sizes, timing, deletion state and failure category. We never store document bytes, extracted text, page images or generated output content in our database or logs.
Encryption — stated accurately
Transfers use TLS, and temporary objects are encrypted at rest by the storage provider. This is standard transport and server-side encryption. It is not end-to-end encryption and it is not zero-knowledge: during processing, the processing system can read the file in order to do the work you asked for.
Private processing (future)
Controlled, organization-specific processing environments are a planned enterprise capability. They do not exist today and are not offered.