Your files never leave your device
Normal AG File Tools processing runs in your browser. Images, PDFs, Office documents, QR or barcode contents, OCR input and identity-document photos are not uploaded to an AG File Tools transformation server.
Browser engines and AI models
Some advanced tools load processing libraries, WebAssembly modules, fonts or AI model files from trusted static package/model hosts when you use that feature. Those downloads bring the processing code to your browser; they do not send your source file to a conversion service. Heavy tools may therefore take longer the first time they are used.
Analytics and advertising boundaries
AG File Tools exposes privacy-safe analytics hooks for events such as a tool opening or a process completing. Those hooks do not include file contents, filenames, passwords, OCR text, QR or barcode payloads, signature contents or document data. If advertising is enabled, the relevant vendors and advertising technologies are disclosed in the Cookies & Advertising page.
Google advertising disclosure
If Google advertising is enabled, Google and other advertising vendors may use cookies, web beacons, IP addresses or similar identifiers to serve, measure or personalize advertising. Google advertising cookies can be used based on visits to this site or other sites. Users can manage Google personalized advertising through Google Ads Settings.
For users in the EEA, UK or Switzerland, any legally required consent for advertising cookies, local storage or personalized advertising will be handled through the applicable consent-management flow. Personalized Google ads in those regions require the relevant Google-certified consent-management setup.
Local browser storage
Your theme preference may be stored locally in your browser. Processed outputs exist in browser memory until you download them, reload the page or close the tab.