Explainer ·
If a Utilio tool needs server processing
Utilio's current local tools do not upload files for processing. This page explains what a future tool would need to say before using server processing.
Short version
Today, supported local tools process files, text, settings, generated values, and results in the browser; Utilio does not send that local tool content to a Utilio server for the core task.
A future server-processed tool would be different: its page should explain what is sent, why it is needed, how long files are kept, and how deletion works before you start.
The page should also explain limits, processors, analytics boundaries, and failure states before you send anything.
What the page would need to explain
If Utilio later adds a tool that needs server processing, that tool would need a separate processing notice before you start. The page should explain the input sent to Utilio, why server processing is needed, what result to expect, and when the result is available.
Server processing can be useful when work is too heavy for the browser, such as very large files, long-running batch work, formats with poor browser support, or tasks that need retries.
- A future heavy PDF tool might send a selected file to Utilio, process it, then return a downloadable result.
- A future batch image tool might keep temporary input and output files while processing runs.
- A future Pro or API tool might require sign-in, rate limits, processing status, file storage, and deletion controls.
What would not happen automatically
Adding a server-processed tool would not change existing local tools into upload tools without a different processing notice and a clear explanation for users. Browser-local tools would still need to keep their local processing promise.
A future server-processed tool would not be allowed to silently use uploaded files, pasted text, generated values, or results for advertising, AI training, unrelated profiling, or open-ended storage.
- No current local tool is converted into a server-processed tool by this page.
- No future server-processed tool should hide what is sent or how deletion works.
- No analytics event should include raw file content, raw pasted text, passwords, keys, tokens, raw domains, URLs, or tool results.
What you should still watch out for
Server processing creates a different decision about trust. Before using that kind of tool, check file sensitivity, legal permission, retention window, deletion controls, download link behavior, account requirements, region, and processors.
Do not send confidential documents, production credentials, private keys, access tokens, regulated data, or third-party personal data for server processing unless the page clearly supports that use and you have the right to process it.
How this differs from local tools and DNS Lookup
Browser-local tools can finish the core operation in the browser. DNS Lookup is a network lookup that sends only the domain and DNS record type to Cloudflare DNS over HTTPS. A future server-processed tool would send the input to Utilio or its processors.
That separation matters: local processing, network lookup, and server processing need distinct processing notices, explanations, limits, and deletion language.
Questions people ask about server processing
Would a server-processed tool upload my file?
Yes, if a future tool is labeled for server processing, the input would leave the browser. The page would need to explain exactly what is sent and why before you start.
How long would Utilio keep uploaded files?
A future server-processed tool would need a specific retention window before launch. Utilio does not accept user files for server processing today, so local tools do not have a server file-retention window.
Could I delete a server-processed result?
A future server-processed tool should explain manual deletion, automatic deletion, download link expiry, and what logs or security records may remain. Without that disclosure, the tool should not be treated as equivalent to a local browser tool.
Would server-processed tools use my files for AI training or ads?
No server-processed tool should silently do that. If Utilio adds server-processed tools, their pages and policies must say what is excluded from advertising, AI training, profiling, and unrelated reuse before launch.