Your files stay in your browser.

• Files, images, videos, or documents processed with AIToo tools
• Personal information submitted through tool inputs
• Browser history or usage patterns tied to a personal profile
• Tracking cookies for advertising profiles

Most AIToo tools run entirely in the browser. When you choose a file, the tool reads it locally, processes it in memory, and lets you download the result from the same page.

• Your files stay on your device
• Processing runs through browser APIs and client-side JavaScript
• No server upload is needed for standard tool workflows
• You remain in control of the source and output files

AIToo may use limited technical signals to keep the website reliable, such as anonymous page analytics, performance information, and error diagnostics. These signals are not designed to include the files, images, documents, or text you process with the tools.

Sidebar Tools processes selected text, links, image files, and visible-tab screenshots locally. Clicking its icon opens tools and remembers a minimal temporary screenshot source; it does not create a content request or replace pending or in-flight input. A right-click entry sends the chosen text, link, page URL, or image source. Use current page in the catalog explicitly submits the active page URL and available title. Content previews leave existing tool input unchanged and do not acknowledge delivery. Page previews show the URL and title without extracting the page body or capturing a screenshot. The extension does not scan pages in the background, read browsing history, send tool inputs to AIToo, or use analytics.

Temporary content and source metadata use browser session storage and expire after 15 minutes. Content is removed after consumption, discard, or expiry cleanup. The separate screenshot-source record contains request/window/tab identifiers, the page URL, and creation/expiry timestamps, without selected text or page title. Another icon click can refresh that source while preserving explicit pending or in-flight content. Session storage is cleared when the extension reloads or updates, or the browser restarts. Temporary image transfers use local IndexedDB, expire after 15 minutes, and are deleted after consumption or cleanup. If the browser is closed, expired images are removed when cleanup next runs. Recent tool shortcuts store identifiers locally without source content or processed results.

Local debug logs retain up to 200 session events with timestamps, version, request/window/tab identifiers, processing stages, safe error codes, and image format or dimensions. They exclude received text, page titles, full URLs, filenames, and image contents. You can clear or export them from Debug logs; exports also include the extension ID and browser user agent. Logs are not uploaded automatically and session logs clear on extension reload or browser-session end.

Previewing or loading a selected web image uses optional source-site access. When access is missing, clicking Preview image or Load web image requests only the selected image host; declining sends no image fetch. An already permitted source can show a thumbnail automatically after image selection, and image-data previews stay local. Image requests omit credentials and referrer and reject redirects. The source server receives the selected image URL and ordinary network information such as your IP address. Obsolete previews are canceled and their temporary image URLs released. You can revoke access in your browser extension settings and use local files or normal paste instead. YouTube thumbnail previews contact i.ytimg.com. Opening a linked web tool or feedback form contacts that service and follows its privacy policy. Visible-page capture uses temporary access granted by your click on the extension icon and runs only after a separate capture action.

Hosting, analytics, and performance services may help deliver the site. They do not receive your processed files through the standard client-side tool workflows.

Because standard processing happens locally, your files do not need to travel through AIToo servers. This reduces exposure and keeps the workflow simple: choose a file, process it in the browser, download the result.

We may update this policy as tools, hosting, or analytics practices change. Any meaningful update will be reflected on this page with a revised date.