Do my files leave my device when I convert them?

For many tools, processing runs in the browser and file contents are not uploaded as part of that workflow. Check the tool page for its current model.

Does feedback attach my file?

No. Feedback never attaches uploaded files or converted output.

Are diagnostics required?

No. They are checked by default for better troubleshooting, but you can uncheck them. The page path is still included with the submission.

Where is the full Privacy Policy?

On the Privacy page at /privacy.

Illustration of a file staying inside a browser with a privacy shield beside a feedback note

Privacy and file formats

How Looty Tools Protects Your Files and Privacy

Looty Tools is built around practical browser utilities. For many tools, file processing stays on your device. Feedback and contact messages are separate: they can send limited text and optional technical details to the team, but they do not attach your source files or converted downloads. This guide explains both sides clearly.

Browser-based local processing

Many Looty Tools utilities process files directly in your browser. For those workflows, file contents are handled on your device for the conversion or editing task and are not uploaded to Looty Tools servers as part of the tool workflow.

Temporary browser memory (and optional local drafts on some tools) may hold working data on your device. Closing or refreshing the page generally clears temporary processing state. Always read the individual tool page for its current model and limits.

Using a tool versus submitting feedback

Running a converter or editor is not the same as sending a feedback form. Tool workflows that are local keep the file on your device for that job. Feedback reports are messages to the Looty Tools team; they are delivered internally as email and never include the uploaded file or the converted result as attachments.

What feedback can include

Every feedback submission includes your message, the selected report or suggestion type, the tool you were using (identified from the workspace), and the current page path.

Diagnostics are optional and checked by default. While enabled, the report may also include browser user agent, viewport width and height, and language. You can uncheck the box before sending. Optional contact email may be prefilled when you are signed in, but you can clear it.

Always: message, feedback type, tool identity, page path.
While diagnostics stay checked: user agent, viewport dimensions, language.
Never attached: uploaded files, conversion output, or download binaries.

What is excluded

Feedback does not collect clipboard contents, cookies, or authentication tokens as form fields. Network addresses may be used on the server for abuse prevention such as rate limiting; they are not written into the feedback email body as a user-facing diagnostic field.

If you are signed in, a verified account identifier may be attached server-side so the team can associate follow-up—never your password.

Limits of browser-only privacy claims

Local processing applies where a tool is designed that way and says so. It is not a blanket promise for every feature forever. Shared or untrusted devices remain risky even when a tool is local. For the full legal policy, see the Privacy page.

Read each tool’s privacy notes. Prefer the Privacy Policy and this guide together when you need both product detail and policy wording.

Where to learn more

Use the Privacy Policy for the formal policy, Contact Us for general messages, and the reporting guide when you need to file an in-tool issue report.

Files and Privacy FAQ

Do my files leave my device when I convert them?: For many tools, processing runs in the browser and file contents are not uploaded as part of that workflow. Check the tool page for its current model.
Does feedback attach my file?: No. Feedback never attaches uploaded files or converted output.
Are diagnostics required?: No. They are checked by default for better troubleshooting, but you can uncheck them. The page path is still included with the submission.
Which diagnostic fields are collected when enabled?: User agent, viewport width and height, and language.
Where is the full Privacy Policy?: On the Privacy page at /privacy.

Related guides

← Back to all guides