Tool inputs are processed locally
The current image, PDF, text, data, developer and color tools run in your browser. Files you select and content you enter into these tools are not uploaded to asdftools or sent to an AI provider for processing. Results are created on your device.
Downloaded files remain wherever you save them. Closing a tool does not delete your original files or downloaded results. Your browser, extensions, device and cloud-synced folders have their own privacy behavior outside our control.
Website requests and security logs
Visiting a page still requires a connection to our web server. Basic access and error logs may record an IP address, requested path, time, response status and technical details needed to operate the service and investigate errors or abuse.
These operational logs are separate from the files processed by the tools and from contact submissions. Their retention follows the server’s log-rotation settings and operational needs; the contact-record deletion schedule below is not a promise about web-server logs. Avoid putting sensitive information in URLs.
If you send a message
The contact form sends the message and any optional name or email address you provide to our server. Unlike tool inputs, a contact submission is intentionally transmitted so it can be reviewed and, if you provide an email address, replied to. Do not include passwords, private keys, confidential documents or sensitive personal information.
Submissions are stored in a private SQLite database on the server, outside the public website directory. Abuse-prevention records use a salted hash derived from the submitting IP address rather than storing the raw address in the contact rate-limit record. A hash is not a guarantee of anonymity, and the web-server logs described above may still contain an IP address.
Contact submissions and rate-limit identifiers are scheduled for deletion after 30 days. Automated cleanup runs daily, so removal occurs during the next cleanup run. Use the contact page for questions about a submission or to request its deletion; include enough context to identify it without resending sensitive material.
Cookies, libraries and tracking
The browser tools do not require an account. We do not run third-party advertising, third-party analytics or account-based tracking on the current site. Tool libraries are served from our own site rather than fetched from third-party script CDNs during use.
The contact page uses a session cookie for request security, including protection against cross-site request forgery. It is not an advertising cookie. We do not sell the information submitted through the contact form.
Future AI features and your choices
There is no live Claude API feature processing your tool inputs today. If an optional AI feature is introduced, we will explain what it sends, which provider receives it, the purpose and relevant retention information before asking you to use it. Local processing will not silently turn into cloud processing.
We use HTTPS and limit exposure of contact records, but no website can promise absolute security. This notice describes the current product rather than claiming universal legal compliance. We will update it when the way we handle information changes.