Workflows
All tools
← All tools

Your files stay with you.

A few things to know about using ToolMoss.

File processing

Images, PDFs and videos are processed inside your browser. The tools do not upload those files to a server. Results are created on your device and saved when you choose Download. There is no server-side file library. Optional accounts store workflow recipes, not your files.

Website requests

Opening the site downloads the page and its supporting code from Cloudflare, our website host. Those normal website requests can include your IP address and browser information. Local file processing does not mean that visiting the website makes no network requests.

Closing the page

Your working files are held in the page’s memory. Reloading or closing the tab clears the working session, so download any results you want to keep first. Files you download remain on your device until you remove them.

Working offline

A tool can continue processing locally after its required code has loaded. Opening another tool, reloading a page or loading a component for the first time may require an internet connection.

Checking for yourself

In your browser’s developer tools, open the Network panel while processing a file. You should see no request containing your image, PDF or video. Browser extensions and your browser’s own services are outside ToolMoss’s control.

Accounts and workflow recipes

When you sign in with Google, ToolMoss stores your account identity and session in Cloudflare D1. Saving a workflow to the cloud uploads its name, nodes and parameters. Publishing creates a link accessible to anyone who has it. Original images, videos and PDF files are never included. You can delete private cloud workflows, revoke share links and delete your account. Local recipes remain in your browser until you remove them or clear site data. Previously downloaded copies of shared recipes cannot be recalled.

Suggestions & feedback

Your feedback is stored privately in Cloudflare D1 with your optional email, page path and language. A temporary hashed network identifier limits spam; it expires daily. Feedback is separate from your account and is not published. Files and workflow contents are not attached.