The 60-Second Check
- Open any tool page, then open your browser DevTools with F12 (or right-click → Inspect) and switch to the Network tab.
- Use the Network tab's filter box to make third-party traffic obvious, e.g. type
-domain:thefreeaitools.comto hide the site's own assets — for the vast majority of the 37 studios the resulting list is empty while you run the tool, because your file bytes and text never leave the tab. - Watch the full request list for anything that is not a page asset. For the vast majority of the 37 studios, nothing but page assets appears — your file bytes and text never leave the tab.
- For proof, do the same in a second browser or a private window with an ad-blocking extension on: the tool output is identical, because the computation happened locally, not on a server.
The same check works in Firefox (Ctrl+Shift+E) and Safari (⌥ option+⌘ command+I, then the Network pane).
Requests You SHOULD See
A tool page normally shows: the HTML document itself, the site's own JavaScript/CSS/images, your browser's favicon fetch, and — only after you have made a consent choice — Google Analytics and Google AdSense. That is the whole list for 35 of the 37 studios.
Studios With Documented Requests
Exactly two multi-mode studios contain features that intentionally fetch third-party data, and both are documented on the tool page itself (the "Limitations" panel). The table is generated from the same source of truth as the studio pages, so it cannot drift:
| Studio | Hosts contacted | Purpose | What leaves your device |
|---|---|---|---|
| Interactive Map, Geodesic Measurement & Explorer Studio | nominatim.openstreetmap.org | place-name search | the address or place name you type into the location search box |
| Interactive Map, Geodesic Measurement & Explorer Studio | api.open-meteo.com | digital elevation model lookup | the latitude and longitude of the vertices you are measuring |
| Interactive Map, Geodesic Measurement & Explorer Studio | tile.openstreetmap.org, opentopomap.org, server.arcgisonline.com, basemaps.cartocdn.com | map tiles for the basemap you pick | your IP address and the map area and zoom level you are viewing |
| Qibla Direction, Solar Ephemeris & RF Geodesic Studio | nominatim.openstreetmap.org | place-name search | the address or place name you type into the location search box |
That table lists every deliberate third-party request the site can make while you use a tool. Map tiles and geocoding queries are made by your browser directly to those public providers; no tool file or measurement is proxied through this site.
Why This Works Without Uploads
The studios are single HTML pages with JavaScript modules. Compression, PDF assembly, format conversion, hashing, text analysis, chart rendering and the rest happen with browser APIs (Canvas, Web Audio, Web Workers, Web Crypto, Blob URLs). Those APIs run on your device.
There is a hard technical backstop as well: the site sends a Content-Security-Policy header whose connect-src directive governs fetch/XHR upload-type connections and permits them only to this site itself, the two documented geocoding/weather hosts and Google Analytics (once you consent). Any other destination is refused by your browser before a request is made, so even a bug in a tool could not quietly upload your data to an unknown server. AdSense works through its script/image directives, and public map tiles load as images from their public providers — neither of those carries your tool inputs.
Script Inventory & Consent
Full detail lives in the privacy policy and the security page. In short:
- Google Analytics loads only after you grant the analytics purpose in the consent banner; until then no measurement request is issued.
- Google AdSense loads only after you grant the ads purpose.
- No file you open, text you paste, password you generate, hash you compute or measurement you draw is uploaded for processing. There is no account system, no server-side processing queue, and no CDN speaking to a backend with your input.
Found a request that does not belong to this list? Please report it via the contact page (security-related findings can be emailed to security@thefreeaitools.com).