Deletion & Retention

Browser-only tools

When a tool runs locally in the browser, Filechanges does not need to create a server-side copy of the file for that workflow. Your file is loaded into browser memory so the tool can read, change, and export it.

• The working copy remains in your current browser session.
• Resetting the tool, refreshing the page, or closing the tab clears that session copy.
• Because no server copy is created for those tools, there is usually nothing on Filechanges servers to delete afterward.

Server-assisted AI requests

For AI Translate and AI Summarize, text or uploaded documents can be sent to Filechanges server routes for the active request. In the current app code, the request body is parsed, text is extracted, and the generated result is returned without intentionally saving the uploaded source file as a permanent stored file.

Hosting infrastructure may still keep short-lived technical logs or request metadata outside the application logic. The statements on this page describe app behavior and do not replace a full infrastructure audit.

Requests for access, correction, or deletion

• If you used a browser-only tool, the fastest way to clear the working copy is to reset the tool, refresh, or close the tab.
• If you used a server-assisted tool and need help with access, correction, or deletion questions, use the Contact page and include the tool name and approximate time of the request.
• Only send the minimum information needed to identify your request.