Privacy Policy
We aim to keep routine tool work on your device. This page distinguishes browser-only processing from features that communicate with a service.
1. The short version
Tool Fly does not currently have a shared user account database for ordinary visitors. Many tools perform their work locally in your browser, so their input files and results are not uploaded to our application backend for processing. However, it would be inaccurate to say that every feature is entirely browser-only or that no information is ever stored anywhere.
Some preferences and drafts are saved in local storage on your device. The contact form sends your message to a backend and then by email. Text to Speech sends the text you submit to the configured speech backend. The website also requests web resources such as Google Fonts, and any server hosting this website may process routine connection data under its own configuration.
2. Tools that process data in your browser
For many file, text, image, PDF, video, calculator, and utility tools, processing is performed by code running on your device. In those cases, the selected file or entered value is handled in browser memory and is not sent to our application backend as part of that tool operation. For example, a local image resize or a calculator can process the selected data in the page, then let you download or copy a result. The page still had to be loaded from a web server, and static resources such as scripts and stylesheets must be delivered to your browser.
Your browser and operating system remain responsible for their own memory, caches, crash reports, extensions, synchronization, and security. Other software on your computer may also have access to files you open. Tool Fly cannot inspect or control those independent device-level processes.
Some tools save your work locally so it survives a page refresh. Examples include preferences such as theme and language, and certain drafts, notes, usage counters, or workspace settings. Local storage is held in the browser profile on this device. It is not a cloud backup and is not synchronized by Tool Fly. Other people using the same browser profile or software with access to the device may be able to access it. Local storage is not encrypted by this website as a separate protection layer.
The AI Assistant currently uses local, rule-based functionality in the app rather than a remote AI API. Its conversation history and rate-limit counters may be kept in this browser’s local storage. The temporary email feature is a local simulation: it does not create a real inbox or receive mail from external senders. These details may change if a future release adds a remote provider, account system, or real mail service; this policy should be updated before such a change is deployed.
When you download a result, it is saved or opened according to your browser’s download and file-handling settings. Tool Fly does not control the folder selected by the browser or what happens to a downloaded copy afterward.
3. Features that send information to a backend
Contact and feedback form
When you submit the contact form, your email address, selected topic, and message are sent to the configured backend. The backend uses the configured email service to deliver the message to toolfly8@gmail.com, with your address set as the reply-to address. The backend applies a submission rate limit. The code is configured not to write message bodies to its application logs. Once email is sent, delivery copies and retention are subject to the mail providers’ systems and policies. Do not include passwords, payment details, or other secrets in a message.
Text to Speech
If you use Text to Speech, the text you submit is sent to the configured Python API to generate audio. The current backend configuration does not log submitted text or retain the generated audio. The backend may log ordinary request metadata such as the client network address, path, and status depending on how it is run; hosting, proxy, or operating-system logs may also apply. Only submit text you are comfortable sending to that service.
Admin sign-in
The private admin workspace uses a backend and email delivery for one-time sign-in codes. This is an operator feature, not required for ordinary tool use. It processes the authorized email address and authentication-related request information.
Google Fonts
The site’s stylesheet requests fonts from Google Fonts. Your browser therefore contacts Google to retrieve those font resources, which may involve network information handled according to Google’s own policies. You can block third-party requests or use browser controls, though the site may then display a fallback font.
4. Why information is used
When an optional feature receives information, it is used to provide the action you requested. Specifically, contact details and the message are used to route and reply to your feedback; speech text is sent to synthesize the audio you asked for; and admin email information is used to verify access for the private operator workspace. Technical request information can be used to deliver responses, enforce rate limits, diagnose failures, and protect the service from misuse.
We do not currently operate a shared visitor account database or a centralized analytics profile for ordinary users. The local admin page may display browser-local usage information on the same device where it was generated. It should not be understood as site-wide analytics or a server-side visitor record.
Tool Fly does not sell personal information. We do not use submitted tool files to build advertising profiles. If future versions introduce advertising, remote AI providers, accounts, or centralized analytics, the information collected and the choices available should be explained here before those features are used.
5. Cookies, local storage, and device data
The app uses browser local storage for selected settings and feature data. We do not currently use a shared database for ordinary visitors or a first-party account system. Local storage can remain after closing a tab, until you clear it or the browser removes it. Private browsing modes may clear it automatically. This storage is associated with the site origin and browser profile; another browser or device will not normally see the same values.
The application may record limited page or tool usage in the local browser for its local admin workspace. This is browser-local analytics, not a site-wide visitor analytics service. We do not currently claim to collect a centralized visitor profile or IP-based analytics database. Some feature data can include text you typed into a draft, not just a setting, so consider clearing local storage on shared devices.
To remove browser-local data, open the browser’s site settings or developer storage controls for the current website and clear its site data. Menu names vary by browser; commonly, this is available through the lock or tune icon beside the address bar, under site permissions or cookies and site data. You may also use a private window for a temporary session, but the browser may still process network requests normally.
Clearing storage may remove saved drafts, preferences, and local workspace settings and may sign out the local admin workspace. Clearing storage does not delete emails already delivered through your mail provider, browser history, downloaded output, or records held by your device, network, browser vendor, hosting provider, or third-party services.
The current source does not intentionally use a first-party analytics cookie for ordinary visitor tracking. Your browser may still store technical data under its own rules, and external resources or future hosting configurations could introduce additional storage. If those practices change, this notice should be revised.
6. Server logs, hosting, and security
When a browser loads a website or calls an API, network infrastructure necessarily handles connection information to route the request. Depending on the deployment, this may include IP address, timestamp, requested path, status code, browser user-agent, and technical error data. This is normal network operation and may be recorded by a web server, reverse proxy, hosting provider, firewall, or operating system even when the application itself does not retain tool inputs.
The current Python backend’s request logging includes connection address and request metadata; it is configured not to print contact message bodies or submitted speech text. Log files, if enabled by the host or process manager, are controlled by that deployment and its retention settings. Rate-limiting logic also temporarily uses the connecting address in memory to apply request limits; its exact behavior and lifetime are determined by the current backend process.
This is a local-first design goal, not a claim that the internet has no logs or that third-party infrastructure never processes connection data. The current local-development services and the eventual deployed service may have different hosts and retention behavior. Before deployment, the operator should review and publish the actual hosting, email, logging, backup, and retention configuration. A reverse proxy may cause an application to see the proxy address instead of the visitor’s address unless it is configured to forward client metadata safely.
We use reasonable development practices, but no internet transmission, browser storage, email system, or local device can be guaranteed completely secure. Avoid transmitting confidential information unless necessary, and keep your browser and operating system updated.
8. Retention and security
Browser-local information remains on your device until removed or expired by the tool or browser. Contact messages are transmitted for delivery; copies may remain in email accounts and provider systems according to their settings. Text-to-speech input and output are not intentionally retained by the current application backend, but operational logs or third-party infrastructure may retain connection metadata. No online service or local storage mechanism can be guaranteed perfectly secure.
There is no central visitor account record from which ordinary visitors can retrieve a server-side profile. If you email us, the message may remain in the receiving mailbox, backups, and email provider systems until deleted under their retention practices. The website operator should establish a mailbox retention and deletion process for deployment; this code cannot determine how long a provider retains delivered mail.
Local drafts and settings may persist indefinitely unless a tool applies an expiry or you clear the site’s storage. Before lending or disposing of a device, remove local browser data and downloaded files as needed. Deleting one copy does not automatically delete copies exported, emailed, downloaded, or stored by a separate service.
9. Children and people using shared devices
Tool Fly is a general-purpose utility website and is not designed to collect children’s personal information or to knowingly create visitor accounts for children. Because the website has no ordinary visitor account system, it does not ask a visitor to provide a birth date as a condition of using its local tools.
Some tools save content locally, so users of shared or managed devices should clear browser storage and avoid entering information they do not want another device user to see. A parent, guardian, school, employer, or device administrator may also be able to view activity through device or network controls that are outside Tool Fly’s control.
10. Your choices and privacy requests
You have practical controls over information you choose to submit and data saved in your browser:
- Use browser site settings to clear local storage and other site data. This can also delete drafts and saved preferences.
- Do not submit optional information through the contact form or speech feature if you do not want it transmitted.
- Use browser privacy controls or extensions to restrict Google Fonts or other external requests.
- Choose not to use a feature that requires a backend, or review its notice before entering information.
- Contact us to ask a question or request help with information submitted through a feature.
We will assess requests based on the information available to us and the law that applies. Because ordinary visitors do not have a server-side account, we may not be able to identify or retrieve information stored only in a particular browser. We cannot remove information from independent email, hosting, internet service, or font providers solely by changing browser storage.
If you contact us about a privacy request, provide enough context for us to understand which feature and approximate submission you mean, but do not send passwords or sensitive identity documents unless we have explained a secure method and why they are necessary. We may need to ask a proportionate follow-up question to avoid acting on the wrong data.
11. Changes to this policy
We may update this policy when the site’s features, providers, or data flows change. The effective date at the top shows when this version was published. If a feature changes to send or retain additional information, this page and the relevant feature notice should be updated.
When reviewing this policy, pay particular attention to the feature-specific sections for contact email, Text to Speech, browser storage, Google Fonts, and hosting logs. These are the places where changes in service configuration are most likely to affect what data is transmitted or retained. The operator should publish the updated version before or when a material new data flow begins, where practical.
12. Contact about privacy
For privacy questions, contact toolfly8@gmail.com or use our contact page. The site has not specified a formal privacy officer, postal address, or legal entity, so this policy does not invent one.
For a question about a local browser draft, tell us which tool was involved and which browser you used. We usually cannot inspect your local storage remotely and will not ask you to email the stored file. For a question about a contact message, identify the approximate date and subject so we can locate the relevant email in the destination mailbox if it is still retained. For a speech request, do not resend the original text unless needed to explain your question.