Privacy policy
Last updated: 26 August 2026
The short version
Most ToolKloud tools process your files inside your browser. For those tools, the file you select is read into your device's memory and never transmitted to us. Three tools need a server to work and are clearly labelled βserver-assistedβ on their own page. We do not require an account and we do not sell data.
Tools that run entirely in your browser
Image, PDF, video, audio, text, code and generator tools use browser APIs (Canvas, Web Workers, WebAssembly, the File API). Your file is never uploaded, so we cannot see it, store it, or recover it for you. Closing the tab discards everything.
Tools that send data to a server
- YouTube to MP3 β the video URL you paste is sent to our server, which downloads the audio stream and returns the converted file. The URL and the temporary media file are deleted from the server after the conversion completes.
- Text to Speech β the text you enter is forwarded to Microsoft's Edge text-to-speech service to synthesise audio. Do not paste confidential text into this tool. We do not retain the text after the audio is returned.
- Text to Speech voice cloning β the optional cloning feature additionally sends your voice sample and text to ElevenLabs, a third-party provider, and requires an API key. It is opt-in and separate from the standard voices.
- MCP Client sandbox β requests are executed against a demo Model Context Protocol server running on our infrastructure. The sandbox is stateless and resets between sessions.
Third-party resources
Two tools fetch code from third parties even though your files stay local: the PDF tools load the PDF.js rendering library from a public CDN (cdnjs), and the background remover downloads its AI model files once before running them on your device. Those requests fetch code and model weights only β they never carry your file. Fonts are served from Google Fonts.
Analytics and cookies
We use Google Analytics 4 to count page views and understand which tools are used. GA4 collects a randomised client identifier, page URL, referrer, approximate location derived from IP, and device and browser type. We do not send file names, file contents, or anything you type into a tool to analytics.
Your theme and language preferences are stored in your browser's local storage on your own device. They are not sent to us and are not used for tracking.
Server logs
Like any web server, ours records standard request logs (IP address, timestamp, requested path, user agent) for security and abuse prevention. These logs are rotated and are not combined with analytics data to build a profile of you.
Your choices
You can block analytics with any content blocker or by using a browser that blocks third-party scripts β every tool keeps working. Clearing your browser storage removes the theme and language preferences. For questions or a data request, email us at hello@toolkloud.com or use the contact page.
How ToolKloud Handles Your Files and Data
The short version: for almost every tool on this site, your file is never uploaded, so there is nothing for us to store, share or lose. This page exists to say exactly which tools that covers and to be specific about the ones it does not.
- Files are processed in your browser β image, video, PDF, text and cryptographic tools run locally through Canvas, WebAssembly and Web Crypto β your file stays in the tab's memory.
- No file storage and no retention period β there is no retention window to disclose because there is no upload; closing the tab is the whole deletion process.
- No accounts, no file history β we do not ask for an email or build a profile, so nothing you convert can be linked back to you later.
- Server-backed features are named explicitly β the few tools that require a server to function are identified here and on their own pages, along with what is sent.
- Analytics are aggregate only β we measure which pages are used, not what you put into them β file contents are never part of any analytics event.
If anything here is unclear or you want detail on a specific tool, ask us directly β we would rather answer than have you guess.