Your files stay your business.

No account. No permanent file library. Clear controls over what you upload and when it is removed.

Server workspace

Files uploaded to the server workspace are processed on the operator’s own infrastructure. File contents are not sent to third-party processing or advertising services. Connections, including your files in transit, pass through Cloudflare, our network provider, which terminates HTTPS; file responses are marked so they are not cached. Processing requires the server to read your files; this is not end-to-end encryption.

Temporary sessions

Files expire after two hours without activity, with an absolute maximum of 24 hours from the start of a session. A cleanup task runs every five minutes. “Delete my files” immediately revokes access and starts removing source files, results and previews. Files are not included in backups.

On-device text editing

When you select “On-device text”, the file you open is read in your browser. Its content is not uploaded. Closing the page clears this editor’s in-memory content. Download your changes before leaving.

Cookies and logs

A secure session cookie links you to your temporary files. Upload-resume details are stored on your device until the upload completes or you clear the session. File contents, passwords and preview grants are not written to application logs.

Supported operations

A separate usage ledger retains a secret-keyed hash of the visitor identity, byte counts and upload counts for a rolling 24 hours. It contains no filenames or file contents. Deleting files does not reset completed usage. By default, visitors sharing an IP address share an allowance. Read the fair-use details.

Files are never executed as programs. Previews and processing have resource limits. Some exports change formatting, metadata or quality; review the warnings attached to the selected tool and result.

Development environments

Production runs in Docker: a web/control stack, independently connected processing workers and a direct HTTPS download service. Development tests can use SQLite and local objects; the workspace identifies that environment. Production refuses the process-only executor.