FILEFRUIT POLICY

Security

Local tools process files inside the browser and do not upload file contents to FileFruit.

A tool that needs native processing explains that requirement before upload and requires explicit consent.

Uploaded inputs are removed after processing. Inputs, outputs, and job controls are also swept after the one-hour expiration window.

A one-day private-object-storage lifecycle is a backup to the application’s one-hour deletion target, not the normal retention promise.

File signatures, declared sizes, supported formats, archive paths, page ranges, and output constraints are validated before or during processing.

Email support@filefruit.com for product support, privacy or accessibility requests, security concerns, and abuse reports. Bug reports should identify the FileFruit tool, page URL, browser and version, operating system, steps to reproduce, expected result, actual result, and visible error text.

Do not email private, confidential, identity, financial, medical, or otherwise sensitive source files.

Screenshots are optional; check them for sensitive information before sending.

FileFruit support will never ask for passwords, tokens, or account credentials.